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

[GH-ISSUE #1862] New Sites Greyed Out / Only “Local” Option Available After Update — Remote NEWTs Cannot Access Resources #2030

New Issue
Closed
opened 2026-04-16 08:58:39 -05:00 by GiteaMirror · 7 comments
GiteaMirror commented 2026-04-16 08:58:39 -05:00
Owner
Copy Link

Originally created by @tajbuilds on GitHub (Nov 14, 2025).
Original GitHub issue: https://github.com/fosrl/pangolin/issues/1862

Originally assigned to: @oschwartz10612 on GitHub.

Describe the Bug

After updating Pangolin + Gerbil to the latest release 12 from 11, I can no longer add new Sites with “Remote” or “Exit Node” options.
Only Local is available, and every other site option is greyed out.

Additionally:

NEWT connects successfully

WebSocket establishes

Gerbil successfully adds peers

The dashboard loads through the domain

But any remote access to internal resources results in Gateway Timeout

NEWT logs on client side show no docker socket access

Traefik shows errors fetching dynamic config from Pangolin

This was all working before the update.

Environment

Server (Exit Node):

Oracle Cloud VM – Ubuntu 24.04

Docker Engine 27

Docker Compose v2

Running:

fosrl/pangolin:latest

fosrl/gerbil:latest

traefik:v3.4.0

Client NEWTs (multiple):

Synology (DSM 7.x)

Another laptop (Ubuntu)

Both NEWTs show connected but no docker socket access

Networking:

Oracle VCN ingress rules opened:

TCP 80, 443, 5013, 22

UDP 51820, 21820

Traefik running via network_mode:service pattern (as per docs)

DNS + Cloudflare well configured

To Reproduce

Deploy Pangolin + Gerbil using current fosrl/pangolin:latest and fosrl/gerbil:latest

Add NEWT from Synology + another device

NEWT connects and is visible

Go to Sites → Add Site

Only Local is selectable. Remote options are greyed out.

Selecting an added site → accessing internal resource → results in Gateway Timeout

Expected Behavior

Remote sites should be selectable

NEWT with active connection should have Docker socket access detected

Remote access via tunnel should work

Pangolin → Traefik dynamic config endpoint should not timeout

Originally created by @tajbuilds on GitHub (Nov 14, 2025). Original GitHub issue: https://github.com/fosrl/pangolin/issues/1862 Originally assigned to: @oschwartz10612 on GitHub. ### Describe the Bug After updating Pangolin + Gerbil to the latest release 12 from 11, I can no longer add new Sites with “Remote” or “Exit Node” options. Only Local is available, and every other site option is greyed out. Additionally: NEWT connects successfully WebSocket establishes Gerbil successfully adds peers The dashboard loads through the domain But any remote access to internal resources results in Gateway Timeout NEWT logs on client side show no docker socket access Traefik shows errors fetching dynamic config from Pangolin This was all working before the update. ### Environment Server (Exit Node): Oracle Cloud VM – Ubuntu 24.04 Docker Engine 27 Docker Compose v2 Running: fosrl/pangolin:latest fosrl/gerbil:latest traefik:v3.4.0 Client NEWTs (multiple): Synology (DSM 7.x) Another laptop (Ubuntu) Both NEWTs show connected but no docker socket access Networking: Oracle VCN ingress rules opened: TCP 80, 443, 5013, 22 UDP 51820, 21820 Traefik running via network_mode:service pattern (as per docs) DNS + Cloudflare well configured ### To Reproduce Deploy Pangolin + Gerbil using current fosrl/pangolin:latest and fosrl/gerbil:latest Add NEWT from Synology + another device NEWT connects and is visible Go to Sites → Add Site Only Local is selectable. Remote options are greyed out. Selecting an added site → accessing internal resource → results in Gateway Timeout ### Expected Behavior Remote sites should be selectable NEWT with active connection should have Docker socket access detected Remote access via tunnel should work Pangolin → Traefik dynamic config endpoint should not timeout
GiteaMirror added the needs investigating label 2026-04-16 08:58:39 -05:00
GiteaMirror commented 2026-04-16 08:58:42 -05:00
Author
Owner
Copy Link

@Lokowitz commented on GitHub (Nov 14, 2025):

Hi @TajFOT please try the fix mentioned here https://github.com/fosrl/pangolin/issues/1724#issuecomment-3435455019
@oschwartz10612 maybe a db migration for the next release would be beneficial.

<!-- gh-comment-id:3533260530 --> @Lokowitz commented on GitHub (Nov 14, 2025): Hi @TajFOT please try the fix mentioned here https://github.com/fosrl/pangolin/issues/1724#issuecomment-3435455019 @oschwartz10612 maybe a db migration for the next release would be beneficial.
GiteaMirror commented 2026-04-16 08:58:42 -05:00
Author
Owner
Copy Link

@StarkZarn commented on GitHub (Nov 27, 2025):

This appears to still be an issue, as of a fresh install for some podman experimentation 2 days ago. Even with the DB subnet update, and commenting out the orgs.subnet_group key in the config file, I still have the issue. The orgs.subnet_group key is still mentioned in the documentation fwiw, which is contrary to the commenter in #1724

<!-- gh-comment-id:3586859189 --> @StarkZarn commented on GitHub (Nov 27, 2025): This appears to still be an issue, as of a fresh install for some podman experimentation 2 days ago. Even with the DB subnet update, and commenting out the `orgs.subnet_group` key in the config file, I still have the issue. The `orgs.subnet_group` key is still mentioned in the documentation fwiw, which is contrary to the commenter in #1724
GiteaMirror commented 2026-04-16 08:58:43 -05:00
Author
Owner
Copy Link

@dereksanders7 commented on GitHub (Dec 9, 2025):

I resolved this by removing my "local" site temporarily

<!-- gh-comment-id:3630213842 --> @dereksanders7 commented on GitHub (Dec 9, 2025): I resolved this by removing my "local" site temporarily
GiteaMirror commented 2026-04-16 08:58:44 -05:00
Author
Owner
Copy Link

@whitestrake commented on GitHub (Dec 9, 2025):

Only just ran into this issue. My install has been around for a while, gone through a bunch of config migration.

The resolution in my case was also to delete the Local site I was using (thanks dereksanders7). Remaking the Local site immediately afterwards, I was still able to make new Newt sites too. Luckily I only had two or three local targets to fix up after, not too much trouble.

<!-- gh-comment-id:3634759066 --> @whitestrake commented on GitHub (Dec 9, 2025): Only just ran into this issue. My install has been around for a while, gone through a bunch of config migration. The resolution in my case was also to delete the Local site I was using (thanks dereksanders7). Remaking the Local site immediately afterwards, I was still able to make new Newt sites too. Luckily I only had two or three local targets to fix up after, not too much trouble.
GiteaMirror commented 2026-04-16 08:58:45 -05:00
Author
Owner
Copy Link

@Re4mstr commented on GitHub (Dec 10, 2025):

I am having this issue as well. Been around a long time as well.. I have 40 resources, so I'm not very interested in fixing up all of those if I dare delete the current local site..

<!-- gh-comment-id:3635857573 --> @Re4mstr commented on GitHub (Dec 10, 2025): I am having this issue as well. Been around a long time as well.. I have 40 resources, so I'm not very interested in fixing up all of those if I dare delete the current local site..
GiteaMirror commented 2026-04-16 08:58:46 -05:00
Author
Owner
Copy Link

@heroichaiku commented on GitHub (Dec 12, 2025):

I was messing around with a number of things to try resolve this issue for myself. Now, FWIW, I don't have either a) a massive configuration or b) much experience with pangolin.

What did help in my case was systemctl gerbil restart probably won't help in 99.9% of cases but hopefully it'll work for someone out there.

<!-- gh-comment-id:3647772339 --> @heroichaiku commented on GitHub (Dec 12, 2025): I was messing around with a number of things to try resolve this issue for myself. Now, FWIW, I don't have either a) a massive configuration or b) much experience with pangolin. What did help in my case was `systemctl gerbil restart` probably won't help in 99.9% of cases but hopefully it'll work for someone out there.
GiteaMirror commented 2026-04-16 08:58:46 -05:00
Author
Owner
Copy Link

@oschwartz10612 commented on GitHub (Jan 20, 2026):

I think this is a duplicate of https://github.com/fosrl/pangolin/issues/1806. Please LMK if not!

<!-- gh-comment-id:3771149629 --> @oschwartz10612 commented on GitHub (Jan 20, 2026): I think this is a duplicate of https://github.com/fosrl/pangolin/issues/1806. Please LMK if not!
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 needs investigating
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#2030
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?