github-starred/pangolin
2
0
Fork 0
mirror of https://github.com/fosrl/pangolin.git synced 2026-07-16 14:47:04 -05:00
Code Issues 1.6k Packages Projects Releases 79 Wiki Activity

[GH-ISSUE #2901] Adding a private resource breaks hole-punch for already-connected clients; cache never repopulates #9028

New Issue
Open
opened 2026-04-30 05:16:40 -05:00 by GiteaMirror · 0 comments
GiteaMirror commented 2026-04-30 05:16:40 -05:00
Owner
Copy Link

Originally created by @andrewixl on GitHub (Apr 24, 2026).
Original GitHub issue: https://github.com/fosrl/pangolin/issues/2901

Describe the Bug

Creating any private resource (siteResources) and once created, if an Olm client is registered (connected) puts the client into a permanent "last hole punch is too old" loop. The client never reaches connected state, and no amount of reconnecting, restarting, or deleting/recreating the resource restores it.

Environment

  • Ubuntu 24.04
  • Pangolin: ee-1.17.1
  • Gerbil: 1.31
  • Traefik: 3.6
  • Newt: 1.11.0
  • Olm Windows: 0.9.0

To Reproduce

Reproduction:

  1. No private resources.
  2. Create a new client. Pair it with a Windows Pangolin client. Confirm connected.
  3. Add ONE private resource pointing at any LAN IP.
  4. Immediately: logs show "handleOlmServerPeerAddMessage: No endpoint found for client N"
  5. Client enters permanent "Client last hole punch is too old" loop
  6. clientSitesAssociationsCache rows for that client have endpoint=NULL, publicKey=NULL
  7. clients.lastHolePunch remains NULL
  8. Deleting the resource restored the client to connectivity.

Expected Behavior

Expected behavior should allow the client to register and connect to the private resources.

Originally created by @andrewixl on GitHub (Apr 24, 2026). Original GitHub issue: https://github.com/fosrl/pangolin/issues/2901 ### Describe the Bug Creating any private resource (siteResources) and once created, if an Olm client is registered (connected) puts the client into a permanent "last hole punch is too old" loop. The client never reaches connected state, and no amount of reconnecting, restarting, or deleting/recreating the resource restores it. ### Environment - Ubuntu 24.04 - Pangolin: ee-1.17.1 - Gerbil: 1.31 - Traefik: 3.6 - Newt: 1.11.0 - Olm Windows: 0.9.0 ### To Reproduce Reproduction: 1. No private resources. 2. Create a new client. Pair it with a Windows Pangolin client. Confirm connected. 3. Add ONE private resource pointing at any LAN IP. 4. Immediately: logs show "handleOlmServerPeerAddMessage: No endpoint found for client N" 5. Client enters permanent "Client last hole punch is too old" loop 6. clientSitesAssociationsCache rows for that client have endpoint=NULL, publicKey=NULL 7. clients.lastHolePunch remains NULL 8. Deleting the resource restored the client to connectivity. ### Expected Behavior Expected behavior should allow the client to register and connect to the private resources.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
api
authentication
bug
config
dependencies
docker
documentation
enhancement
good first issue
help wanted
Improvement
Look Into
needs investigating
networking
new feature
non-critical bug
potential bug
pull-request
Mirrored from GitHub Pull Request
 question
reverse proxy
Security
stale
ui
wontfix
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/pangolin#9028
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?