this post was submitted on 01 Nov 2023
1 points (100.0% liked)

Self-Hosted Main

589 readers
1 users here now

A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.

For Example

We welcome posts that include suggestions for good self-hosted alternatives to popular online services, how they are better, or how they give back control of your data. Also include hints and tips for less technical readers.

Useful Lists

founded 2 years ago
MODERATORS
communick@selfhosted.forum
1
Strange nginx proxy manager issue (alien.top)
submitted 2 years ago by williamwgant@alien.top to c/main@selfhosted.forum
1 comments fedilink hide all child comments
 

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.

top 1 comments
sorted by: hot top controversial new old
[โ€“] thekrautboy@alien.top 1 points 2 years 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