[GH-ISSUE #96] Proxy to other docker containers #85

New issue

Closed

opened 2026-02-26 05:34:17 +03:00 by kerem · 1 comment

kerem commented

2026-02-26 05:34:17 +03:00

Owner

Originally created by @jrichet on GitHub (Mar 6, 2019).
Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/96

How do I connect to other docker containers?

I've tried connecting to localhost/127.0.0.1 on an alternate port exposed in those containers, but no joy. Is there a trick I'm not aware of?

I keep getting a 502.

It would be super helpful if the documentation included some troubleshooting tips

Originally created by @jrichet on GitHub (Mar 6, 2019). Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/96 How do I connect to other docker containers? I've tried connecting to localhost/127.0.0.1 on an alternate port exposed in those containers, but no joy. Is there a trick I'm not aware of? I keep getting a 502. It would be super helpful if the documentation included some troubleshooting tips

kerem

2026-02-26 05:34:17 +03:00

closed this issue
added the
product-support
label

kerem commented

2026-02-26 05:34:18 +03:00

Author

Owner

@jc21 commented on GitHub (Mar 6, 2019):

I assume you're running your NPM docker image in bridge mode, which is the default. In this mode 127.0.0.1 only connects back to the NPM docker image network stack, not the host machine.

You have 3 options:

Run NPM in host mode.
Add your other services to the bridge network stack: add them as services in the docker-compose.yml file and connect to them using the service name as the hostname.
Connect to your other services by the machine's host IP address on the local network, ie: 192.168.1.50.

@jc21 commented on GitHub (Mar 6, 2019): I assume you're running your NPM docker image in `bridge` mode, which is the default. In this mode `127.0.0.1` only connects back to the NPM docker image network stack, not the host machine. You have 3 options: 1. Run NPM in [`host` mode](https://docs.docker.com/network/host/). 2. Add your other services to the bridge network stack: add them as services in the `docker-compose.yml` file and connect to them using the service name as the hostname. 3. Connect to your other services by the machine's host IP address on the local network, ie: 192.168.1.50.

kerem referenced this issue

2026-02-26 05:34:38 +03:00

[GH-ISSUE #120] Cloudflare DNS Lets Encrypt #106

kerem referenced this issue

2026-02-26 05:34:38 +03:00

[GH-ISSUE #120] Cloudflare DNS Lets Encrypt #106

kerem referenced this issue

2026-02-26 05:34:38 +03:00

[GH-ISSUE #120] Cloudflare DNS Lets Encrypt #106

kerem referenced this issue

2026-02-26 05:34:38 +03:00

[GH-ISSUE #120] Cloudflare DNS Lets Encrypt #106