Portainer Templates logo

Portainer Templates

Unifi-network-application Unifi-network-application

Network

The Unifi-network-application software is a powerful, enterprise wireless software engine ideal for high-density client deployments requiring low latency and high uptime performance.

Image details

Pulls: 1.9M
Architectures: amd64, arm64
Image size: 270 MB
Latest: 10.4.57
User: linuxserver
Created: Sep 06, 2023
Updated: 6 days ago
Status: active

Configuration

Type
Container
Platform
linux
Image
linuxserver/unifi-network-application:latest
Ports
8443:8443/tcp3478:3478/udp10001:10001/udp8080:8080/tcp1900:1900/udp8843:8843/tcp8880:8880/tcp6789:6789/tcp5514:5514/udp
Volumes
/config : /srv/lsio/unifi-network-application/config
Env vars
PUID=1000PGID=1000TZ=Etc/UTCMONGO_USER=unifiMONGO_PASS=MONGO_HOST=unifi-dbMONGO_PORT=27017MONGO_DBNAME=unifiMONGO_AUTHSOURCE=adminMEM_LIMIT=1024MEM_STARTUP=1024MONGO_TLS=
Restart
unless-stopped

Template by technorabilia

Notes

Portainer App Templates by Technorabilia, based on data provided by LinuxServer.io.

Ensure to create the following volume directories on the host file system, or modify the paths in the volume mapping section under the advanced options below, as needed.

mkdir -p /srv/lsio/unifi-network-application/config

Installation

  1. Ensure both Docker and Portainer are installed, and up-to-date
  2. Log into your Portainer web UI
  3. Under Settings → App Templates, paste the below URL
  4. Head to Home → App Templates, and the list of apps will show up
  5. Select the app you wish to deploy, fill in any config options, and hit Deploy

Template Import URL

https://raw.githubusercontent.com/Lissy93/portainer-templates/main/templates.json
Show Me demo

docker run -d --name Unifi-network-application \
  -p 8443:8443/tcp \
  -p 3478:3478/udp \
  -p 10001:10001/udp \
  -p 8080:8080/tcp \
  -p 1900:1900/udp \
  -p 8843:8843/tcp \
  -p 8880:8880/tcp \
  -p 6789:6789/tcp \
  -p 5514:5514/udp \
  -e 'PUID=1000' \
  -e 'PGID=1000' \
  -e 'TZ=Etc/UTC' \
  -e 'MONGO_USER=unifi' \
  -e 'MONGO_PASS=' \
  -e 'MONGO_HOST=unifi-db' \
  -e 'MONGO_PORT=27017' \
  -e 'MONGO_DBNAME=unifi' \
  -e 'MONGO_AUTHSOURCE=admin' \
  -e 'MEM_LIMIT=1024' \
  -e 'MEM_STARTUP=1024' \
  -e 'MONGO_TLS=' \
  -v /srv/lsio/unifi-network-application/config:/config \
  --restart=unless-stopped \
  linuxserver/unifi-network-application:latest

Save this file as compose.yaml and run docker compose up -d
Use this only as a guide.

services:
  unifi-network-application:
    image: linuxserver/unifi-network-application:latest
    ports:
      - 8443:8443/tcp
      - 3478:3478/udp
      - 10001:10001/udp
      - 8080:8080/tcp
      - 1900:1900/udp
      - 8843:8843/tcp
      - 8880:8880/tcp
      - 6789:6789/tcp
      - 5514:5514/udp
    volumes:
      - /srv/lsio/unifi-network-application/config:/config
    environment:
      PUID: '1000'
      PGID: '1000'
      TZ: Etc/UTC
      MONGO_USER: unifi
      MONGO_PASS: ''
      MONGO_HOST: unifi-db
      MONGO_PORT: '27017'
      MONGO_DBNAME: unifi
      MONGO_AUTHSOURCE: admin
      MEM_LIMIT: '1024'
      MEM_STARTUP: '1024'
      MONGO_TLS: ''
    restart: unless-stopped

Save this file as unifi-network-application-stack.yml, then from a manager node, run docker stack deploy -c unifi-network-application-stack.yml unifi-network-application

version: '3.8'
services:
  unifi-network-application:
    image: linuxserver/unifi-network-application:latest
    ports:
      - 8443:8443/tcp
      - 3478:3478/udp
      - 10001:10001/udp
      - 8080:8080/tcp
      - 1900:1900/udp
      - 8843:8843/tcp
      - 8880:8880/tcp
      - 6789:6789/tcp
      - 5514:5514/udp
    volumes:
      - /srv/lsio/unifi-network-application/config:/config
    environment:
      PUID: '1000'
      PGID: '1000'
      TZ: Etc/UTC
      MONGO_USER: unifi
      MONGO_PASS: ''
      MONGO_HOST: unifi-db
      MONGO_PORT: '27017'
      MONGO_DBNAME: unifi
      MONGO_AUTHSOURCE: admin
      MEM_LIMIT: '1024'
      MEM_STARTUP: '1024'
      MONGO_TLS: ''
    deploy:
      restart_policy:
        condition: any

Save each file below into a folder, then run kubectl apply -f .
Written for k3s, but works on any cluster: bind mounts use hostPath, named volumes get a persistent volume claim, and ports are exposed via a LoadBalancer service.

unifi-network-application-deployment.yaml

apiVersion: apps/v1
kind: Deployment
metadata:
  name: unifi-network-application
  labels:
    app: unifi-network-application
spec:
  replicas: 1
  selector:
    matchLabels:
      app: unifi-network-application
  template:
    metadata:
      labels:
        app: unifi-network-application
    spec:
      containers:
        - name: unifi-network-application
          image: linuxserver/unifi-network-application:latest
          env:
            - name: PUID
              value: '1000'
            - name: PGID
              value: '1000'
            - name: TZ
              value: Etc/UTC
            - name: MONGO_USER
              value: unifi
            - name: MONGO_PASS
              value: ''
            - name: MONGO_HOST
              value: unifi-db
            - name: MONGO_PORT
              value: '27017'
            - name: MONGO_DBNAME
              value: unifi
            - name: MONGO_AUTHSOURCE
              value: admin
            - name: MEM_LIMIT
              value: '1024'
            - name: MEM_STARTUP
              value: '1024'
            - name: MONGO_TLS
              value: ''
          ports:
            - containerPort: 8443
              protocol: TCP
            - containerPort: 3478
              protocol: UDP
            - containerPort: 10001
              protocol: UDP
            - containerPort: 8080
              protocol: TCP
            - containerPort: 1900
              protocol: UDP
            - containerPort: 8843
              protocol: TCP
            - containerPort: 8880
              protocol: TCP
            - containerPort: 6789
              protocol: TCP
            - containerPort: 5514
              protocol: UDP
          volumeMounts:
            - name: unifi-network-application-data-0
              mountPath: /config
      volumes:
        - name: unifi-network-application-data-0
          hostPath:
            path: /srv/lsio/unifi-network-application/config

unifi-network-application-service.yaml

apiVersion: v1
kind: Service
metadata:
  name: unifi-network-application
spec:
  type: LoadBalancer
  selector:
    app: unifi-network-application
  ports:
    - name: 8443-tcp
      port: 8443
      targetPort: 8443
      protocol: TCP
    - name: 3478-udp
      port: 3478
      targetPort: 3478
      protocol: UDP
    - name: 10001-udp
      port: 10001
      targetPort: 10001
      protocol: UDP
    - name: 8080-tcp
      port: 8080
      targetPort: 8080
      protocol: TCP
    - name: 1900-udp
      port: 1900
      targetPort: 1900
      protocol: UDP
    - name: 8843-tcp
      port: 8843
      targetPort: 8843
      protocol: TCP
    - name: 8880-tcp
      port: 8880
      targetPort: 8880
      protocol: TCP
    - name: 6789-tcp
      port: 6789
      targetPort: 6789
      protocol: TCP
    - name: 5514-udp
      port: 5514
      targetPort: 5514
      protocol: UDP

Save this file as ~/.config/containers/systemd/unifi-network-application.container

[Unit]
Description=Unifi-network-application

[Container]
Image=linuxserver/unifi-network-application:latest
ContainerName=unifi-network-application
PublishPort=8443:8443/tcp
PublishPort=3478:3478/udp
PublishPort=10001:10001/udp
PublishPort=8080:8080/tcp
PublishPort=1900:1900/udp
PublishPort=8843:8843/tcp
PublishPort=8880:8880/tcp
PublishPort=6789:6789/tcp
PublishPort=5514:5514/udp
Environment=PUID=1000
Environment=PGID=1000
Environment=TZ=Etc/UTC
Environment=MONGO_USER=unifi
Environment=MONGO_PASS=
Environment=MONGO_HOST=unifi-db
Environment=MONGO_PORT=27017
Environment=MONGO_DBNAME=unifi
Environment=MONGO_AUTHSOURCE=admin
Environment=MEM_LIMIT=1024
Environment=MEM_STARTUP=1024
Environment=MONGO_TLS=
Volume=/srv/lsio/unifi-network-application/config:/config

[Service]
Restart=always

[Install]
WantedBy=default.target

Then reload systemd and start the service:

systemctl --user daemon-reload
systemctl --user start unifi-network-application

For a system-wide service, use /etc/containers/systemd/ and drop --user.

For more installation options, see the Documentation in our GitHub repo

linuxserver.io
Blog Discord Discourse GitHub Open Collective
The LinuxServer.io team brings you another container release featuring:
  • regular and timely application updates
  • easy user mappings (PGID, PUID)
  • custom base image with s6 overlay
  • weekly base OS updates with common layers across the entire LinuxServer.io ecosystem to minimise space usage, down time and bandwidth
  • regular security updates

Find us at:
  • Blog - all the things you can do with our containers including How-To guides, opinions and much more!
  • Discord - realtime support / chat with the community and the team.
  • Discourse - post on our community forum.
  • GitHub - view the source for all of our repositories.
  • Open Collective - please consider helping us by either donating or contributing to our budget

linuxserver/unifi-network-application

Scarf.io pulls GitHub Stars GitHub Release GitHub Package Repository GitLab Container Registry Quay.io Docker Pulls Docker Stars Jenkins Build
The Unifi-network-application software is a powerful, enterprise wireless software engine ideal for high-density client deployments requiring low latency and high uptime performance.
unifi-network-application

Supported Architectures

We utilise the docker manifest for multi-platform awareness. More information is available from docker here and our announcement here.
Simply pulling lscr.io/linuxserver/unifi-network-application:latest should retrieve the correct image for your arch, but you can also pull specific arch images via tags.
The architectures supported by this image are:
| Architecture | Available | Tag | | :----: | :----: | ---- | | x86-64 | ✅ | amd64-\ | | arm64 | ✅ | arm64v8-\ |

Application Setup

After setup, the web UI is available at https://ip:8443. The application can be configured, or a backup restored, using the first run wizard.
This container requires an external mongodb database instance.

Setting Up Your External Database

Starting with version 8.1 of Unifi Network Application, mongodb 3.6 through 7.0 are supported. Starting with version 9.0 of Unifi Network Application, mongodb 8.0 is also supported.
Make sure you pin your database image version and do not use latest, as mongodb does not support automatic upgrades between major versions.
MongoDB >4.4 on X8664 Hardware needs a CPU with AVX support. Some lower end Intel CPU models like Celeron and Pentium (before Tiger-Lake) more Details: Advanced Vector Extensions - Wikipedia don't support AVX, but you can still use MongoDB 4.4.
If you are using the official mongodb container, you can create your user using an init-mongo.sh file with the following contents (do not modify; copy/paste as is):
#!/bin/bash

if which mongosh > /dev/null 2>&1; then
  mongo_init_bin='mongosh'
else
  mongo_init_bin='mongo'
fi
"${mongo_init_bin}" <<EOF
use ${MONGO_AUTHSOURCE}
db.auth("${MONGO_INITDB_ROOT_USERNAME}", "${MONGO_INITDB_ROOT_PASSWORD}")
db.createUser({
  user: "${MONGO_USER}",
  pwd: "${MONGO_PASS}",
  roles: [
    "clusterMonitor",
    { db: "${MONGO_DBNAME}", role: "dbOwner" },
    { db: "${MONGO_DBNAME}_stat", role: "dbOwner" },
    { db: "${MONGO_DBNAME}_audit", role: "dbOwner" },
    { db: "${MONGO_DBNAME}_restore", role: "dbOwner" }
  ]
})
EOF

Mount the sh file into your mongodb container, and make sure to set the env vars below with the same values you supplied to the Unifi container.
For example: ```yaml
unifi-db:
  image: docker.io/mongo:<version tag>
  container_name: unifi-db
  environment:
    - MONGO_INITDB_ROOT_USERNAME=root
    - MONGO_INITDB_ROOT_PASSWORD=
    - MONGO_USER=unifi
    - MONGO_PASS=
    - MONGO_DBNAME=unifi
    - MONGO_AUTHSOURCE=admin
  volumes:
    - /path/to/data:/data/db
    - /path/to/init-mongo.sh:/docker-entrypoint-initdb.d/init-mongo.sh:ro
  restart: unless-stopped
```
Note that the init script method will only work on first run. If you start the Mongodb container without an init script it will generate test data automatically and you will have to manually create your databases, or restart with a clean /data/db volume and an init script mounted.
You can also run the commands directly against the database using either mongo (< 6.0) or mongosh (>= 6.0).

Device Adoption

For Unifi to adopt other devices, e.g. an Access Point, it is required to change the inform IP address. Because Unifi runs inside Docker by default it uses an IP address not accessible by other devices. To change this go to Settings > System > Advanced and set the Inform Host to a hostname or IP address accessible by your devices. Additionally the checkbox "Override" has to be checked, so that devices can connect to the controller during adoption (devices use the inform-endpoint during adoption).
Note that you must use 8080:8080. If you MUST change the port, it must be changed on both sides and manually changed in your system.properties file. Otherwise, devices will initially communicate and then break after.
Please note, Unifi change the location of this option every few releases so if it's not where it says, search for "Inform" or "Inform Host" in the settings.
In order to manually adopt a device take these steps:
ssh ubnt@$AP-IP
set-inform http://$address:8080/inform

The default device password is ubnt. $address is the IP address of the host you are running this container on and $AP-IP is the Access Point IP address.
When using a Security Gateway (router) it could be that network connected devices are unable to obtain an ip address. This can be fixed by setting "DHCP Gateway IP", under Settings > Networks > networkname, to a correct (and accessible) ip address.

Migration From Unifi-Controller

If you were using the mongoless tag for the Unifi Controller container, you can switch directly to the Unifi Network Application container without needing to perform any migration steps.
You cannot perform an in-place upgrade from an existing Unifi-Controller container, you must run a backup and then a restore.
The simplest migration approach is to take a full backup of your existing install, including history, from the Unifi-Controller web UI, then shut down the old container.
You can then start up the new container with a clean /config mount (and a database container configured), and perform a restore using the setup wizard.

Strict reverse proxies

This image uses a self-signed certificate by default. This naturally means the scheme is https. If you are using a reverse proxy which validates certificates, you need to disable this check for the container.

Usage

To help you get started creating a container from this image you can either use docker-compose or the docker cli.
>!NOTE >Unless a parameter is flagged as 'optional', it is mandatory and a value must be provided.

docker-compose (recommended, click here for more info)

---
services:
  unifi-network-application:
    image: lscr.io/linuxserver/unifi-network-application:latest
    container_name: unifi-network-application
    environment:
      - PUID=1000
      - PGID=1000
      - TZ=Etc/UTC
      - MONGO_USER=unifi
      - MONGO_PASS=
      - MONGO_HOST=unifi-db
      - MONGO_PORT=27017
      - MONGO_DBNAME=unifi
      - MONGO_AUTHSOURCE=admin
      - MEM_LIMIT=1024 #optional
      - MEM_STARTUP=1024 #optional
      - MONGO_TLS= #optional
    volumes:
      - /path/to/unifi-network-application/data:/config
    ports:
      - 8443:8443
      - 3478:3478/udp
      - 10001:10001/udp
      - 8080:8080
      - 1900:1900/udp #optional
      - 8843:8843 #optional
      - 8880:8880 #optional
      - 6789:6789 #optional
      - 5514:5514/udp #optional
    restart: unless-stopped

docker cli (click here for more info)

docker run -d \
  --name=unifi-network-application \
  -e PUID=1000 \
  -e PGID=1000 \
  -e TZ=Etc/UTC \
  -e MONGO_USER=unifi \
  -e MONGO_PASS= \
  -e MONGO_HOST=unifi-db \
  -e MONGO_PORT=27017 \
  -e MONGO_DBNAME=unifi \
  -e MONGO_AUTHSOURCE=admin \
  -e MEM_LIMIT=1024 `#optional` \
  -e MEM_STARTUP=1024 `#optional` \
  -e MONGO_TLS= `#optional` \
  -p 8443:8443 \
  -p 3478:3478/udp \
  -p 10001:10001/udp \
  -p 8080:8080 \
  -p 1900:1900/udp `#optional` \
  -p 8843:8843 `#optional` \
  -p 8880:8880 `#optional` \
  -p 6789:6789 `#optional` \
  -p 5514:5514/udp `#optional` \
  -v /path/to/unifi-network-application/data:/config \
  --restart unless-stopped \
  lscr.io/linuxserver/unifi-network-application:latest

Parameters

Containers are configured using parameters passed at runtime (such as those above). These parameters are separated by a colon and indicate <external>:<internal> respectively. For example, -p 8080:80 would expose port 80 from inside the container to be accessible from the host's IP on port 8080 outside the container.
| Parameter | Function | | :----: | --- | | -p 8443:8443 | Unifi web admin port | | -p 3478:3478/udp | Unifi STUN port | | -p 10001:10001/udp | Required for AP discovery | | -p 8080:8080 | Required for device communication | | -p 1900/udp | Required for Make controller discoverable on L2 network option | | -p 8843 | Unifi guest portal HTTPS redirect port | | -p 8880 | Unifi guest portal HTTP redirect port | | -p 6789 | For mobile throughput test | | -p 5514/udp | Remote syslog port | | -e PUID=1000 | for UserID - see below for explanation | | -e PGID=1000 | for GroupID - see below for explanation | | -e TZ=Etc/UTC | specify a timezone to use, see this list. | | -e MONGO_USER=unifi | Mongodb Username. Only evaluated on first run. Special characters must be url encoded. | | -e MONGO_PASS= | Mongodb Password. Only evaluated on first run. Special characters must be url encoded. | | -e MONGO_HOST=unifi-db | Mongodb Hostname. Only evaluated on first run. | | -e MONGO_PORT=27017 | Mongodb Port. Only evaluated on first run. | | -e MONGO_DBNAME=unifi | Mongodb Database Name (stats DB is automatically suffixed with _stat). Only evaluated on first run. | | -e MONGO_AUTHSOURCE=admin | Mongodb authSource. For Atlas set to admin. Only evaluated on first run. | | -e MEM_LIMIT=1024 | Optionally change the Java memory limit (in Megabytes). Set to default to reset to default | | -e MEM_STARTUP=1024 | Optionally change the Java initial/minimum memory (in Megabytes). Set to default to reset to default | | -e MONGO_TLS= | Mongodb enable TLS. Only evaluated on first run. | | -v /config | Persistent config files |

Environment variables from files (Docker secrets)

You can set any environment variable from a file by using a special prepend FILE__.
As an example:
-e FILE__MYVAR=/run/secrets/mysecretvariable

Will set the environment variable MYVAR based on the contents of the /run/secrets/mysecretvariable file.

Umask for running applications

For all of our images we provide the ability to override the default umask settings for services started within the containers using the optional -e UMASK=022 setting. Keep in mind umask is not chmod it subtracts from permissions based on it's value it does not add. Please read up here before asking for support.

User / Group Identifiers

When using volumes (-v flags), permissions issues can arise between the host OS and the container, we avoid this issue by allowing you to specify the user PUID and group PGID.
Ensure any volume directories on the host are owned by the same user you specify and any permissions issues will vanish like magic.
In this instance PUID=1000 and PGID=1000, to find yours use id your_user as below:
id your_user

Example output:
uid=1000(your_user) gid=1000(your_user) groups=1000(your_user)

Docker Mods

Docker Mods Docker Universal Mods
We publish various Docker Mods to enable additional functionality within the containers. The list of Mods available for this image (if any) as well as universal mods that can be applied to any one of our images can be accessed via the dynamic badges above.

Support Info

  • Shell access whilst the container is running:
```bash
docker exec -it unifi-network-application /bin/bash
```
  • To monitor the logs of the container in realtime:
```bash
docker logs -f unifi-network-application
```
  • Container version number:
```bash
docker inspect -f '{{ index .Config.Labels "build_version" }}' unifi-network-application
```
  • Image version number:
```bash
docker inspect -f '{{ index .Config.Labels "build_version" }}' lscr.io/linuxserver/unifi-network-application:latest
```

Updating Info

Most of our images are static, versioned, and require an image update and container recreation to update the app inside. With some exceptions (noted in the relevant readme.md), we do not recommend or support updating apps inside the container. Please consult the Application Setup section above to see if it is recommended for the image.
Below are the instructions for updating containers:

Via Docker Compose

  • Update images:
* All images:

    ```bash
    docker-compose pull
    ```

* Single image:

    ```bash
    docker-compose pull unifi-network-application
    ```
  • Update containers:
* All containers:

    ```bash
    docker-compose up -d
    ```

* Single container:

    ```bash
    docker-compose up -d unifi-network-application
    ```
  • You can also remove the old dangling images:
```bash
docker image prune
```

Via Docker Run

  • Update the image:
```bash
docker pull lscr.io/linuxserver/unifi-network-application:latest
```
  • Stop the running container:
```bash
docker stop unifi-network-application
```
  • Delete the container:
```bash
docker rm unifi-network-application
```
  • Recreate a new container with the same docker run parameters as instructed above (if mapped correctly to a host folder, your /config folder and settings will be preserved)
  • You can also remove the old dangling images:
```bash
docker image prune
```

Image Update Notifications - Diun (Docker Image Update Notifier)

>!TIP >We recommend Diun for update notifications. Other tools that automatically update containers unattended are not recommended or supported.

Building locally

If you want to make local modifications to these images for development purposes or just to customize the logic:
git clone https://github.com/linuxserver/docker-unifi-network-application.git
cd docker-unifi-network-application
docker build \
  --no-cache \
  --pull \
  -t lscr.io/linuxserver/unifi-network-application:latest .

The ARM variants can be built on x8664 hardware and vice versa using lscr.io/linuxserver/qemu-static
docker run --rm --privileged lscr.io/linuxserver/qemu-static --reset

Once registered you can define the dockerfile to use with -f Dockerfile.aarch64.

Versions

  • 20.04.26: - Bump JRE to v25 to support v10.3+ of the application.
  • 20.10.25: - Switch to using FW API endpoint for version checks.
  • 08.05.25: - Update sample init-mongo.sh for compatibility with 9.1.120 (only affects new installs).
  • 13.02.25: - Revert JRE to 17.
  • 12.02.25: - Bump JRE to 21.
  • 11.08.24: - Important: The mongodb init instructions have been updated to enable auth (RBAC). We have been notified that if RBAC is not enabled, the official mongodb container allows remote access to the db contents over port 27017 without credentials. If you set up the mongodb container with the old instructions we provided, you should not map or expose port 27017. If you would like to enable auth, the easiest way is to create new instances of both unifi and mongodb with the new instructions and restore unifi from a backup.
  • 11.08.24: - Rebase to Ubuntu Noble.
  • 04.03.24: - Install from zip package instead of deb.
  • 17.10.23: - Add environment variables for TLS and authSource to support Atlas and new MongoDB versions.
  • 05.09.23: - Initial release.

Serve Unifi-network-application on your own domain behind Caddy, Nginx or Traefik. Fill in your domain and copy the result. It's a starting point, some apps need their own base URL or extra headers set too.

Proxying unifi-network-application.example.com to https://Unifi-network-application:8443

Add this to your Caddyfile

unifi-network-application.example.com {
	reverse_proxy https://Unifi-network-application:8443 {
		transport http {
			tls_insecure_skip_verify
		}
	}
}

Check the logs first

Nine times out of ten the logs tell you exactly what went wrong.

  • In Portainer, go to Containers, click the container, then Logs. Or run docker logs Unifi-network-application
  • Exit codes help too: 137 means killed, usually out of memory. 126 or 127 means the command inside the image is broken.

Port already in use

If deployment fails with "Bind for 0.0.0.0:8443 failed: port is already allocated", something else on your server is using that port.

  • Find what's using it: sudo ss -tlnp | grep :8443
  • Stop the other service, or pick a different host port. In 8443:8443 only the left number is yours to change, the right one belongs to the app.

Running but the page won't load

The container is up but nothing appears in your browser.

  • Use your server's real IP: http://your-server-ip:8080. The 0.0.0.0 link Portainer shows isn't a real address.
  • Give it a minute after first deploy, Unifi-network-application can take a while to initialise.
  • Make sure your firewall allows the port, e.g. sudo ufw allow 8080

Permission denied on volumes

If the logs show "permission denied", the app can't write to its data folder on the host.

  • Fix the ownership: sudo chown -R 1000:1000 /srv/lsio/unifi-network-application/config
  • Or set the PUID and PGID variables (defaults 1000:1000) to match your own user, found with id $USER

Image won't pull

Test the pull directly on the host: docker pull linuxserver/unifi-network-application:latest

  • "manifest unknown" means the tag no longer exists. This template uses latest, so try pinning a specific version instead.
  • "toomanyrequests" is the Docker Hub rate limit. Log in with docker login to raise it.
  • "no space left on device" means a full disk. Reclaim space with docker system prune

"exec format error"

This means the image was built for a different CPU architecture than your server.

  • This image supports: amd64, arm64
  • Check yours with uname -m: x86_64 is amd64, aarch64 is arm64. Raspberry Pi and other ARM boards are the usual culprits.

Container keeps restarting

The unless-stopped restart policy relaunches the app after every crash, so the real error can scroll past.

  • Check the logs right after a restart, the last few lines before it died are the useful ones.
  • Get the exit code with docker inspect Unifi-network-application --format '{{.State.ExitCode}}'
  • Still stuck? Redeploy once with the restart policy set to no so the failure stays visible.

Required settings are blank

MONGO_PASS, MONGO_TLS have no default value, and Unifi-network-application may crash or misbehave if left empty.

  • Fill them in on the deploy screen before hitting deploy.

Raise an issue

Found something which isn't working as it should? Here's how to report it.

Similar apps

Adguardhome-sync Adguardhome-sync NetworkCheckmate Checkmate NetworkDdclient Ddclient NetworkDuckdns Duckdns NetworkFail2ban Fail2ban Network iperf NetworkNetAlertX NetAlertX NetworkNginx Proxy Manager (stack) Nginx Proxy Manager (stack) Network