mirror of
https://github.com/fosrl/pangolin.git
synced 2026-07-16 06:08:33 -05:00
[GH-ISSUE #3041] Client connections and LAN resource unavailability after updates #27917
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 @GisaLab on GitHub (May 9, 2026).
Original GitHub issue: https://github.com/fosrl/pangolin/issues/3041
Describe the Bug
Hello
After upgrading the Pangolin server to v1.18 and Newt to v1.12.5, several client machines remain disconnected (including one machine upgraded to pangolin-cli 0.8.0 and then recreated as 0.8.1), and the LAN site sometimes becomes unavailable (disconnections observed lasting 7 and 23 minutes). Since the Newt update to v1.12.5, the site indicates it is connected, but no site resources are accessible.
Environment
To Reproduce
v1.18.3.pangolin-cli(e.g.0.8.0then0.8.1).v1.12.5).1.5.0(or1.4.4for regression testing).v1.18.3.pangolin-clion a client machine (e.g.0.8.0), observe the status in the interface.pangolin-cli 0.8.1.v1.12.5.v1.5.0orv1.4.4.v1.12.5, the site displays connected status but no resources are accessible.Expected Behavior
pangolin-cli(or after recreation), and remain reachable via Olm.v1.12.5, the LAN site should remain accessible and the resources exposed via Traefik/Newt should respond normally (no inconsistency between the "connected" status and the inaccessibility of resources).pangolin.domain.commust succeed without repeated errors of typei/o timeoutorno route to host.Screenshots / Logs
Additional Context
v1.18.3, Newt →v1.12.5, attempted to usepangolin-cli 0.8.0then recreated in0.8.1.dynamic_config.ymlandtraefik_config.yml: no obvious changes detected.v1.5.0andv1.4.4were unsuccessful in restoring the client connection.failed to read ICMP packet: i/o timeoutandfailed to create ICMP socket: ping connect: no route to host).SendMessageIntervalfornewt/wg/get-configandolm/wg/register).@GisaLab commented on GitHub (May 10, 2026):
Finally the problem came from the transfer of my domain name to cloudflare I did not know that it required a specific configuration I had not come across the discussion threads that talked about it before posting.
@LaurenceJJones commented on GitHub (May 11, 2026):
ahh thats make sense, apologies for the lack of reply on our end. Yes when changing over to cloudflare and enabling the proxy on the dns entry pings cannot complete anymore due to the fact that cloudflare blocks them and since you cannot connect anymore to the real ip of gerbil.
Will class as complete 👍🏻