I’ve running AdGuard Home and Nginx Proxy Manager as Docker-based apps on TrueNAS SCALE Electric Eel on IP address 10.10.10.2. Thus, I’ve added this IP address as name server to my router as well as nameserver 1 and 2 in the TrueNAS network configuration.
Starting the Nginx Proxy Manager will now stuck in “deploying”, because the Let’s Encrypt ACME certificate script will now fail with [Errno -3] Temporary failure in name resolution.
As soon as I change a nameserver in TrueNAS to e.g. 9.9.9.9 and start the Nginx Proxy Manager, it works fine.
How can get it working that the Nginx Proxy Manager app can access the local DNS server of the AdGuard Home app to make DNS resolutions?
Just curious… why do you have everything going through AdGuard Home? It’s anti-ad blocking and tracking server, but I have it set to apply to the DHCP addresses in my network. The apps in TrueNAS SCALE get their DNS settings from the TrueNAS server, and I have mine go through 208.67.222.222 and 208.67.220.220 to avoid this type of issue.
Have you checked the AdGuard Home on the Blocked domains to see what is being blocked and possibly placing that domain in the allow list?
I simply want to also block any tracking within apps, which does happen, depending on the app. That’s why I also want to use it internally.
It seemed to me that the NPM container couldn’t even connect to 10.10.10.2. Unfortunately, due to the restrictive Docker container, I couldn’t test a ping or dig command.
