Hi,
all of a sudden all my services no longer work. I am on version 1.6.2
In traefik, all I get when trying to connect is 2025-07-07T15:46:15Z DBG httputil/proxy.go:121 > 502 Bad Gateway | error=dial tcp x.x.x.x:53007: connect: no route to host
In the newt docker container, I have ERROR: 2025/07/07 15:53:31 Failed to connect: failed to get token: failed to request new token: Post "https://example.org/api/v1/auth/newt/get-token": dial tcp: lookup example.org on 127.0.0.11:53: server misbehaving. Retrying in 10s...
What went wrong here?
Originally created by @juxeii on GitHub (Jul 7, 2025).
Original GitHub issue: https://github.com/fosrl/pangolin/issues/1028
Hi,
all of a sudden all my services no longer work. I am on version `1.6.2`
In `traefik`, all I get when trying to connect is
`2025-07-07T15:46:15Z DBG httputil/proxy.go:121 > 502 Bad Gateway | error=dial tcp x.x.x.x:53007: connect: no route to host`
In the `newt `docker container, I have
`ERROR: 2025/07/07 15:53:31 Failed to connect: failed to get token: failed to request new token: Post "https://example.org/api/v1/auth/newt/get-token": dial tcp: lookup example.org on 127.0.0.11:53: server misbehaving. Retrying in 10s...`
What went wrong here?
@oschwartz10612 commented on GitHub (Jul 7, 2025):
Hum I am sorry you are having this issue. You are definitly getting the bad gateway because newt is not connected. The question is why is newt not able to connect.
It looks like a DNS issue.
The error message "lookup example.org on 127.0.0.11:53: server misbehaving" indicates it is trying to resolve example.org (your domain) using a DNS resolver at 127.0.0.11:53, and that server isn't responding correctly.
This IP (127.0.0.11) often points to an internal DNS service, common in Docker containers or similar environments.
To troubleshoot:
Check /etc/resolv.conf within your application's environment (especially if it's a Docker container).
Test DNS resolution from within the environment (e.g., nslookup example.org).
Verify the health and configuration of your DNS server at 127.0.0.11 (or whatever it's proxying to).
Consider temporarily configuring a public DNS server (like 8.8.8.8) to see if that resolves the issue!
<!-- gh-comment-id:3045768677 -->
@oschwartz10612 commented on GitHub (Jul 7, 2025):
Hum I am sorry you are having this issue. You are definitly getting the bad gateway because newt is not connected. The question is why is newt not able to connect.
It looks like a DNS issue.
The error message "lookup example.org on 127.0.0.11:53: server misbehaving" indicates it is trying to resolve example.org (your domain) using a DNS resolver at 127.0.0.11:53, and that server isn't responding correctly.
This IP (127.0.0.11) often points to an internal DNS service, common in Docker containers or similar environments.
To troubleshoot:
Check /etc/resolv.conf within your application's environment (especially if it's a Docker container).
Test DNS resolution from within the environment (e.g., nslookup example.org).
Verify the health and configuration of your DNS server at 127.0.0.11 (or whatever it's proxying to).
Consider temporarily configuring a public DNS server (like 8.8.8.8) to see if that resolves the issue!
@oschwartz10612 Thank you so much for your help. But I just figured out, that my NAS somehow lost connection to my DNS server. That was simple to fix. Sorry again for confusion :(
<!-- gh-comment-id:3045804889 -->
@juxeii commented on GitHub (Jul 7, 2025):
@oschwartz10612 Thank you so much for your help. But I just figured out, that my NAS somehow lost connection to my DNS server. That was simple to fix. Sorry again for confusion :(
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Originally created by @juxeii on GitHub (Jul 7, 2025).
Original GitHub issue: https://github.com/fosrl/pangolin/issues/1028
Hi,
all of a sudden all my services no longer work. I am on version
1.6.2In
traefik, all I get when trying to connect is2025-07-07T15:46:15Z DBG httputil/proxy.go:121 > 502 Bad Gateway | error=dial tcp x.x.x.x:53007: connect: no route to hostIn the
newtdocker container, I haveERROR: 2025/07/07 15:53:31 Failed to connect: failed to get token: failed to request new token: Post "https://example.org/api/v1/auth/newt/get-token": dial tcp: lookup example.org on 127.0.0.11:53: server misbehaving. Retrying in 10s...What went wrong here?
@oschwartz10612 commented on GitHub (Jul 7, 2025):
Hum I am sorry you are having this issue. You are definitly getting the bad gateway because newt is not connected. The question is why is newt not able to connect.
It looks like a DNS issue.
The error message "lookup example.org on 127.0.0.11:53: server misbehaving" indicates it is trying to resolve example.org (your domain) using a DNS resolver at 127.0.0.11:53, and that server isn't responding correctly.
This IP (127.0.0.11) often points to an internal DNS service, common in Docker containers or similar environments.
To troubleshoot:
@juxeii commented on GitHub (Jul 7, 2025):
@oschwartz10612 Thank you so much for your help. But I just figured out, that my NAS somehow lost connection to my DNS server. That was simple to fix. Sorry again for confusion :(