Can't log in, HTTP 401 error, "authorization request has expired", possible cookies issue #451
Labels
No labels
bug
chore
documentation
enhancement
help
in-progress
question
ready-for-release
released
translation
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
adam/gate#451
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
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?
Describe the bug:
I really wish I could give a clear description but it's so unclear to me what is going on under the hood. If I try to log in with Vivaldi (Flatpak), I usually get a login loop similar to #120. Sometimes I don't. There is no obvious reason it does or doesn't work. Sometimes trying in a fresh incognito tab works, sometimes it doesn't — sometimes minutes apart it will go from working to not working. Today I started getting a brand new variation I haven't seen before where for some reason my browser requests
/oidc/auth/ZoKiDnVA93biCsqFI3U3S0nUll6tEg3acRx4atH2CVnand receives the response{"error":"invalid_request","error_description":"authorization request has expired"}. An incognito tab does not have this behavior and just login loops similar to issue #120. I switched to:edgeand setENABLE_DEBUG: trueand found no clear help in the logs, but I will include them. #337 might also be related since I only use a passkey and do not use a password for this account.To Reproduce:
Attempt to log in.
Expected behavior:
Login succeeds.
Database Driver:
Screenshots:
Additional context:
Note that for the following logs, I have replaced my real public ip address with 1.2.3.4, and my real domain with example.com.
Logs for non-incognito tab (I have cleared all cookies and site data that I could find, to no avail):
Logs for incognito tab:
Eight hours later and when I tried again everything works fine. No rhyme or reason that I can figure out, but it working hours later has me continuing to think it's related to cookies or some other local data expiring and the frontend not handling it correctly. I'm switching back to
:latestfor now, but let me know if there is further testing you would like me to do. I'm going to leave this issue open since it's a recurring problem, not a one-off, and it's not clear to me what actually changed.I'm glad it's working for you now, weird error. From the logs you provided it looks like something wrong with the session, maybe the cookie could't be set? Feel free to continue this issue if the error pops up again