Unifi network controller: config.gateway.json

[mhobbelen]

How do i map my config.gateway.json file in the Unifi Network Controller container from linuxserver. I'm running the latest version (10.3.58) and mapped the /config folder in the container to a volume on my docker host (running ubuntu server lts). This doesn't work correctly (i see this because the seperate WAN subinterfaces aren't created for IPTV). Please help.

[j0nnymoe]

Probably best to explain what you've done first (with some examples of file locations etc) then people will be able to help.

[mhobbelen]

I've setup my docker-compose file like this:

services:
unifi-db:
image: docker.io/mongo:8.0
container_name: unifi-db
environment:
- PUID=1000
- PGID=1000
- TZ=America/Toronto
- MONGO_INITDB_ROOT_USERNAME=root
- MONGO_INITDB_ROOT_PASSWORD=xxxx
- MONGO_USER=unifi
- MONGO_PASS=xxxx
- MONGO_DBNAME=unifi
- MONGO_AUTHSOURCE=admin
volumes:
- db:/data/db
- ./init-mongo.sh:/docker-entrypoint-initdb.d/init-mongo.sh:ro
ports:
- 27017:27017
networks:
unifi_bridge:
aliases:
- unifi-db
restart: unless-stopped
unifi-network-application:
image: lscr.io/linuxserver/unifi-network-application:latest
container_name: unifi-network-application
environment:
- PUID=1000
- PGID=1000
- TZ=America/Toronto
- MONGO_USER=unifi
- MONGO_PASS=xxxx
- MONGO_HOST=unifi-db
- MONGO_PORT=27017
- MONGO_DBNAME=unifi
- MEM_LIMIT=1024 #optional
- MEM_STARTUP=1024 #optional
- MONGO_TLS= #optional
depends_on:
- unifi-db
volumes:
- config:/config
- data:/unifi/data
- run:/var/run/unifi
ports:
- 8443:8443
- 3478:3478/udp
- 10001:10001/udp
- 8080:8080
- 1900:1900/udp #optional
- 8844:8843 #optional
- 8880:8880 #optional
- 6789:6789 #optional
- 5514:5514/udp #optional
networks:
unifi_bridge:
aliases:
- unifi-network-application
restart: unless-stopped

volumes:
db:
config:
data:
run:

networks:
unifi_bridge:
driver: bridge

I've placed the config.gateway.json file in the config volume below /data/sites/default. For the data volume below sites/default.
HostOS: Distributor ID: Ubuntu
Description: Ubuntu 24.04.4 LTS
Release: 24.04
Codename: noble

Docker: Docker version 29.4.2, build 055a478

[drizuid]

config.gateway.json does indeed go in /config/data/sites/ this is how mine is for my parents and it works fine.
this that may be causing you issues if it is not working (looking from a container perspective, i will assume that you created the file correctly, which is out of scope for us)

• you're using volumes rather than bind mounts as recommended in our readme, i use bind mounts, no issues (note: volumes should NOT cause an issue, but you're seeking support while not following our recommendations, so it's mentioned)
• For data below sites/default. im not sure what this means, but if you are hoping that default indicates that this will cascade to other sites, that is not how unifi works, default is literally just the default site and nothing to do with other sites; there is no "data" below sites/default sites/default is just a single site.
• what is the output of snap list | grep docker

bear in mind, the config.gateway.json is VERY specific, indenting must be perfect, commands must be perfect, any error in this will cause the file to be ignored.

[mhobbelen]

Sorry, i've updated this line. This should be: For the data volume, below /sites/default.
I'm not referring to set this up for multiple sites.

The json file itself is correct. I've used this file for years and years on the image of jacobalberty (where the recommendation was to use volumes, that's why). I've used PI hardware for years, but due to the mongo upgrade, i've switched to x86. The json itself is a fork of coolhva (hans van achterberg - https://www.vanachterberg.org/usg-kpn-ftth/tabs/about/)

[mhobbelen]

mhobbelen@nuc-home:~/unifi$ snap list | grep docker
No snaps are installed yet. Try 'snap install hello-world'.

[drizuid]

good, low hanging fruit there, often ubuntu will default to a snap docker install which causes numerous issues.
I can only say config.gateway.json works fine on our container as i've been using one as long as we have offered a container (numerous years now) and you have it in the correct place. i would dig into the console to see what is going wrong. Also worth noting that afaik, only the USG even supports config.gateway.json, newer unifi routers dont at all or not fully (depending on which one)

[mhobbelen]

I know, i'm still using a good old usg3p. When it dies, i need to do switch over to something different. But i like this setup with a separate controller, not depended on the unifi hardware. However, when i run into issues, this isn't my first reaction ;-)

[j0nnymoe]

Also, why are you adding volumes for data & run when we don't list it in the readme?

[mhobbelen]

data was added by me, i was fiddling with the config. run not sure, i think i copied some stuff over from other people over the years.

[mhobbelen]

The owner of the config.gateway.json wasn't configured correctly. this is changed and now everything works. closing.