mirror of
https://github.com/fosrl/pangolin.git
synced 2026-05-27 08:36:30 -05:00
[GH-ISSUE #2375] Newt cannot connect to the Pangolin network. #17138
No Assignees
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: github-starred/pangolin#17138
Reference in New Issue
Block a user
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?
Originally created by @jack9603301 on GitHub (Jan 29, 2026).
Original GitHub issue: https://github.com/fosrl/pangolin/issues/2375
Describe the Bug
This is a very strange problem, and the following characteristics have been observed:
pangolin vps log(docker compose logs -f)
newt log:
Environment
The topology uses a two-layer proxy topology:
VPS -> NPM -> LXD (Docker) -> Pangolin
To Reproduce
The investigation is still ongoing, but he should be able to connect to the network normally. I've been testing it for two days, and the port hasn't been blocked.
Expected Behavior
Newt cannot connect to the Pangolin network.
@jack9603301 commented on GitHub (Jan 29, 2026):
I reinstalled it, simplified the topology, and changed two ports. Now it can connect to the network via newt, but the downside is that another problem has arisen: the client cannot connect.
Log:
[warn]: Client last hole punch is too old and we have sites to send; skipping this register
@bazziebaz commented on GitHub (Feb 7, 2026):
Having similar issues on Oracle free VPS. All security list are rules in place (TCP 80+443 UDP 51820+21820), netcat tests from newt docker container all ok, but no luck.
Now, did this test: on VPS security list: open up all IPs and all protocols -> SUCCESS! As if there is one more undocumented port which is also needed? After site is up I can remove the all-rule and it seems to keep on working.
@geek1o commented on GitHub (Feb 8, 2026):
I have exactly the same problem as bazziebaz, the only thing that helps is completely disabling the firewall, although the necessary ports are open.
@Xerionty commented on GitHub (Feb 10, 2026):
Came here because I experience the same issue.
@jack9603301 commented on GitHub (Feb 11, 2026):
I am testing on another server that is located in the same country as me, so I think it should be normal. Let me test it. Perhaps the previous error was caused by interference with UDP traffic or poor network quality conditions
@jack9603301 commented on GitHub (Feb 11, 2026):
I am testing on another server that is located in the same country as me, so I think it should be normal. Let me test it. Perhaps the previous error was caused by interference with UDP traffic or poor network quality conditions
@schtinkafinga commented on GitHub (Feb 14, 2026):
In Cloud console you have to set your firewall ingress to allow all UDP ports
@github-actions[bot] commented on GitHub (Mar 1, 2026):
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.
@github-actions[bot] commented on GitHub (Mar 15, 2026):
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.