Site connector (CLI/Newt 1.26) fails registration with “Site last hole punch is too old” while older Newt works on same network
Los mantenedores suelen responder en 1 día
Nadie ha tomado este issue todavía.
Evaluación
- Dificultad
- 4/5
- Tiempo estimado
- 3-5 días
- Aptitud para principiantes
- 38/100
- Tipo de issue
- Error
- Claridad
- Bastante claro
- Estado de actividad
- Activo
- Stack tecnológico
- go, linux
- Área
- networking
Línea de trabajo
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.
Escrito por el modelo de indexación a partir del texto del issue.
Descripción
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.
- Lenguaje dominante
- Go
- Estrellas
- 70
- Forks
- 26
- Merge medio
- 4 h 19 min
- PR fusionados (30 d)
- 11
Preparar el entorno
- Incluye un Dockerfile o un archivo de Docker Compose
- Tiene una plantilla de pull request
- Leer la guía de contribución
Primeros pasos
- Lee el issue completo y luego la guía de contribución del proyecto.
- Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
- Haz un fork del repositorio y trabaja en una rama.
- Abre un pull request que haga referencia al número del issue.
Más de fosrl/cli
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 72/100
Los mantenedores suelen responder en 1 día
-
bug
Dificultad 2/5 1-3 horas Aptitud para principiantes 76/100
Los mantenedores suelen responder en 1 día
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 56/100
Los mantenedores suelen responder en 1 día
-
Automatic Site UpdatesAbierto
Dificultad 3/5 1-2 días Aptitud para principiantes 53/100
fosrl/cli#179 · 13 comentarios ·
Los mantenedores suelen responder en 1 día
-
needs investigating
fosrl/cli#74 · 4 comentarios · 2 reacciones ·
Los mantenedores suelen responder en 1 día
Issues similares
-
Project submission: xmcp DocsAbierto
Dificultad 1/5 Menos de una hora Aptitud para principiantes 62/100
slavakurilyak/awesome-ai-agents#1005 ·
-
agent-research-finding chore
Dificultad 2/5 1-3 horas Aptitud para principiantes 78/100
jordansmall/spindrift#7370 ·
Los mantenedores suelen responder en 1 día
-
☢️ Bug v3
Dificultad 2/5 1-3 horas Aptitud para principiantes 82/100
Los mantenedores suelen responder en 1 día
-
The repo's gates check is clean and runs need no swapsPosiblemente ocupada @turbot-agent-fleet la tomó hoy. Abiertoagent:ready
Dificultad 2/5 1-3 horas Aptitud para principiantes 64/100
turbot/tailpipe#677 · 2 comentarios ·
Los mantenedores suelen responder en 1 día
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 62/100
elecnix/terraform-permcheck#229 ·
Los mantenedores suelen responder en 1 día