github-starred/pangolin
2
0
Fork 0
mirror of https://github.com/fosrl/pangolin.git synced 2026-05-21 09:21:15 -05:00
Code Issues 856 Packages Projects Releases 74 Wiki Activity

[GH-ISSUE #1028] No route to host for all serives #1728

New Issue
Closed
opened 2026-04-16 08:30:21 -05:00 by GiteaMirror · 2 comments
GiteaMirror commented 2026-04-16 08:30:21 -05:00
Owner
Copy Link

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?

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?
GiteaMirror commented 2026-04-16 08:30:23 -05:00
Author
Owner
Copy Link

@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!
GiteaMirror commented 2026-04-16 08:30:23 -05:00
Author
Owner
Copy Link

@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 :(

<!-- 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 :(
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
api
authentication
bug
config
dependencies
docker
documentation
enhancement
good first issue
help wanted
Improvement
Look Into
needs investigating
networking
new feature
non-critical bug
potential bug
pull-request
Mirrored from GitHub Pull Request
 question
reverse proxy
Security
stale
ui
wontfix
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/pangolin#1728
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?