mirror of
https://github.com/fosrl/pangolin.git
synced 2026-05-08 05:39:49 -05:00
Unable to create Sites #739
No Assignees
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: github-starred/pangolin#739
Reference in New Issue
Block a user
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?
Originally created by @Lokowitz on GitHub (Oct 21, 2025).
Describe the Bug
Notices today that i am not able to create a new site anymore.
NewtandBasic WGare grayed out not selectable, justLocal.So sounds like a connection problem to Gerbil. But my existing Sites and Resources are working still fine.
Maybe something related to the Gerbil default port change?
Only interesting from the logs, Gerbil is spamming all the time:
Pangolin looks good:
Environment
To Reproduce
Not sure if this can be reproduced easily. My Setup is just regulary upgraded since beta phase.
Expected Behavior
Able to add new Sites
@baldemar-wuda commented on GitHub (Oct 21, 2025):
Same thing for me.
@Lokowitz commented on GitHub (Oct 21, 2025):
And I tried to go back to older versions:
Pangolin 1.10.3 and 1.11.0
Gerbil 1.2.0 and 1.2.1
But no combination solved the issue.
@oschwartz10612 commented on GitHub (Oct 21, 2025):
e447549de1should fix this when 1.11.1 isreleased again.
@oschwartz10612 commented on GitHub (Oct 21, 2025):
Could you check the latest 1.11.1 release?
@Tuphal commented on GitHub (Oct 22, 2025):
Still not possible to add a new tunnel.
@Lokowitz commented on GitHub (Oct 22, 2025):
Also for me not working with the new image.
@Lokowitz commented on GitHub (Oct 22, 2025):
Gerbil spamming is caused through olm holepunch, I turned it off for now.
Should be related to my CGNAT IPv4, hope support for IPv6 is coming :)
@oschwartz10612 commented on GitHub (Oct 22, 2025):
Hum this is caused when there is not an exit node in the database to
assign a site to. This is usually when there is no gerbil registered but
the update should not have caused this but who knows...
Couple of questions:
Are you on enterprise or community
If you restart the whole stack
docker compose downanddocker compose upto get gerbil to register does it work?If not when this occurs could you check the console logs and network
tab in the browser debugger. Looking for an error message or a 500/400
error call to pick-site-defaults in the network tab. LMK if this is the
case.
If you have a backup database, roll back to that and then upgrade
again and see if it occurs. Make sure it still works on your old database.
Run the following commands
sudo apt install sqlite3
sqlite3 config/db/db.sqlite "SELECT * FROM exitNodes"
And then let me know what the output is
@Tuphal commented on GitHub (Oct 22, 2025):
Community edition
Gebril is connected. The first site is working without issues
This is pointing to a right direction..
The API shows:
{"data":null,"success":false,"error":true,"message":"No available subnets","status":500,"stack":null}I could not find any config variable to change the subnet. The org-subnet should be enough big for a second site.
Edit: I used DB Browser for my downloaded database. Here is the exitNodes entry:
Edit 2: Should the subnet from the site not be part of the adress?
Subnet 100.89.128.8/30Adress 100.89.128.1/24@Lokowitz commented on GitHub (Oct 23, 2025):
I got deeper in the database and found some inconsistencies in ip addresses and subnets.
I updated the database and now It is working again, maybe it was caused through a wrong migration task and/or outdated configs.
1. Check
config/config.ymlI still had the subnet group configured and this is not required anymore -> so remove
2. Check database table orgs
I have 2 orgs, one really old one (since beta phase) and one is maybe 2-3 months old
The old org has subnet
100.90.128.0/24and the newer one has100.89.138.0/20, the new default should be100.90.128.0/24, but is matching the value inconfig.yml.Line 3 is just a test org to get the default values.
3. Check database table sites
Subnet for my first site (local) is set to
0.0.0.0/0a new created is getting0.0.0.0/32.The other newt sites have
100.89.128.4/30,100.89.128.8/30,100.89.128.12/30what is looking good so far.SiteId 1, 4, 5 is associated to org 1, SiteId 9 to org 2 and SiteId 12 to org 3 (test).
And now you see that address of SiteId 9 is not matching the subnet of org 2.
Steps to fix it
100.90.128.0/240.0.0.0/32NULL100.90.128.x/24to match the org subnet (increase x for each site in the same org)@Tuphal commented on GitHub (Oct 24, 2025):
Thank you ver much @Lokowitz for the steps.
These worked perfectly !!!
In my case I only had to follow step 2 and 3
@elcajon commented on GitHub (Oct 28, 2025):
Also run into this today.
Changing the local subnet from /0 to /32 fixed it (address was already empty)
Database migration table content for reference:
@intersectRaven commented on GitHub (Nov 4, 2025):
I experienced this just yesterday and this fixed it.
@oschwartz10612 commented on GitHub (Nov 4, 2025):
Thanks so much @Lokowitz that was indeed an issue on an older version. I double checked and this should not occur on latest versions.