[GH-ISSUE #1081] Infinite redirect after upgrade to 1.7.1 #16733

Closed
opened 2026-05-18 16:56:38 -05:00 by GiteaMirror · 20 comments
Owner

Originally created by @RomRider on GitHub (Jul 18, 2025).
Original GitHub issue: https://github.com/fosrl/pangolin/issues/1081

After updating to 1.7.1, I get an infinite redirect loop between /setup and / after login using OIDC and thus can't connect anymore.

There's nothing in the logs.

Originally created by @RomRider on GitHub (Jul 18, 2025). Original GitHub issue: https://github.com/fosrl/pangolin/issues/1081 After updating to 1.7.1, I get an infinite redirect loop between `/setup` and `/` after login using OIDC and thus can't connect anymore. There's nothing in the logs.
Author
Owner

@R-Nabil commented on GitHub (Jul 18, 2025):

I have the same exact issue.

Funnily other services routes through pangolin works fine.

<!-- gh-comment-id:3087328780 --> @R-Nabil commented on GitHub (Jul 18, 2025): I have the same exact issue. Funnily other services routes through pangolin works fine.
Author
Owner

@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.

<!-- gh-comment-id:3087367156 --> @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.
Author
Owner

@R-Nabil 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.

Let me know how I can help but as of now I don't see any logs

<!-- gh-comment-id:3088163966 --> @R-Nabil 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. Let me know how I can help but as of now I don't see any logs
Author
Owner

@DJKatastrof commented on GitHub (Jul 18, 2025):

I thought something was wrong with my instance lol. But im having the same issue

<!-- gh-comment-id:3088693365 --> @DJKatastrof commented on GitHub (Jul 18, 2025): I thought something was wrong with my instance lol. But im having the same issue
Author
Owner

@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

<!-- gh-comment-id:3089395645 --> @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
Author
Owner

@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.

<!-- gh-comment-id:3089397234 --> @boomam commented on GitHub (Jul 18, 2025): Same issue for me, too. v1.7.2 &nbsp; 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. &nbsp; Checking the user list at org level with the admin user shows the OIDC user getting created though.
Author
Owner

@R-Nabil 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

May I ask how did you remove the user ?

<!-- gh-comment-id:3089401300 --> @R-Nabil 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 May I ask how did you remove the user ?
Author
Owner

@pinionless commented on GitHub (Jul 18, 2025):

May I ask how did you remove the user ?

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

<!-- gh-comment-id:3089407750 --> @pinionless commented on GitHub (Jul 18, 2025): > May I ask how did you remove the user ? 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
Author
Owner

@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.

<!-- gh-comment-id:3089414027 --> @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.
Author
Owner

@pinionless 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.

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

<!-- gh-comment-id:3089430187 --> @pinionless 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. 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
Author
Owner

@Goreden commented on GitHub (Jul 18, 2025):

I thought I was the only one whose stuck in an infinite loop.

<!-- gh-comment-id:3089685223 --> @Goreden commented on GitHub (Jul 18, 2025): I thought I was the only one whose stuck in an infinite loop.
Author
Owner

@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 Settings section. 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.com
New Resource should be : resource.p.example.com
But I entered: p.example.com

The 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.

<!-- gh-comment-id:3089916834 --> @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 Settings` section. 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.com` New Resource should be : `resource.p.example.com` But I entered: `p.example.com` The 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.
Author
Owner

@oschwartz10612 commented on GitHub (Jul 18, 2025):

Looking into it now!

<!-- gh-comment-id:3090231905 --> @oschwartz10612 commented on GitHub (Jul 18, 2025): Looking into it now!
Author
Owner

@elcajon 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.

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.

<!-- gh-comment-id:3090443346 --> @elcajon 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. 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.
Author
Owner

@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

<!-- gh-comment-id:3090521094 --> @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
Author
Owner

@miloschwartz commented on GitHub (Jul 18, 2025):

Should be fixed in latest 1.7.3

<!-- gh-comment-id:3091246000 --> @miloschwartz commented on GitHub (Jul 18, 2025): Should be fixed in latest 1.7.3
Author
Owner

@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 ?

<!-- gh-comment-id:3091275417 --> @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 ?
Author
Owner

@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.

<!-- gh-comment-id:3091275983 --> @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.
Author
Owner

@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.

<!-- gh-comment-id:3091282134 --> @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.
Author
Owner

@boomam 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.

It's likely related to #737

<!-- gh-comment-id:3091283926 --> @boomam 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. It's likely related to #737
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/pangolin#16733