Ever since using the new Network Application image (vs the deprecated unifi-controller), the application no longer find new updated firmware releases or flags for an updated application.
using the deprecated image, I used to get both notifications and I was able to simply update the device firmware and if there was new application version I could pull a new image.
Now I have to manually search through ui.com and manually update firmware using the url and if manually search and find out if there is a new version of the application released.
Any help is appreciated. Thanks.
driz
4 October 2024 18:20
2
Please could you provide the following information so we can help with supporting your issue:
Output of uname -mr && docker version
Output of cat /etc/os-release
Docker run command or compose snippet
Container logs beginning with our logo (rules 5)
Someone reported this issue on our discord earlier this week and the problem was caused by SSL certs they’d injected into the container.
With a default deployment of the container, we’re unable to replicated. Post your compose / container logs / unifi server logs.
uname -r : 5.10.0-32-amd64
docker version:
Client: Docker Engine - Community
Version: 27.1.2
API version: 1.46
Go version: go1.21.13
Git commit: d01f264
Built: Mon Aug 12 11:51:13 2024
OS/Arch: linux/amd64
Context: default
Server: Docker Engine - Community
Engine:
Version: 27.1.2
API version: 1.46 (minimum version 1.24)
Go version: go1.21.13
Git commit: f9522e5
Built: Mon Aug 12 11:51:13 2024
OS/Arch: linux/amd64
Experimental: false
containerd:
Version: 1.7.20
GitCommit: 8fc6bcff51318944179630522a095cc9dbf9f353
runc:
Version: 1.1.13
GitCommit: v1.1.13-0-g58aa920
docker-init:
Version: 0.19.0
GitCommit: de40ad0
cat /etc/os-release:
PRETTY_NAME="Debian GNU/Linux 11 (bullseye)"
NAME="Debian GNU/Linux"
VERSION_ID="11"
VERSION="11 (bullseye)"
VERSION_CODENAME=bullseye
ID=debian
HOME_URL="https://www.debian.org/"
SUPPORT_URL="https://www.debian.org/support"
BUG_REPORT_URL="https://bugs.debian.org/"
run command: sudo docker-compose -f unifi-network-application.yml up -d
yml content:
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=unifipwd123
- MONGO_HOST=unifi-db
- MONGO_PORT=27017
- MONGO_DBNAME=unifi
- MONGO_AUTHSOURCE=admin
volumes:
- /opt/unifi:/config
ports:
- 8080:8080
- 8443:8443
- 8843:8843
- 6789:6789
- 3478:3478/udp
restart: unless-stopped
depends_on:
- unifi-db
unifi-db:
image: docker.io/mongo:4.4-focal
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:
- /opt/mongo/data:/data/db
- /opt/mongo/init-mongo.sh:/docker-entrypoint-initdb.d/init-mongo.sh:ro
restart: unless-stopped
Container logs:(not sure if there is another way of getting logs as this seems to be empty)
$ sudo docker logs -f unifi-network-application
[migrations] started
[migrations] no migrations found
───────────────────────────────────────
██╗ ███████╗██╗ ██████╗
██║ ██╔════╝██║██╔═══██╗
██║ ███████╗██║██║ ██║
██║ ╚════██║██║██║ ██║
███████╗███████║██║╚██████╔╝
╚══════╝╚══════╝╚═╝ ╚═════╝
Brought to you by linuxserver.io
───────────────────────────────────────
To support LSIO projects visit:
https://www.linuxserver.io/donate/
───────────────────────────────────────
GID/UID
───────────────────────────────────────
User UID: 1000
User GID: 1000
───────────────────────────────────────
Linuxserver.io version: 8.4.62-ls66
Build-date: 2024-10-01T17:37:31+00:00
───────────────────────────────────────
[custom-init] No custom files found, skipping...
[ls.io-init] done.
Any updates on this from the logs that I provided a while back?
driz
8 November 2024 16:00
6
your container logs show no issues and you’re the only user to ever report this behavior.
Thank you for confirming that there were no issue with the setup. That led me to explore options that would be unique to my setup. After a bunch of digging I found out that the issue was rising from the DNS.
The nameserver that is inserted into the Unifi container from the host was the host itself. I host a private nameserver on the server that I host the docker container. This was causing issues. since the Unifi does not need to know about my private namespace, adding a
dns = 8.8.8.8
into the compose yml file fixed the issue.