Taramu

Got it working instantly on my Unraid machine with following parameters: https://github.com/lemker/unifi-os-server/blob/main/docker-compose.yaml On the contra side it requires "Privileged" permission and also does not run with extra parameters "--user 99:100" Some more tweaking might be required and also better path names I guess. Screenshot from my working Unraid docker template:

A working docker container for Unifi OS Server seems to exist already: https://github.com/lemker/unifi-os-server Would be nice to get your view on it Pete, might this be a good base for an upcoming project with Unraid support?

Since updating to v7.2.4 my server icon is missing, can this be fixed somehow? Choosing a different server icon does not work permanently:

Starting with 10.1.85 following message comes up after each login. Is possible to permanently disable that message?

I would also like to stay with the docker container. It's less ressource intensive than a VM and easy to deploy.

Wow, thanks for checking the firmware for each model. I was on my way to reset everything but based on your reply it doesn't seem required. For now I will just wait for the next updates being released for my systems and wait. Really appreicate your work, it's the best Unifi release for Unraid available. Edit: Also found the website with firmwares listed for each model. Might be interesting for someone else. https://ui.com/download/releases/firmware

Thanks for the quick reply! My controller is running firmware 9.0.114-unraid and devices didn't receive updates for many months. The only restriction I have on my Unraid template is that only port 8080 is opened, which is used to manage my devices. All other ports were disabled in my Unraid template. I installed a new USW Flex 2.5G switch today which came with FW 2.0.5, but newer FW releases are available: https://community.ui.com/releases/UniFi-Switch-Flex-2-5G-8-2-1-5/2052fc64-571c-4e39-9354-3c3759ff8c63 Also I have some Unifi 6 Pro APs running on 6.6.77, but 6.6.78 is available since a long time: https://community.ui.com/releases/UniFi-Access-Point-6-6-78/b0097366-3989-47b8-b46a-13d36aefa96b On my DNS servers I see that all DNS requests by the UniFi controller are successfully answered without any issues. From the controller itself I'm also able to resolve DNS entries and reach the internet without restrictions.

Did anyone face the issue that the Controller does not find firmware updates for devices? I have multiple Unifi 6 APs and a USW Flex Switch which all are running with an old firmware. When clicking "Check for Updates" for in Settings -> Device Firmware I get the result no updates avilable, my controller is able to reach the internet and correctly resolves a DNS entry to fw-update.ubnt.com. I don't get the issue.

Found the issue reason for the unhealthy state: https://github.com/0xERR0R/blocky/issues/1666 Since I binded port 53 to a specific IP in my config.yml, above issue is occuring. The image by itself is doing health checks. My solution was to disable the health check in Unraid container settings: - Edit the blocky docker container in Unraid - Add "--no-healthcheck" under Extra Parameters - Save and restart the container Thanks for building this Unraid template. The developer of blocky did an awesome job, DNS requests in my network are instant now and faster than before when I was using Pihole and Adguard Home.

Hello, I'm using your blocky template and it works fine. Recently I noticed that Unraid always displays docker health "unhealthy" for the blocky container (see screenshot attached). In the logs of the blocky container I see no issues, does someone have an idea how to fix?

Thanks for the updates as always, really appreciate them. Would be great though if "latest" version tags could be added for each stream (home/company/critical for unraid and non-unraid versions). That would allow automatic updates without manual user interactions to change the version and fix CVEs automatically.

Can someone help me to get Obsidian Livesync running with the CouchDB database on Unraid? I'm trying to follow this guide which requires a "local.ini" with the configuration shown: https://github.com/vrtmrz/obsidian-livesync/blob/main/docs/setup_own_server.md The issue is, that I don't understand where to place the local.ini inside this CouchDB docker container. It seems like a local.ini file already exists in this container under /opt/couchdb/etc/ But this directory is not mounted inside my appdata folder. Would be really great to get some help, I'm struggling since hours.

EDIT: I was able to fix this. The issue seemed to be that I was using a deprecated user template with my settings, which were not compatible with the latest release of NGINX Proxy Manager. Installing the application with the new template from Community Applications fixed it. Hello, I have an issue where NGINX Proxy Manager is completely ignoring my Port Mapping with a custom docker network. For Unraids WebUI, I changed the default ports 80 to 81 and 443 to 444 and used Port 80 and Port 443 exclusively for NGINX Proxy Manager successfully for multiple years. Yesterday I updated to Unraid 6.11 and since then NGINX Proxy Manager only responds to ports 8080 and 4443. No matter what ports I enter and which network is assigned, only those ports are answering. Downgrading to Unraid 6.10.3 didn't help. Re-deploying NXING Proxy Manager with a fresh config (deleted my config folder before) also didn't help. My configuration looks like following: The issue is not happening with other containers, where custom ports are working when I add them to my proxynet network. Might this be an issue with the latest release or is there some way to fix this?

EDIT: I was able to fix this. The issue seemed to be that I was using a deprecated user template with my settings, which were not compatible with the latest release of NGINX Proxy Manager. Installing the application with the new template from Community Applications fixed it. Hello, I'm using Unraid since a few years without any hiccups, since I updated to version 6.11 I'm having many problems with my Docker containers. Downgrading to 6.10.3 didn't help and a reinstallation also didn't fix the issue. I created a custom network "docker network create proxynet" which I assign to all of my Reverse proxied docker containers. NGINX Proxy Manager is used as my Reverse Proxy and it ran perfectly, now all of my proxied Docker containers are not reachable anymore. The issue seems to be, that NGINX Proxy Manager is not reachable via Port 80 and Port 443, which is the configuration in my template. Instead the Webserver only replies to Ports 8080 and 4443. This is my config, but no matter what ports I'm entering the values are not working: Does anyone have an idea how I can force the container to use Port 80 and 443 again? I'm only having this issue with this specific docker container, for others port mapping is working.

Hello, I have the same problem. My br0 interface is not working with VMs and Docker Containers, any fix for this? For Docker Containers only my eth0 interface (bridging disabled) and my custom docker networks (like proxynet for my NGINX webserver )are working. Setting br0 to docker containers does not work, even if "Host access to custom networks" is enabled. My network card is an Asus XG-C100F with an AQC107 chipset.

Same issue for me

EDIT: Had a network wide issue because of DHCP snooping. My switches blocked the requests, whitelisting the switchports fixed it. Does Pihole work as DHCP server work for someone? I can't get it to work since hours, tried everything. No other DHCP server in my network. I tried setting the container to following network interfaces: - host with Unraid Server IP: DHCP Request of client won't get answered, client disconnects. I can see the client IP / MAC in Pihole. Client chooses APIPA address (169.x.x.x) - br0 with custom IP in client subnet: Same as with host, can see the client IP / MAC but client gets disconnected. Client chooses APIPA (169.x.x.x). Everything besides DHCP works. I don't know why it doesn't work. Same issue with Adguard Home.