mirror of
https://github.com/fosrl/pangolin.git
synced 2026-07-17 07:04:36 -05:00
[GH-ISSUE #3093] Pangolin MacOS Client 0.8.3 Stuck at Registering #27929
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 @jelly8perplexed on GitHub (May 16, 2026).
Original GitHub issue: https://github.com/fosrl/pangolin/issues/3093
Describe the Bug
I upgraded from 0.8.1 to 0.8.3 and since upgrading I can no longer connect to my site. The status in the taskbar shows registering. I can see the updated version reflected in the Pangolin dashboard.
Within Preferences -> Status , it shows connected but no sites connected.
Environment
To Reproduce
Attempts to connect to the pangolin site stay stuck at registering. I can re-add the account successfully, but connection never occurs.
Expected Behavior
Expected behavior is the client connects and shows connected in the taskbar section.
@AstralDestiny commented on GitHub (May 17, 2026):
Are you behind cf for your control plane at all? asking as they've been having some waf issues lately where it blocks stuff it shouldn't be.
@jelly8perplexed commented on GitHub (May 17, 2026):
Ah, good catch. Yes I am using cloudflare, but in DNS only for any pangolin resources
@jelly8perplexed commented on GitHub (May 27, 2026):
Is there anything that can be done on the cloudflare side or do we just have to wait for an update to their platform?
@jelly8perplexed commented on GitHub (Jun 6, 2026):
Looks like it connects fine through cloudflare, looking at logs on the endpoint.
Hole-punch also works:
It loops here:
Confirmed ports are open on the VPS, nothing changed there. Pangolin setup also hasn't changed.
@AstralDestiny commented on GitHub (Jun 6, 2026):
CF should have fixed it's security rules if you do have it proxied at all right now. You have the wireguard ip set to a non proxied ip right?
@jelly8perplexed commented on GitHub (Jun 6, 2026):
Yes that's correct. It's all dns-only.
I do see logs within pangolin. I tried archiving the client, and then upon reconnecting it shows up in the list but not as an active client. I've fully uninstalled and reinstalled as well.
[pangolin] 2026-06-06T01:56:33.233660889Z 2026-06-06T01:56:33+00:00 [info]: [handleOlmRegisterMessage] Handling register olm message
[pangolin] 2026-06-06T01:56:33.251253269Z 2026-06-06T01:56:33+00:00 [warn]: [handleOlmRegisterMessage] Client last hole punch is too old and we have sites to send; skipping this register. The client is failing to hole punch and identify its network address with the server. Can the client reach the server on UDP port 21820? {"orgId":"homelab"}
[pangolin] 2026-06-06T01:56:35.004529861Z 2026-06-06T01:56:35+00:00 [info]: All connections removed for OLM ID: 6f1uegu61kqxi6b
[pangolin] 2026-06-06T01:56:35.004577238Z 2026-06-06T01:56:35+00:00 [info]: Client disconnected - OLM ID: 6f1uegu61kqxi6b
Although it can connect fine on that port:
@AstralDestiny commented on GitHub (Jun 6, 2026):
oracle or ionos at all?
@jelly8perplexed commented on GitHub (Jun 7, 2026):
Negative. I host on digital ocean.