[GH-ISSUE #411] Newt logs : Error connecting to target: dial tcp IP:port: connect: connection refused #1435

New Issue

GiteaMirror · 2026-04-16T08:04:29-05:00

GiteaMirror commented

2026-04-16 08:04:29 -05:00

Originally created by @davidszerman on GitHub (Mar 26, 2025).
Original GitHub issue: https://github.com/fosrl/pangolin/issues/411

Hello,

i created a new site connected to Pangolin via Newt

On Pangolin, I can see that the site is connected

I try to create a ressource on the distant site

When i connect via web browser to the ressource, I have this error message in the newt logs 👍
ERROR: 2025/03/26 16:49:59 Error connecting to target: dial tcp IP:PORT: connect: connection refused

Any idea ?
What IP should I write ? 127.0.0.1 ? The newt docker IP ? Any other ?

Any of them works

Did I miss something ?

Thanks

Originally created by @davidszerman on GitHub (Mar 26, 2025). Original GitHub issue: https://github.com/fosrl/pangolin/issues/411 Hello, i created a new site connected to Pangolin via Newt On Pangolin, I can see that the site is connected I try to create a ressource on the distant site When i connect via web browser to the ressource, I have this error message in the newt logs 👍 ERROR: 2025/03/26 16:49:59 Error connecting to target: dial tcp IP:PORT: connect: connection refused Any idea ? What IP should I write ? 127.0.0.1 ? The newt docker IP ? Any other ? Any of them works Did I miss something ? Thanks

GiteaMirror closed this issue

2026-04-16 08:04:29 -05:00

GiteaMirror commented

2026-04-16 08:04:30 -05:00

@miloschwartz commented on GitHub (Mar 26, 2025):

This seems like Newt is unable to address the target of the resource on the network.

Note about using localhost:

If Newt is running in a container, then 127.0.0.1 or localhost will refer to the container itself, not the container's host machine. If the resources are running in the same Docker network as Newt, you can use the container name as the hostname. Otherwise, you can use the special Docker address 172.17.0.1 which will address the bare metal host itself.

Alternatively, you can use the IP of the host on the LAN. For example, if you're running Newt on an Unraid machine with internal address 192.168.1.81, and the resources are exposed at 192.168.1.81:8080, you could use this as the target in Pangolin.

@miloschwartz commented on GitHub (Mar 26, 2025): This seems like Newt is unable to address the target of the resource on the network. Note about using localhost: If Newt is running in a container, then `127.0.0.1` or `localhost` will refer to the container itself, not the container's host machine. If the resources are running in the same Docker network as Newt, you can use the container name as the hostname. Otherwise, you can use the special Docker address `172.17.0.1` which will address the bare metal host itself. Alternatively, you can use the IP of the host on the LAN. For example, if you're running Newt on an Unraid machine with internal address `192.168.1.81`, and the resources are exposed at `192.168.1.81:8080`, you could use this as the target in Pangolin.

GiteaMirror commented

2026-04-16 08:04:30 -05:00

@Boerny41 commented on GitHub (Mar 27, 2025):

Pretty much what @miloschwartz said, however, not all containers seem to work when addressing them via their docker hostname.

I've got a few containers that show Error connecting to target: dial tcp 172.21.0.3:8764: connect: connection refused when entering their hostname in the pangolin web UI. For these containers, I had to enter the 192.168.0.0/24 address. Don't forget to allow the port of said services it in the firewall of your docker server.

I'm not sure what the problem is, but some containers just don't seem to like how pangolin handles the connection.

@Boerny41 commented on GitHub (Mar 27, 2025): Pretty much what @miloschwartz said, however, not all containers seem to work when addressing them via their docker hostname. I've got a few containers that show `Error connecting to target: dial tcp 172.21.0.3:8764: connect: connection refused` when entering their hostname in the pangolin web UI. For these containers, I had to enter the 192.168.0.0/24 address. Don't forget to allow the port of said services it in the firewall of your docker server. I'm not sure what the problem is, but some containers just don't seem to like how pangolin handles the connection.

GiteaMirror commented

2026-04-16 08:04:31 -05:00

@davidszerman commented on GitHub (Mar 28, 2025):

Hi

Thank you both !

Indeed, the 172.17.0.1 address worked !

That is great ! !

Thanks

@davidszerman commented on GitHub (Mar 28, 2025): Hi Thank you both ! Indeed, the 172.17.0.1 address worked ! That is great ! ! Thanks

GiteaMirror commented

2026-04-16 08:04:31 -05:00

@miloschwartz commented on GitHub (Mar 28, 2025):

@davidszerman Awesome!

@miloschwartz commented on GitHub (Mar 28, 2025): @davidszerman Awesome!

GiteaMirror referenced this issue

2026-04-16 09:28:24 -05:00

[PR #1435] [MERGED] Bump actions/setup-go from 5 to 6 #2551

GiteaMirror referenced this issue

2026-04-20 08:54:13 -05:00

[PR #1435] [MERGED] Bump actions/setup-go from 5 to 6 #4494

GiteaMirror referenced this issue