[GH-ISSUE #1433] Pangolin can not connect to resoueses. #38702

Closed
opened 2026-06-22 01:58:16 -05:00 by GiteaMirror · 9 comments
Owner

Originally created by @krod1408 on GitHub (Sep 7, 2025).
Original GitHub issue: https://github.com/fosrl/pangolin/issues/1433

It seems that you loose all connections to you sites...not sure why but it seems to be dns related and this is not good. When you install everything works fine and out of no where it stops working is a problem...everything is correct so what is the problem...use a different domain? what is up?

Originally created by @krod1408 on GitHub (Sep 7, 2025). Original GitHub issue: https://github.com/fosrl/pangolin/issues/1433 It seems that you loose all connections to you sites...not sure why but it seems to be dns related and this is not good. When you install everything works fine and out of no where it stops working is a problem...everything is correct so what is the problem...use a different domain? what is up?
GiteaMirror added the stale label 2026-06-22 01:58:16 -05:00
Author
Owner

@krod1408 commented on GitHub (Sep 7, 2025):

I am suer that i am not the only one to say this.

<!-- gh-comment-id:3264160747 --> @krod1408 commented on GitHub (Sep 7, 2025): I am suer that i am not the only one to say this.
Author
Owner

@krod1408 commented on GitHub (Sep 8, 2025):

Weather or not i ca find a different solution is not the solution I will look for something that works as expected.

<!-- gh-comment-id:3264168517 --> @krod1408 commented on GitHub (Sep 8, 2025): Weather or not i ca find a different solution is not the solution I will look for something that works as expected.
Author
Owner

@krod1408 commented on GitHub (Sep 8, 2025):

Let me say this...this is a test vps...so its not a problem but what would happen it this happend on production and all of a sudden you needed a different domain.

<!-- gh-comment-id:3264170781 --> @krod1408 commented on GitHub (Sep 8, 2025): Let me say this...this is a test vps...so its not a problem but what would happen it this happend on production and all of a sudden you needed a different domain.
Author
Owner

@krod1408 commented on GitHub (Sep 8, 2025):

I M looking at this and it is corrcet

Starting proxy to 8096 proxy timed out....ok.

<!-- gh-comment-id:3264373994 --> @krod1408 commented on GitHub (Sep 8, 2025): I M looking at this and it is corrcet Starting proxy to 8096 proxy timed out....ok.
Author
Owner

@krod1408 commented on GitHub (Sep 8, 2025):

I know everything is correct still get error Newt o5osl88eoritw7u does not have Docker socket access

<!-- gh-comment-id:3264503217 --> @krod1408 commented on GitHub (Sep 8, 2025): I know everything is correct still get error Newt o5osl88eoritw7u does not have Docker socket access
Author
Owner

@Esa-mimbias commented on GitHub (Sep 8, 2025):

I know everything is correct still get error Newt o5osl88eoritw7u does not have Docker socket access

have you tried adding --docker-socket to newt command line ? for example (if docker is started by systemd) :

/usr/local/bin/newt --id <newtID> --secret <newtSecret> --endpoint <newtEndoint> --docker-socket /var/run/docker.sock
<!-- gh-comment-id:3266276997 --> @Esa-mimbias commented on GitHub (Sep 8, 2025): > I know everything is correct still get error Newt o5osl88eoritw7u does not have Docker socket access have you tried adding `--docker-socket` to newt command line ? for example (if docker is started by systemd) : ``` /usr/local/bin/newt --id <newtID> --secret <newtSecret> --endpoint <newtEndoint> --docker-socket /var/run/docker.sock ```
Author
Owner

@oschwartz10612 commented on GitHub (Sep 8, 2025):

Hi @krod1408 I understand the frustration and you have been posting around on some other threads. Lets keep troubleshooting on this thread.

As I asked on the other thread, could you please provide some sample logs from Pangolin and Newt from when you are unable to access a resource. I hope I can see something in these logs that will help me help you.

<!-- gh-comment-id:3268054504 --> @oschwartz10612 commented on GitHub (Sep 8, 2025): Hi @krod1408 I understand the frustration and you have been posting around on some other threads. Lets keep troubleshooting on this thread. As I asked on the other thread, could you please provide some sample logs from Pangolin and Newt from when you are unable to access a resource. I hope I can see something in these logs that will help me help you.
Author
Owner

@github-actions[bot] commented on GitHub (Sep 23, 2025):

This issue has been automatically marked as stale due to 14 days of inactivity. It will be closed in 14 days if no further activity occurs.

<!-- gh-comment-id:3321973254 --> @github-actions[bot] commented on GitHub (Sep 23, 2025): This issue has been automatically marked as stale due to 14 days of inactivity. It will be closed in 14 days if no further activity occurs.
Author
Owner

@github-actions[bot] commented on GitHub (Oct 7, 2025):

This issue has been automatically closed due to inactivity. If you believe this is still relevant, please open a new issue with up-to-date information.

<!-- gh-comment-id:3374722691 --> @github-actions[bot] commented on GitHub (Oct 7, 2025): This issue has been automatically closed due to inactivity. If you believe this is still relevant, please open a new issue with up-to-date information.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/pangolin#38702