After adding 3 Windows PCs as Pangolin Sites via WireGuard, I wasn't able to create a new Private Resource and select any of those as the private resource site because the dropdown only showed me my Newt-based sites.
Environment
OS Type & Version: Ubuntu 22.04
Pangolin Version: 1.16.2
Gerbil Version: 1.3.0
Traefik Version: 3.6
Newt Version:
Olm Version:
To Reproduce
Visit your pangolin dashboard and add a new site using the "WireGuard Tunnel" option.
Go to your private resources page and click the "+ Add Resource" button.
Click on the dropdown menu labeled "Site" within the dialog. The previously added site won't be listed here.
Expected Behavior
Visit your pangolin dashboard and add a new site using the "WireGuard Tunnel" option.
Go to your private resources page and click the "+ Add Resource" button.
Click on the dropdown menu labeled "Site" within the dialog and select your newly created site.
Originally created by @nulldoubt on GitHub (Mar 24, 2026).
Original GitHub issue: https://github.com/fosrl/pangolin/issues/2701
### Describe the Bug
After adding 3 Windows PCs as Pangolin Sites via WireGuard, I wasn't able to create a new Private Resource and select any of those as the private resource site because the dropdown only showed me my Newt-based sites.
### Environment
- OS Type & Version: Ubuntu 22.04
- Pangolin Version: 1.16.2
- Gerbil Version: 1.3.0
- Traefik Version: 3.6
- Newt Version:
- Olm Version:
### To Reproduce
1. Visit your pangolin dashboard and add a new site using the "WireGuard Tunnel" option.
2. Go to your private resources page and click the "+ Add Resource" button.
3. Click on the dropdown menu labeled "Site" within the dialog. The previously added site won't be listed here.
### Expected Behavior
1. Visit your pangolin dashboard and add a new site using the "WireGuard Tunnel" option.
2. Go to your private resources page and click the "+ Add Resource" button.
3. Click on the dropdown menu labeled "Site" within the dialog and select your newly created site.
@LaurenceJJones commented on GitHub (Mar 24, 2026):
Hey 👋🏻
This is expected because WireGuard doesnt natively support NAT hole punching and relaying capabilities so currently private resources are only available for newt sites so not a bug but intended, however, I realized the documentation doesnt explain this clearly so will make sure this is known. it is documented here but will reiterate it inside the resources section.
edit: also we rely on Newt to do packet enforcement rules (can user access tcp 22? etc etc) which wireguard cannot do by itself without manual rules intervention.
<!-- gh-comment-id:4119702730 -->
@LaurenceJJones commented on GitHub (Mar 24, 2026):
Hey 👋🏻
This is expected because WireGuard doesnt natively support NAT hole punching and relaying capabilities so currently private resources are only available for newt sites so not a bug but intended, however, I realized the documentation doesnt explain this clearly so will make sure this is known. [it is documented here](https://docs.pangolin.net/manage/sites/understanding-sites#basic-wireguard-site) but will reiterate it inside the resources section.
edit: also we rely on Newt to do packet enforcement rules (can user access tcp 22? etc etc) which wireguard cannot do by itself without manual rules intervention.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Originally created by @nulldoubt on GitHub (Mar 24, 2026).
Original GitHub issue: https://github.com/fosrl/pangolin/issues/2701
Describe the Bug
After adding 3 Windows PCs as Pangolin Sites via WireGuard, I wasn't able to create a new Private Resource and select any of those as the private resource site because the dropdown only showed me my Newt-based sites.
Environment
To Reproduce
Expected Behavior
@LaurenceJJones commented on GitHub (Mar 24, 2026):
Hey 👋🏻
This is expected because WireGuard doesnt natively support NAT hole punching and relaying capabilities so currently private resources are only available for newt sites so not a bug but intended, however, I realized the documentation doesnt explain this clearly so will make sure this is known. it is documented here but will reiterate it inside the resources section.
edit: also we rely on Newt to do packet enforcement rules (can user access tcp 22? etc etc) which wireguard cannot do by itself without manual rules intervention.
@LaurenceJJones commented on GitHub (Mar 24, 2026):
https://github.com/fosrl/docs-v2/pull/89