[BUG] Support file / packet capture download times out — port 28082/tcp missing from example docker-compose.yml

Open Beginner friendly
#191 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
1/5
Estimated time
Under an hour
Newbie friendliness
88/100
Issue type
Bug
Clarity
Clearly specified
Activity status
Active
Tech stack
docker, docker-compose
Domain
devops

Research direction

Start with the example docker-compose.yml used in the image documentation and review its published ports. Add the port mapping for 28082/tcp, then deploy the example and verify that support file and packet capture downloads complete successfully.

Written by the indexing model from the issue text.

Description

Is there an existing issue for this?
  • I have searched the existing issues
Current Behavior

When using the example docker-compose.yml as provided in the image documentation, trying to download a "Support File" or a packet capture from the UniFi Network Application web UI fails with a timeout.
This happens because the controller serves these downloads over port 28082/tcp, which is not exposed/mapped in the container's port list.

Expected Behavior

Support file and packet capture downloads should complete successfully.
Port 28082/tcp should be included (at least as an optional mapping, similar to 1900, 8843, 8880, etc.) in the example docker-compose.yml so users aren't left without a working download feature.

Steps To Reproduce
  1. Deploy the container using the example docker-compose.yml as provided in the documentation.
  2. Log into the UniFi Network Application web UI.
  3. Go to UniFi Device > Select device -> Settings and click "Download support file" (or attempt to download a packet capture in Airview - Select WiFi band - packet capture).
  4. The download request hangs and eventually times out.
  5. Add 28082:28082 to the port mappings and restart the container — the download now works.
Environment
- OS: Debian/13
- How docker service was installed: Docker Compose on docker-cli
CPU architecture

arm64

Docker creation
services:
  unifi-network-application:
    image: linuxserver/unifi-network-application:10.6.101
    container_name: unifi-app
    depends_on:
      - unifi-db
    environment:
      - PUID=1003
      - PGID=1003
      - TZ=Europe/Rome
      - MONGO_USER=unifi
      - MONGO_PASS=PEprrWVq7fZdeUV
      - MONGO_HOST=unifi-db  # Usa il nome del servizio
      - MONGO_PORT=27017
      - MONGO_DBNAME=unifi
      - MONGO_AUTHSOURCE=admin
      - MEM_LIMIT=3072
      - MEM_STARTUP=1024
    volumes:
      - ./config:/config
    ports:
      - 11443:8443
      - 3478:3478/udp
      - 10001:10001/udp
      - 8080:8080
      - 1900:1900/udp
      - 6789:6789
    restart: unless-stopped
Container logs
"docker logs unifi-app" shows nothing relevant, the application container itself starts and runs normally, no errors logged there:
[ls.io-init] done.

However, on the UniFi AP side (via SSH), the following error appears when attempting the support file upload/download:

Sat Sep  5 12:08:20 2026 user.notice syswrapper[17997][5474]: Failed to upload support file. Http code: 000, rc: 7

"rc: 7" corresponds to curl's "Failed to connect to host" error, and "Http code: 000" confirms no HTTP response was ever received — consistent with port 28082/tcp not being reachable, since it isn't published in the container's port mapping / not allowed through the firewall.
Dominant language
Dockerfile
Stars
1.2k
Forks
98
PR merge metrics
No merged PRs in 30d

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from linuxserver/docker-unifi-network-application

All issues in linuxserver/docker-unifi-network-application

Similar issues

More DevOps issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.