mirror of
https://github.com/fosrl/pangolin.git
synced 2026-07-21 17:34:41 -05:00
Infinite redirect after upgrade to 1.7.1 #500
No Assignees
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: github-starred/pangolin#500
Reference in New Issue
Block a user
Originally created by @RomRider on GitHub (Jul 18, 2025).
After updating to 1.7.1, I get an infinite redirect loop between
/setupand/after login using OIDC and thus can't connect anymore.There's nothing in the logs.
@R-Nabil commented on GitHub (Jul 18, 2025):
I have the same exact issue.
Funnily other services routes through pangolin works fine.
@miloschwartz commented on GitHub (Jul 18, 2025):
Are there any browser logs or server side logs that seem to correspond to this? Will get a patch out asap once I can replicate.
@R-Nabil commented on GitHub (Jul 18, 2025):
Let me know how I can help but as of now I don't see any logs
@DJKatastrof commented on GitHub (Jul 18, 2025):
I thought something was wrong with my instance lol. But im having the same issue
@pinionless commented on GitHub (Jul 18, 2025):
I had this issue.
I Removed Pocket ID user (delete) from Pangolin.
Logged in again with Pocket ID to auto create new user and it works now without redirect loop
@boomam commented on GitHub (Jul 18, 2025):
Same issue for me, too.
v1.7.2
Removing the OIDC user from the system doesnt fix it either.
Instead login drops me back to the login screen despite the validation step returning a green 'connected' tick for a second or so.
Checking the user list at org level with the admin user shows the OIDC user getting created though.
@R-Nabil commented on GitHub (Jul 18, 2025):
May I ask how did you remove the user ?
@pinionless commented on GitHub (Jul 18, 2025):
Well, Pocket ID account is separate to the admin account defined in the yml: "users: server_admin:"
So I deleted all cookies for my pangolin.domain.com and logged in using the login/password
@R-Nabil commented on GitHub (Jul 18, 2025):
ok. for me logging in as the admin also fails with the same infinite loop.
I set up a passkey, which could be why maybe ?
So clearing cookies didn't help, nor can I delete the non-admin user.
@pinionless commented on GitHub (Jul 18, 2025):
I just added passkey in pangolin and can access the server admin account with both login/password or passkey
I only had the loop issue with a Pocket ID accounts.
also,
I don't see the "users: server_admin:" I have in my config.yml in the documentation. I got some outdated config I quess
@Goreden commented on GitHub (Jul 18, 2025):
I thought I was the only one whose stuck in an infinite loop.
@LeonvanHeerden commented on GitHub (Jul 18, 2025):
I started having the issue after adding a new resource.
I thought it was as a result of the domain that I entered on the
HTTPS Settingssection. I entered my main domain with no subdomain. It seems that you are able to enter your primary Pangolin DNS entry for a resource, and it accepts it.E.g.
Pangolin FQDN:
p.example.comNew Resource should be :
resource.p.example.comBut I entered:
p.example.comThe old screen had a "Subdomain" edit field and you could select a domain you wanted from a drop down. So it was not possible to duplicate your pangolin FQDN on a resource.
I had to restore my backup DB to be able to get back into the system.
@oschwartz10612 commented on GitHub (Jul 18, 2025):
Looking into it now!
@elcajon commented on GitHub (Jul 18, 2025):
Exactly what I observed. If I login using my local Pangolin Account everything works fine. Logging in using my OIDC (Pocket ID) I'm looping between my Pangolin domain and the /setup path.
@miloschwartz commented on GitHub (Jul 18, 2025):
Was able to reproduce and think I found the issue in the code. Doing more tests then will get a fix out asap
@miloschwartz commented on GitHub (Jul 18, 2025):
Should be fixed in latest 1.7.3
@R-Nabil commented on GitHub (Jul 18, 2025):
Hey.
For me the redirect loop is fixed. Thank you.
However I still can't login with username/password and passkey. Is there a way I can reset the passkey through CLI or else ?
@Matt-CyberGuy commented on GitHub (Jul 18, 2025):
Unfortunately the new version only corrects the login loop. Within an org after adding a user and then authenticating through OIDC, while logged in my user within the org exists and I can browse whatever I've been given access to, but once I log out, and back in, the user disappears and the user looses access to everything.
@Matt-CyberGuy commented on GitHub (Jul 19, 2025):
Ok... I think I resolved it. for my OIDC set up, I had 'Auto Provision Users' enabled, thinking this was something I wanted for users that I had given access to already in my Authentik directory.
Once I disabled this and removed the user that was auto-created when I logged in, the issue above went away... looks like the option conflicts with the org directory somehow.
@boomam commented on GitHub (Jul 19, 2025):
It's likely related to #737