mirror of
https://github.com/fosrl/pangolin.git
synced 2026-07-16 06:08:33 -05:00
[GH-ISSUE #2950] Newt connects to outdated IPv6 endpoint after VPS migration – server keeps serving stale node address #11040
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 @dawiddyd on GitHub (May 1, 2026).
Original GitHub issue: https://github.com/fosrl/pangolin/issues/2950
Describe the Bug
Title
Newt connects to outdated IPv6 endpoint after VPS migration – server keeps serving stale node address
Description
After migrating my VPS to a different machine (resulting in a new IPv6 subnet), Newt is no longer able to connect correctly to the Pangolin server.
Problem
Even after deleting and recreating the node in the Pangolin UI, Newt continues to connect to an old IPv6 endpoint that is no longer valid:
This address belonged to the previous VPS network and is no longer reachable.
However:
pangolin.my.siteresolves correctlyObserved behavior
Newt logs:
Despite recreating the node, the same stale IPv6 endpoint is still used.
Docker compose file
Environment
To Reproduce
Deploy Pangolin + Newt via Docker
Connect node successfully
Migrate VPS to new host (IPv6 subnet changes)
Delete node in Pangolin UI
Create a new node and update credentials
Restart Newt container
Observe it still attempts to connect to old IPv6 endpoint
Expected Behavior
After:
Newt should:
@oschwartz10612 commented on GitHub (May 1, 2026):
Try to configure the base endpoint for gerbil in your config.yml file
then restart both gerbil and pangolin.
https://docs.pangolin.net/self-host/advanced/config-file#setting-up-your-config-yml
@dawiddyd commented on GitHub (May 2, 2026):
OK yes this fixed the issue, totally forgot about the config file. Thanks a lot for your help!