Originally assigned to: @oschwartz10612 on GitHub.
Describe the Bug
My Pangolin node is on a box with a dynamic ip-address.
When that node gets a new ip (once a day), the newt-tunnels lose connection.
Apparently they ping to the old ip-address, whereas configured with a dns-name.
Re-checked with the current newt-version.
Environment
OS Type & Version: (e.g., Ubuntu 22.04)
Pangolin Version: 1.11.0 CE
Newt Version: 1.6.0
To Reproduce
Simply change the ip-address of the pangolin node while running.
Expected Behavior
Newt tunnels should recover and use the new ip-
Originally created by @sqrt-1764 on GitHub (Oct 28, 2025).
Original GitHub issue: https://github.com/fosrl/pangolin/issues/1766
Originally assigned to: @oschwartz10612 on GitHub.
### Describe the Bug
My Pangolin node is on a box with a dynamic ip-address.
When that node gets a new ip (once a day), the newt-tunnels lose connection.
Apparently they ping to the old ip-address, whereas configured with a dns-name.
Re-checked with the current newt-version.
### Environment
- OS Type & Version: (e.g., Ubuntu 22.04)
- Pangolin Version: 1.11.0 CE
- Newt Version: 1.6.0
### To Reproduce
Simply change the ip-address of the pangolin node while running.
### Expected Behavior
Newt tunnels should recover and use the new ip-
GiteaMirror
added the bug label 2026-04-25 15:44:52 -05:00
To ensure stable accessibility from the Internet, a fixed IP address is highly recommended.
A small VPS server is perfectly adequate for this purpose.
<!-- gh-comment-id:3477037987 -->
@RadioHerzblut commented on GitHub (Nov 2, 2025):
To ensure stable accessibility from the Internet, a fixed IP address is highly recommended.
A small VPS server is perfectly adequate for this purpose.
Same problem. Seems like this was not an issue before, but tracking down a fix is being a bit extra so far. Not going to waste money on a VPS so I may just have to swap off and go back to SWAG or another reverse proxy.
<!-- gh-comment-id:3508379350 -->
@crookshanked commented on GitHub (Nov 9, 2025):
Same problem. Seems like this was not an issue before, but tracking down a fix is being a bit extra so far. Not going to waste money on a VPS so I may just have to swap off and go back to SWAG or another reverse proxy.
Same problem. My current workaround is a cron job on every newt tunnel node which checks the domain name via dig every 5 minutes and restarts newt service if it changes.
This very same problem exists in basic wireguard (it doesn’t re-resolve dns after losing tunnel connectivity). I have a similar cron job running on my opnsense.
<!-- gh-comment-id:3542671961 -->
@Master-Yoba commented on GitHub (Nov 17, 2025):
Same problem. My current workaround is a cron job on every newt tunnel node which checks the domain name via dig every 5 minutes and restarts newt service if it changes.
This very same problem exists in basic wireguard (it doesn’t re-resolve dns after losing tunnel connectivity). I have a similar cron job running on my opnsense.
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 @sqrt-1764 on GitHub (Oct 28, 2025).
Original GitHub issue: https://github.com/fosrl/pangolin/issues/1766
Originally assigned to: @oschwartz10612 on GitHub.
Describe the Bug
My Pangolin node is on a box with a dynamic ip-address.
When that node gets a new ip (once a day), the newt-tunnels lose connection.
Apparently they ping to the old ip-address, whereas configured with a dns-name.
Re-checked with the current newt-version.
Environment
To Reproduce
Simply change the ip-address of the pangolin node while running.
Expected Behavior
Newt tunnels should recover and use the new ip-
@RadioHerzblut commented on GitHub (Nov 2, 2025):
To ensure stable accessibility from the Internet, a fixed IP address is highly recommended.
A small VPS server is perfectly adequate for this purpose.
@crookshanked commented on GitHub (Nov 9, 2025):
Same problem. Seems like this was not an issue before, but tracking down a fix is being a bit extra so far. Not going to waste money on a VPS so I may just have to swap off and go back to SWAG or another reverse proxy.
@Master-Yoba commented on GitHub (Nov 17, 2025):
Same problem. My current workaround is a cron job on every newt tunnel node which checks the domain name via dig every 5 minutes and restarts newt service if it changes.
This very same problem exists in basic wireguard (it doesn’t re-resolve dns after losing tunnel connectivity). I have a similar cron job running on my opnsense.