Greetings,

I started out by spinning up a number of docker-compose setups for various things. Initially, I set everything up with static IP addresses, but I later understood that nginx proxy manager can, if on the same network as a container, reference the container by hostname (or so I thought). However, after moving a few containers over to just being on the network, nginx now returns a bad gateway error on those containers. Am I just misunderstanding something? NGINX proxy manager is on that network as well (I just have one network for the moment). Any ideas of what I could be doing wrong?

​

Edit: A little more info. All the containers are mapped in nginx proxy manager using their hostname. Everything worked, until I stopped specifying a static IP for the containers. Then everything choked. It’s almost as if they disappeared off the docker network at that point, even though they were set to be on it.

  • thekrautboyBEnglish
    1·
    1 year ago

    When you say “by hostname” of the containers, are you using the exact containername of the target service?

    You can try to docker exec into the NPM container and from there ping the target container by its name, to confirm the connection itself works, if it does then the problem is somehow NPM itself i guess. Or the target container is not responding properly.

    /r/NginxProxyManager exists