[GH-ISSUE #2557] Cannot reach private resource in Docker network #2188

New Issue

GiteaMirror · 2026-04-16T09:13:35-05:00

GiteaMirror commented

2026-04-16 09:13:35 -05:00

Originally created by @kreativekrise on GitHub (Feb 27, 2026).
Original GitHub issue: https://github.com/fosrl/pangolin/issues/2557

Describe the Bug

I set up a private resource to access a Nginx Docker container via a Newt tunnel. Both containers are running in the same external Docker network, and Newt can reach Nginx on the console. However, I'm unable to access the Nginx container using the container name or its IP when in "Host" mode. DNS resolution works (dig nginx.internal resolves to an IP), but I can't actually reach the container. Both curl http://<IP_OR_ALIAS>:80 and ping <IP> result in timeouts.

When I switch the private resource mode to CIDR and provide the Docker network range, I can access the container using its IP, indicating that connectivity exists, but the "Host" mode is not functioning as expected.

Environment

OS Type & Version: Ubuntu 24.04
Pangolin Version: 1.15.4
Gerbil Version: 1.3.0
Traefik Version: 3.6
Newt Version: 1.10.0
Pangolin-CLI Version: 0.3.3

To Reproduce

Set up a Docker network with multiple containers, including a Nginx container.
Use Newt to set up a private resource to access the Nginx container, using either the container name or IP as the host target.
Attempt to access the Nginx container via curl or ping.
Observe that the connection times out.
Switch the private resource mode from "Host" to CIDR and enter the Docker network range.
Attempt to access the Nginx container again and confirm that it is accessible.

Expected Behavior

I expect to be able to access the Nginx container using either its container name or IP address when the private resource is set to "Host" mode, similar to the behavior when using CIDR mode.

Originally created by @kreativekrise on GitHub (Feb 27, 2026). Original GitHub issue: https://github.com/fosrl/pangolin/issues/2557 ### Describe the Bug I set up a private resource to access a Nginx Docker container via a Newt tunnel. Both containers are running in the same external Docker network, and Newt can reach Nginx on the console. However, I'm unable to access the Nginx container using the container name or its IP when in "Host" mode. DNS resolution works (`dig nginx.internal` resolves to an IP), but I can't actually reach the container. Both `curl http://<IP_OR_ALIAS>:80` and `ping <IP>` result in timeouts. When I switch the private resource mode to CIDR and provide the Docker network range, I can access the container using its IP, indicating that connectivity exists, but the "Host" mode is not functioning as expected. ### Environment - OS Type & Version: Ubuntu 24.04 - Pangolin Version: 1.15.4 - Gerbil Version: 1.3.0 - Traefik Version: 3.6 - Newt Version: 1.10.0 - Pangolin-CLI Version: 0.3.3 ### To Reproduce 1. Set up a Docker network with multiple containers, including a Nginx container. 2. Use Newt to set up a private resource to access the Nginx container, using either the container name or IP as the host target. 3. Attempt to access the Nginx container via `curl` or `ping`. 4. Observe that the connection times out. 5. Switch the private resource mode from "Host" to CIDR and enter the Docker network range. 6. Attempt to access the Nginx container again and confirm that it is accessible. ### Expected Behavior I expect to be able to access the Nginx container using either its container name or IP address when the private resource is set to "Host" mode, similar to the behavior when using CIDR mode.

GiteaMirror closed this issue

2026-04-16 09:13:36 -05:00

GiteaMirror commented

2026-04-16 09:13:36 -05:00

@kreativekrise commented on GitHub (Mar 1, 2026):

It just started working. Nothing was changed.

@kreativekrise commented on GitHub (Mar 1, 2026): It just started working. Nothing was changed.

GiteaMirror referenced this issue

2026-04-20 08:26:38 -05:00

[GH-ISSUE #2188] OICD broken #4034

GiteaMirror referenced this issue

2026-04-25 15:53:20 -05:00