mirror of
https://github.com/fosrl/pangolin.git
synced 2026-07-16 06:08:33 -05:00
[GH-ISSUE #1526] Hole punch process failing - prevents tunnel establishment and all connectivity #12745
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 @devarmada on GitHub (Sep 23, 2025).
Original GitHub issue: https://github.com/fosrl/pangolin/issues/1526
Problem
Newt client connects via WebSocket but tunnel never establishes because hole punch process fails, leaving site.endpoint null and blocking WireGuard configuration delivery.
Environment
• Pangolin Server: 1.10.2 in Podman on Debian VPS
• Gerbil: 1.2.1 in Podman on Debian VPS
• Newt Client: 1.5.0 on Raspberry Pi 4, Raspbian Bullseye (ARM64)
• Network: Newt on local network 172.19.1.0/24, Pangolin on public VPS
Root Cause
Hole punch process fails → site.endpoint remains null → WireGuard config blocked → no tunnel
Flow:
Evidence
Pangolin logs - can't find endpoint
2025-09-23T10:05:32.524Z [warn]: Site 2 has no endpoint, skippingNewt logs - can't get WireGuard config
Sep 23 12:05:50 dente newt[408]: INFO: SendMessageInterval timed out after 10 attempts for message type: newt/wg/get-configImpact
• HTTP resources: 504 Gateway Timeout
• TCP resources: Non-functional
• All tunnel-dependent features broken
• Core Pangolin functionality unusable
Versions Tested
• Pangolin 1.10.2 + gerbil 1.2.1 + newt 1.5.0
The hole punch endpoint
/api/v1/gerbil/update-hole-punchis never successfully called, preventing the site.endpoint field from being set, which blocks all tunnel functionality.@AstralDestiny commented on GitHub (Sep 23, 2025):
You have wireguard port open? and does your newt succeed even getting to icmp ping tests?
@oschwartz10612 commented on GitHub (Sep 23, 2025):
^^ port 51820 and port 21820 https://docs.digpangolin.com/manage/clients/add-client#prerequisites
@devarmada commented on GitHub (Sep 23, 2025):
I have missed that resource, sorry.
Port 51820 was already there, I've added port 21820
The VPS has no firewall, BTW
These are the logs from the newt client
@miloschwartz commented on GitHub (Sep 27, 2025):
Seems like it's working now?
@devarmada commented on GitHub (Sep 28, 2025):
It isn't working 😭
I still have the same issue and I made no progress at all.
Thanks for checking, anyway!
@github-actions[bot] commented on GitHub (Oct 13, 2025):
This issue has been automatically marked as stale due to 14 days of inactivity. It will be closed in 14 days if no further activity occurs.
@github-actions[bot] commented on GitHub (Oct 27, 2025):
This issue has been automatically closed due to inactivity. If you believe this is still relevant, please open a new issue with up-to-date information.
@LunkSnee commented on GitHub (Dec 27, 2025):
also experiencing this. using Oracle Cloud and have all ports open. I can ping it directly, but the newt can't ping.
@AstralDestiny commented on GitHub (Dec 27, 2025):
You added it to both the pangolin instance and the oracle web ui for ports for UDP 21820 / 51820 ? @LunkSnee ?
@zelo66 commented on GitHub (Dec 29, 2025):
Same for me, firewall disabled
@LunkSnee commented on GitHub (Dec 29, 2025):
Yes, I did. Not sure what was causing the issue, but I shutdown the containers, erased the database, and started back up fresh, and I was able to get things to connect. Just destroying the containers without erasing the database didn't fix it. I had to start fresh. Its up and running now.