Site connector (CLI/Newt 1.26) fails registration with “Site last hole punch is too old” while older Newt works on same network

Offen
#178 3 Kommentare 0 Reaktionen 0 zugewiesene Personen Auf GitHub ansehen

Maintainer antworten meist innerhalb von 1 Tag

Dieses Issue hat noch niemand übernommen.

Bewertung

Schwierigkeit
4/5
Geschätzter Aufwand
3-5 Tage
Anfängerfreundlichkeit
38/100
Issue-Typ
Bug
Klarheit
Größtenteils klar
Aktivitätsstatus
Aktiv
Tech-Stack
go, linux
Bereich
networking

Rechercherichtung

Start by tracing the CLI site's registration and hole-punch flow, then compare it with the older Newt path; the payload does not name source files or tests. Check how the site identifies its network address and handles relay fallback, using the reported UDP ports and timeout logs as clues. Done means the CLI site registers and receives a working peer configuration, through hole-punch or relay.

Vom Indexierungsmodell aus dem Issue-Text verfasst.

Beschreibung

Describe the Bug

I am migrating from the Newt site connector to the now recommended Pangolin CLI site connector. The old Newt site works reliably. A newly created site using the current CLI binary on a Proxmox LXC container consistently fails to register.

Environment
  • OS Type & Version: Ubuntu 26.04 LTS (Pangolin server VPS) Debian 13 (Pangolin CLI LXC)
  • Pangolin Version: 1.26.0
  • Gerbil Version: 1.8.0
  • Traefik Version: 3.7.17
  • Newt Version: 1.20.0
  • Client Version: 0.21.0
To Reproduce

Creating a new CLI binary install on a Proxmox LXC container and attempting to connect to my self-hosted Pangolin server fails. Proxmox is on the latest 9.2 version, with tun access given to the LXC.

Inspecting server-side logs, I see:

Site last hole punch is too old; skipping this register.
The site is failing to hole punch and identify its network address with the server.
Can the site reach the server on its Relay UDP port?

From the client side, I see the following logs:

Websocket connected
Connecting to endpoint: pangolin.labnest.net
SendMessageInterval timed out after 16 attempts for message type: newt/wg/get-config
Initial reliable ping failed... failed to read ICMP packet: i/o timeout
(repeated ping timeouts)

UDP packets from the LXC reach my VPS on both ports 51820 and 21820 (confirmed with tcpdump and nc -u). I verified no firewall is blocking the ports.
When started with -native flag, the site does create a WireGuard interface and receives a tunnel IP, but never completes registration and never receives a working peer config.

I have tried fully deleting and recreating the site and get the same error. Setting a static port also doesn't help.
I compared ip addr and wg show between the working Newt and failing CLI sites. Both create an interface and get a tunnel IP.

AI Disclosure

Utilized Grok to troubleshoot error logs and attempt to get the connection working. Also used it to help me write this issue.

Expected Behavior

The CLI site should complete hole-punch (or fall back to relay) and receive a WireGuard configuration.

Vorherrschende Sprache
Go
Sterne
70
Forks
26
Ø Merge
4 Std. 19 Min.
Gemergte PRs (30 T.)
11

Entwicklungsumgebung

Erste Schritte

  1. Lesen Sie das ganze Issue und danach den Beitragsleitfaden des Projekts.
  2. Schreiben Sie ins Issue, dass Sie es übernehmen — das erspart doppelte Arbeit.
  3. Forken Sie das Repository und arbeiten Sie in einem Branch.
  4. Öffnen Sie einen Pull Request, der die Issue-Nummer nennt.

Mehr aus fosrl/cli

Alle Issues in fosrl/cli

Ähnliche Issues

Weitere Issues zu Go

Neue Issues direkt in Ihr Postfach

Eine kurze Übersicht über anfängerfreundliche GitHub-Issues.