Lack of DNS Resolution/Internet Connection causes NPM panel 'Bad Gateway' about nginx-proxy-manager HOT 4 OPEN

I have the same issue.
There seems to be no way to manually configure an IP address for DNS.

The configuration I have is:

• Docker PiHole connected to MacVLan.
• DHCP Server broadcasts PiHole MacVLan IP for DNS for all clients on the network.
• The Nginx Proxy manager in docker tries to use, but CANNOT see the IP address of the PiHole (MacVLan network is not accessible to other docker containers - by design)
• I have no way to tell NPM to use an alternate DNS IP.

Even if we have to edit a config file, it would be better than nothing.
An option in the GUI would also be great though!?

from nginx-proxy-manager.

@doublehelix why not just use the dns option in docker compose? You just add e.g dns: 192.168.1.5 on the same level as container_name, image, etc

from nginx-proxy-manager.

@doublehelix why not just use the dns option in docker compose? You just add e.g dns: 192.168.1.5 on the same level as container_name, image, etc

Unfortunately that doesn't work due to network isolation within docker containers and networks.
The only solution I've found so far is to network pihole on a macVLan and create a shared bridge that is used by all containers that need to use the DNS services in the pihole container (including nginx).
This has the unfortunate side effect that all docker containers are now networked together. Not ideal, and the opposite of the intention of isolation by default.

The other solution of course is to not host DNS in docker. (Which is the route I ended up taking in the meantime)

from nginx-proxy-manager.

all docker containers are now networked together.

You can setup firewall rules on that network to:

• accept anything to/from the pihole specific IP and ports you need
• drop everything else

That way they will not really be networked together, as the connection would be immediately dropped.

from nginx-proxy-manager.