-
-
Notifications
You must be signed in to change notification settings - Fork 5.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Error 500 on first OAuth login attempt after restart #5005
Comments
Although I’ve seen this multiple times, I can’t find the right conditions to reproduce it and it’s not as simple as just restarting. I’ll close for now and reopen later if I can reproduce. |
This is still plaguing me on 1.9-dev. It looks like it's related to this error in the logs:
|
This should be resolved by #6467 |
It doesn't seem to be. |
See also: #3837 (comment) |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs during the next 2 weeks. Thank you for your contributions. |
Just to notify I just had the same error |
Hello For information, I manage server related by @benchti , we can do any test required. Note it's now updated to 1.9.2 |
I had a similar issue still on v1.13.0-rc1 with Nextcloud OAuth2 provider at the first login with a new account. |
|
I have exactly the same issue using Gitea v1.13.7:-
|
I suspect it's some issue to do with the loginsources not registering their providers with gothic (or not actually completely registered by the time that it comes to login.) I think however that the use of gothic here is probably incorrect and we should just use goth or just the providers directly ourselves. I guess I will have a look in #16199 or after that is merged. |
Hey, |
For this error: [E] UserSignIn: could not find a matching session for this request Two possibilities:
I think this issue could be closed |
[x]
):Description
Every time I first start gitea, the very first login attempt with oauth will result in a 500 error.
It doesn't happen again even if I clear the browser application cache.
It doesn't happen again even if I revoke the oauth app and go through the oauth flow again.
I believe I can narrow it down more, but I've experienced it in production several times after upgrading and restarting. I'll have to set up a dev environment to test it and get the logs (in prod the HTTP GETs just blow everything else away pretty quickly).
The text was updated successfully, but these errors were encountered: