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

Aperta
#178 3 commenti 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
4/5
Tempo stimato
3-5 giorni
Idoneità per principianti
38/100
Tipo di issue
Bug
Chiarezza
Abbastanza chiara
Stato di attività
Attiva
Stack tecnologico
go, linux
Ambito
networking

Direzione di ricerca

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.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

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.

Lingua principale
Go
Stelle
70
Fork
26
Merge medio
4h 19m
PR unite (30g)
11

Preparare l'ambiente

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di fosrl/cli

Tutte le issue di fosrl/cli

Issue simili

Altre issue su Go

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.