github-starred/pangolin
2
0
Fork 0
mirror of https://github.com/fosrl/pangolin.git synced 2026-05-21 09:21:15 -05:00
Code Issues 856 Packages Projects Releases 74 Wiki Activity

[GH-ISSUE #3096] Newt site stays online but WireGuard data plane stops carrying traffic #17293

New Issue
Open
opened 2026-05-18 17:47:05 -05:00 by GiteaMirror · 0 comments
GiteaMirror commented 2026-05-18 17:47:05 -05:00
Owner
Copy Link

Originally created by @yusuf-madkour on GitHub (May 17, 2026).
Original GitHub issue: https://github.com/fosrl/pangolin/issues/3096

Describe the Bug

A Newt site that previously worked stopped carrying public-resource traffic. Pangolin still showed the site online / reconnected, but resources behind that Newt site returned 502.

The site had historical non-zero data in/out counters, so this was not a fresh setup that never worked. The same backend resources were restored immediately by moving them from the Newt site to a local Pangolin site on the VPS, reaching the same backend IPs/ports over an existing NetBird route.

Environment

  • Pangolin/Gerbil/Traefik host: Ubuntu 24.04.3 LTS, aarch64, Oracle VPS
  • Original Newt host: Proxmox VE 9.1.4, unprivileged Ubuntu LXC 100, amd64
  • Reproduction Newt host: Debian 13.2 (trixie), aarch64, bare-metal madpi
  • Pangolin Version: 1.18.4
  • Gerbil Version: 1.4.0
  • Traefik Version: 3.5
  • Newt Version: 1.12.5

To Reproduce

I do not have a clean minimal reproducer yet. The failure was observed in this sequence:

  1. Run Pangolin/Gerbil/Traefik on a VPS with a Newt site connected from a home network behind CGNAT.
  2. Use the Newt site successfully for public resources for some time; the site had non-zero data in/out counters.
  3. After the failure starts, keep the same Newt site connected. Pangolin still shows it online / reconnected.
  4. Access public resources routed through that Newt site.
  5. The resources return 502, while Gerbil wg0 shows no useful RX / handshake traffic.

Additional checks:

  • The issue reproduced with a separate bare-metal Newt test on a raspberry pi device in the same subnet.
  • A plain UDP probe to Gerbil 51820 reached the VPS.

Expected Behavior

If the Newt site is online/reconnected, the WireGuard data plane should recover or report a clear failed state. Previously working public resources behind the Newt site should not remain stuck at 502 with no useful wg0 RX/handshake traffic.

Originally created by @yusuf-madkour on GitHub (May 17, 2026). Original GitHub issue: https://github.com/fosrl/pangolin/issues/3096 ### Describe the Bug A Newt site that previously worked stopped carrying public-resource traffic. Pangolin still showed the site online / reconnected, but resources behind that Newt site returned 502. The site had historical non-zero data in/out counters, so this was not a fresh setup that never worked. The same backend resources were restored immediately by moving them from the Newt site to a local Pangolin site on the VPS, reaching the same backend IPs/ports over an existing NetBird route. ### Environment - Pangolin/Gerbil/Traefik host: Ubuntu 24.04.3 LTS, aarch64, Oracle VPS - Original Newt host: Proxmox VE 9.1.4, unprivileged Ubuntu LXC 100, amd64 - Reproduction Newt host: Debian 13.2 (trixie), aarch64, bare-metal `madpi` - Pangolin Version: 1.18.4 - Gerbil Version: 1.4.0 - Traefik Version: 3.5 - Newt Version: 1.12.5 ### To Reproduce I do not have a clean minimal reproducer yet. The failure was observed in this sequence: 1. Run Pangolin/Gerbil/Traefik on a VPS with a Newt site connected from a home network behind CGNAT. 2. Use the Newt site successfully for public resources for some time; the site had non-zero data in/out counters. 3. After the failure starts, keep the same Newt site connected. Pangolin still shows it online / reconnected. 4. Access public resources routed through that Newt site. 5. The resources return 502, while Gerbil `wg0` shows no useful RX / handshake traffic. Additional checks: - The issue reproduced with a separate bare-metal Newt test on a raspberry pi device in the same subnet. - A plain UDP probe to Gerbil `51820` reached the VPS. ### Expected Behavior If the Newt site is online/reconnected, the WireGuard data plane should recover or report a clear failed state. Previously working public resources behind the Newt site should not remain stuck at 502 with no useful `wg0` RX/handshake traffic.
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#17293
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?