[GH-ISSUE #3093] Pangolin MacOS Client 0.8.3 Stuck at Registering #32377

Open
opened 2026-06-15 09:49:47 -05:00 by GiteaMirror · 8 comments
Owner

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

  • OS Type & Version: MacOS Tahoe 26.5
  • Pangolin Version: 1.18.4
  • Gerbil Version: 1.3.1
  • Traefik Version: 3.6.14
  • Newt Version: 1.12.5
  • Pangolin Client: 0.8.3

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.

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 - OS Type & Version: MacOS Tahoe 26.5 - Pangolin Version: 1.18.4 - Gerbil Version: 1.3.1 - Traefik Version: 3.6.14 - Newt Version: 1.12.5 - Pangolin Client: 0.8.3 ### 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.
Author
Owner

@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.

<!-- gh-comment-id:4468645739 --> @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.
Author
Owner

@jelly8perplexed commented on GitHub (May 17, 2026):

Ah, good catch. Yes I am using cloudflare, but in DNS only for any pangolin resources

<!-- gh-comment-id:4468663647 --> @jelly8perplexed commented on GitHub (May 17, 2026): Ah, good catch. Yes I am using cloudflare, but in DNS only for any pangolin resources
Author
Owner

@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?

<!-- gh-comment-id:4557949979 --> @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?
Author
Owner

@jelly8perplexed commented on GitHub (Jun 6, 2026):

Looks like it connects fine through cloudflare, looking at logs on the endpoint.

  • net.pangolin.Pangolin.PacketTunnel: ... Websocket Connected

Hole-punch also works:

  • PacketTunnel: Got exit nodes for hole punching: [{ztna.URL.com 21820 ...}]
  • PacketTunnel: Starting UDP hole punch to 1 exit nodes with shared bind

It loops here:

  • websocket: Sending message: olm/wg/register, data: map[...]
  • ...
  • websocket: Sending message: olm/wg/register, data: map[...]

Confirmed ports are open on the VPS, nothing changed there. Pangolin setup also hasn't changed.

<!-- gh-comment-id:4636872341 --> @jelly8perplexed commented on GitHub (Jun 6, 2026): Looks like it connects fine through cloudflare, looking at logs on the endpoint. - net.pangolin.Pangolin.PacketTunnel: ... Websocket Connected Hole-punch also works: - PacketTunnel: Got exit nodes for hole punching: [{ztna.URL.com 21820 ...}] - PacketTunnel: Starting UDP hole punch to 1 exit nodes with shared bind It loops here: - websocket: Sending message: olm/wg/register, data: map[...] - ... - websocket: Sending message: olm/wg/register, data: map[...] Confirmed ports are open on the VPS, nothing changed there. Pangolin setup also hasn't changed.
Author
Owner

@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?

<!-- gh-comment-id:4636887342 --> @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?
Author
Owner

@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:

  • nc -vuz 134.199.187.xx 21820
  • Connection to 134.199.187.xx port 21820 [udp/*] succeeded!
<!-- gh-comment-id:4636931171 --> @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: - nc -vuz 134.199.187.xx 21820 - Connection to 134.199.187.xx port 21820 [udp/*] succeeded!
Author
Owner

@AstralDestiny commented on GitHub (Jun 6, 2026):

oracle or ionos at all?

<!-- gh-comment-id:4637081334 --> @AstralDestiny commented on GitHub (Jun 6, 2026): oracle or ionos at all?
Author
Owner

@jelly8perplexed commented on GitHub (Jun 7, 2026):

Negative. I host on digital ocean.

<!-- gh-comment-id:4643336626 --> @jelly8perplexed commented on GitHub (Jun 7, 2026): Negative. I host on digital ocean.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/pangolin#32377