mirror of
https://github.com/fosrl/pangolin.git
synced 2026-07-16 14:47:04 -05:00
[GH-ISSUE #2308] Idle timeout kicks me out after 30s and have to restart pangolin #23424
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 @danieldonaldson on GitHub (Jan 23, 2026).
Original GitHub issue: https://github.com/fosrl/pangolin/issues/2308
Describe the Bug
I have to constantly restart pangolin-cli for it to keep accessing my site.
I have pangolin running on one VPS. I have dokploy running on another. I can run
pangolin upand access the dokploy web interface via:http://dokploy-admin.pangolin:3000/and I can run through all the settings, etc. Once I leave it for ~30 seconds I cannot connect again until I runpangolin down && pangolin upThese are the logs:
Newt on the dokploy server:
Gerbil on pangolin server:
Pangolin logs:
See the important bit above
2026-01-23T15:03:10+00:00 [info]: Kicking offline olm client 1 due to inactivityEnvironment
To Reproduce
See above
Expected Behavior
Does not disconnect after 30 seconds
@github-actions[bot] commented on GitHub (Feb 7, 2026):
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 (Feb 21, 2026):
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.
@Tavernoshca commented on GitHub (Mar 26, 2026):
Hi @danieldonaldson
I have the exact same problem on fedora with the pangolin cli. I constantly have to reconnect for accessing my private resources. Do you still have this problem or did you find a solution/workaround?
@danieldonaldson commented on GitHub (Apr 1, 2026):
@Tavernoshca no unfortunately still struggling with it
@LaurenceJJones commented on GitHub (Apr 1, 2026):
When you run the cli can you add
--attachto the pangolin up command so we can see the logs that the client is generating.As by default the client should be pinging the tunnel path every 5 seconds so there could be something that is denying this path. Also 30 seconds doesnt seem accurate as the code looks for at least 2 minutes of staleness but this could be confusing when the olm client is reusing the previous credentials.