[GH-ISSUE #702] UDP (Wireguard Server) not Working #3521

Closed
opened 2026-04-20 07:30:48 -05:00 by GiteaMirror · 4 comments
Owner

Originally created by @fredmorais on GitHub (May 11, 2025).
Original GitHub issue: https://github.com/fosrl/pangolin/issues/702

Hey everyone,

I tried to search for this issue, but searching "Pangolin Wireguard" points me in a completely different direction.

Here is my usecase: right now I am accessing my home network with a Wireguard server running in docker and I have an open port on my firewall. I am testing Pangolin, and got a VPS for it.

I tested Pangolin with an HTTPS resource and it is working fine. I have Newt install on docker as well, connect it to the VPS, set up a resource pointed at my HTTPS server (Jellyfin) and it works great! However, following the same steps (obviously changing the IP and port for the correct values) for Wireguard yields no results. I checked that the Newt container can access the Wireguard server multiple times. Here are some screenshots to show how I configured it:

traefik_config.yml

entryPoints:
 // Redacted HTTP and HTTPS entry points
  udp-59382:
    address: ":59382/udp"

docker-compose.yml

gerbil:
   // Redacted
    ports:
      - 80:80
      - 443:443
      - 51820:51820/udp
      #
      - 59382:59382/udp

config.yml

flags:
  allow_raw_resources: true

Pangolin Config

Image

Keep in mind that I was exposing port 59382 in my firewall and pointing it to 51820 on my Wireguard server. Also, I'll never use this port in the future after exposing it here :)

So my final question: what am I doing wrong? Is this not supported at all or do I have something misconfigured? Thank you in advance!

Originally created by @fredmorais on GitHub (May 11, 2025). Original GitHub issue: https://github.com/fosrl/pangolin/issues/702 Hey everyone, I tried to search for this issue, but searching "Pangolin Wireguard" points me in a completely different direction. Here is my usecase: right now I am accessing my home network with a Wireguard server running in docker and I have an open port on my firewall. I am testing Pangolin, and got a VPS for it. I tested Pangolin with an HTTPS resource and it is working fine. I have Newt install on docker as well, connect it to the VPS, set up a resource pointed at my HTTPS server (Jellyfin) and it works great! However, following the same steps (obviously changing the IP and port for the correct values) for Wireguard yields no results. I checked that the Newt container can access the Wireguard server multiple times. Here are some screenshots to show how I configured it: ### traefik_config.yml ``` entryPoints: // Redacted HTTP and HTTPS entry points udp-59382: address: ":59382/udp" ``` ### docker-compose.yml ``` gerbil: // Redacted ports: - 80:80 - 443:443 - 51820:51820/udp # - 59382:59382/udp ``` ### config.yml ``` flags: allow_raw_resources: true ``` ### Pangolin Config ![Image](https://github.com/user-attachments/assets/439c72c0-a7df-4118-9510-b7c0e5d270a9) Keep in mind that I was exposing port 59382 in my firewall and pointing it to 51820 on my Wireguard server. Also, I'll never use this port in the future after exposing it here :) So my final question: what am I doing wrong? Is this not supported at all or do I have something misconfigured? Thank you in advance!
GiteaMirror added the stale label 2026-04-20 07:30:48 -05:00
Author
Owner

@mellow65 commented on GitHub (May 16, 2025):

I'm sorry, I've read through your post several times, and I'm still confused on what you're trying to do. Also I'm not super well versed in all of this, but I have been messing around with Pangolin a lot, so maybe I can poke at some things and try to help.

This is what I'm gathering:
You have Pangolin running on a VPS and Newt running at home, and that link works just fine, and you can forward on to Jellyfin as you would expect.

You are trying to connect Pangolin to an existing wireguard server you have running at home? Wouldn't you want to hook Pangolin to a wireguard client that's installed at home?

If you're just trying to do a normal wireguard tunnel to your home network, I've done this by added a second site using the wireguard option.

I know there isn't exactly server and client for wireguard, I'm just using server as the thing with the public IP and client as the thing you want to connect to the server.

Or maybe I'm missing your end goal here. Sorry I couldn't be more help.

<!-- gh-comment-id:2887255294 --> @mellow65 commented on GitHub (May 16, 2025): I'm sorry, I've read through your post several times, and I'm still confused on what you're trying to do. Also I'm not super well versed in all of this, but I have been messing around with Pangolin a lot, so maybe I can poke at some things and try to help. This is what I'm gathering: You have Pangolin running on a VPS and Newt running at home, and that link works just fine, and you can forward on to Jellyfin as you would expect. You are trying to connect Pangolin to an existing wireguard server you have running at home? Wouldn't you want to hook Pangolin to a wireguard client that's installed at home? If you're just trying to do a normal wireguard tunnel to your home network, I've done this by added a second site using the wireguard option. I know there isn't exactly server and client for wireguard, I'm just using server as the thing with the public IP and client as the thing you want to connect to the server. Or maybe I'm missing your end goal here. Sorry I couldn't be more help.
Author
Owner

@fredmorais commented on GitHub (May 18, 2025):

Hey, no need to apologize!

I've been searching online and I think Headscale is better suited for what I am trying to achieve. Thank you for the help nonetheless!

<!-- gh-comment-id:2889057746 --> @fredmorais commented on GitHub (May 18, 2025): Hey, no need to apologize! I've been searching online and I think Headscale is better suited for what I am trying to achieve. Thank you for the help nonetheless!
Author
Owner

@github-actions[bot] commented on GitHub (Jun 2, 2025):

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:2928199781 --> @github-actions[bot] commented on GitHub (Jun 2, 2025): 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.
Author
Owner

@github-actions[bot] commented on GitHub (Jun 16, 2025):

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.

<!-- gh-comment-id:2974797428 --> @github-actions[bot] commented on GitHub (Jun 16, 2025): 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.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/pangolin#3521