github-starred/pangolin
2
0
Fork 0
mirror of https://github.com/fosrl/pangolin.git synced 2026-05-07 13:19:07 -05:00
Code Issues 564 Packages Projects Releases 72 Wiki Activity

[GH-ISSUE #2571] Wireguard setup not working - Gateway Timeout #4134

New Issue
Open
opened 2026-04-20 08:35:46 -05:00 by GiteaMirror · 5 comments
GiteaMirror commented 2026-04-20 08:35:46 -05:00
Owner
Copy Link

Originally created by @trashmaster9000 on GitHub (Mar 1, 2026).
Original GitHub issue: https://github.com/fosrl/pangolin/issues/2571

Describe the Bug

i'm trying to get a basic wireguard tunnel working, the connected client would be a openwrt router.
the tunnel connects just fine but i can not make resources accessible via this tunnel.

i've checked all firewall settings but can not find the issue, i suspect a missconfiguration on pangolins side maybe?

Environment

  • OS Type & Version: Debian 13
  • Pangolin Version: 1.16.2
  • Gerbil Version:
  • Traefik Version:
  • Newt Version:
  • Olm Version: (if applicable)

To Reproduce

setup basic wireguard tunnel, add wireguard to openwrt, set input to accept of wireguard zone in firewall settings, create new resource in pangolin dashboard and point to openwrt wireguard ip address port 80
try to access newly created resource

Expected Behavior

if i accept incomming connections on the wireguard interface in openwrt as test and point pangolin to that adress and port 80 i expect to see the openwrt web interface but instead i get a "Gateway Timeout" error.
the tunnel is shown as connected in pangolin and openwrt, there is a bit of traffic going through (a few packets rx and tx per minute)

Originally created by @trashmaster9000 on GitHub (Mar 1, 2026). Original GitHub issue: https://github.com/fosrl/pangolin/issues/2571 ### Describe the Bug i'm trying to get a basic wireguard tunnel working, the connected client would be a openwrt router. the tunnel connects just fine but i can not make resources accessible via this tunnel. i've checked all firewall settings but can not find the issue, i suspect a missconfiguration on pangolins side maybe? ### Environment - OS Type & Version: Debian 13 - Pangolin Version: 1.16.2 - Gerbil Version: - Traefik Version: - Newt Version: - Olm Version: (if applicable) ### To Reproduce setup basic wireguard tunnel, add wireguard to openwrt, set input to accept of wireguard zone in firewall settings, create new resource in pangolin dashboard and point to openwrt wireguard ip address port 80 try to access newly created resource ### Expected Behavior if i accept incomming connections on the wireguard interface in openwrt as test and point pangolin to that adress and port 80 i expect to see the openwrt web interface but instead i get a "Gateway Timeout" error. the tunnel is shown as connected in pangolin and openwrt, there is a bit of traffic going through (a few packets rx and tx per minute)
GiteaMirror added the stale label 2026-04-20 08:35:47 -05:00
GiteaMirror commented 2026-04-20 08:35:48 -05:00
Author
Owner
Copy Link

@LaurenceJJones commented on GitHub (Mar 1, 2026):

It's difficult for us to reproduce an issue that requires us spending time getting an openwrt router online and all the pitfalls it may have reproducing.

openwrt wireguard ip address port 80

This may be caused by the OpenWRT interface only binding to certain address ranges on the router itself. Could you check which interfaces it's bound too as port 80 might not be reachable from the wireguard tunnel ip.

also check #2341 to ensure you got the right ip of the tunnel

<!-- gh-comment-id:3980322602 --> @LaurenceJJones commented on GitHub (Mar 1, 2026): It's difficult for us to reproduce an issue that requires us spending time getting an openwrt router online and all the pitfalls it may have reproducing. > openwrt wireguard ip address port 80 This may be caused by the OpenWRT interface only binding to certain address ranges on the router itself. Could you check which interfaces it's bound too as port 80 might not be reachable from the wireguard tunnel ip. also check #2341 to ensure you got the right ip of the tunnel
GiteaMirror commented 2026-04-20 08:35:50 -05:00
Author
Owner
Copy Link

@github-actions[bot] commented on GitHub (Mar 16, 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.

<!-- gh-comment-id:4064342395 --> @github-actions[bot] commented on GitHub (Mar 16, 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.
GiteaMirror commented 2026-04-20 08:35:53 -05:00
Author
Owner
Copy Link

@trashmaster9000 commented on GitHub (Mar 21, 2026):

Hey, sorry, didnt really have time to tinker with this...
the openwrt web interface should be reachable through the wireguard interface, i've not set the webinterface to only be bound to specific interfaces. port forwards dont work either.

i've used the wireguard IP address shown in the openwrt webinterface for the pangolin configuration, no other IP in that subnet is working.

i'm new to wireguard but would like to help you debug this, could you recommend any steps for troubleshooting this issue?

<!-- gh-comment-id:4102924956 --> @trashmaster9000 commented on GitHub (Mar 21, 2026): Hey, sorry, didnt really have time to tinker with this... the openwrt web interface should be reachable through the wireguard interface, i've not set the webinterface to only be bound to specific interfaces. port forwards dont work either. i've used the wireguard IP address shown in the openwrt webinterface for the pangolin configuration, no other IP in that subnet is working. i'm new to wireguard but would like to help you debug this, could you recommend any steps for troubleshooting this issue?
GiteaMirror commented 2026-04-20 08:35:55 -05:00
Author
Owner
Copy Link

@tunip commented on GitHub (Apr 1, 2026):

Did you checked the routing in OpenWrt? I did a Pangolin <- WireGuard -> Server setup and have seen, there is a missing route into the tunnel. Need to add tihs manually and then it worked.

<!-- gh-comment-id:4169381550 --> @tunip commented on GitHub (Apr 1, 2026): Did you checked the routing in OpenWrt? I did a Pangolin <- WireGuard -> Server setup and have seen, there is a missing route into the tunnel. Need to add tihs manually and then it worked.
GiteaMirror commented 2026-04-20 08:35:56 -05:00
Author
Owner
Copy Link

@github-actions[bot] commented on GitHub (Apr 16, 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.

<!-- gh-comment-id:4256614451 --> @github-actions[bot] commented on GitHub (Apr 16, 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.
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 stale
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#4134
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?