[GH-ISSUE #2950] Newt connects to outdated IPv6 endpoint after VPS migration – server keeps serving stale node address #30107

Closed
opened 2026-06-13 10:34:11 -05:00 by GiteaMirror · 2 comments
Owner

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:

Connecting to endpoint: [OLD_IPV6_REDACTED]

This address belonged to the previous VPS network and is no longer reachable.

However:

  • DNS for pangolin.my.site resolves correctly
  • ICMP/IPv6 connectivity is working
  • WebSocket connection to Pangolin succeeds
  • New node creation + fresh credentials do not resolve the issue

Observed behavior

Newt logs:

Websocket connected
Connecting to endpoint: [OLD_IPV6_REDACTED]
failed to read ICMP packet: i/o timeout

Despite recreating the node, the same stale IPv6 endpoint is still used.


Docker compose file

services:
  newt:
    image: fosrl/newt
    container_name: newt
    restart: unless-stopped
    volumes:
      - /var/run/docker.sock:/var/run/docker.sock:ro
    environment:
      - PANGOLIN_ENDPOINT=https://pangolin.my.site
      - NEWT_ID=redacted
      - NEWT_SECRET=redacted
      - DOCKER_SOCKET=unix:///var/run/docker.sock
    network_mode: host

Environment

  • OS Type & Version: Debian GNU/Linux 13 (trixie)
  • Pangolin Version: 1.18.1
  • Gerbil Version: 1.3.0
  • Traefik Version: v3.6
  • Newt Version: 1.12.3

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:

  • deleting a node
  • recreating a new node
  • assigning fresh NEWT_ID / NEWT_SECRET

Newt should:

  • receive a fresh endpoint from the server
  • not reuse any previously assigned IPs
  • connect to the updated VPS IPv6 address
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: ```text id="a8m2kc" Connecting to endpoint: [OLD_IPV6_REDACTED] ``` This address belonged to the previous VPS network and is no longer reachable. However: * DNS for `pangolin.my.site` resolves correctly * ICMP/IPv6 connectivity is working * WebSocket connection to Pangolin succeeds * New node creation + fresh credentials do not resolve the issue --- ### **Observed behavior** Newt logs: ```text id="k9d3px" Websocket connected Connecting to endpoint: [OLD_IPV6_REDACTED] failed to read ICMP packet: i/o timeout ``` Despite recreating the node, the same stale IPv6 endpoint is still used. --- ### **Docker compose file** ``` services: newt: image: fosrl/newt container_name: newt restart: unless-stopped volumes: - /var/run/docker.sock:/var/run/docker.sock:ro environment: - PANGOLIN_ENDPOINT=https://pangolin.my.site - NEWT_ID=redacted - NEWT_SECRET=redacted - DOCKER_SOCKET=unix:///var/run/docker.sock network_mode: host ``` ### Environment - OS Type & Version: Debian GNU/Linux 13 (trixie) - Pangolin Version: 1.18.1 - Gerbil Version: 1.3.0 - Traefik Version: v3.6 - Newt Version: 1.12.3 ### 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: - deleting a node - recreating a new node - assigning fresh NEWT_ID / NEWT_SECRET Newt should: - receive a **fresh endpoint from the server** - not reuse any previously assigned IPs - connect to the updated VPS IPv6 address
Author
Owner

@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

<!-- gh-comment-id:4360893008 --> @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
Author
Owner

@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!

<!-- gh-comment-id:4362998490 --> @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!
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/pangolin#30107