-
-
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
2FA issues in dev version #14271
Labels
Comments
The specific line that is erroring is https://github.com/go-gitea/gitea/blob/master/routers/user/setting/security_twofa.go#L192 |
Closed
@binfalse can you use https://docs.gitea.io/en-us/config-cheat-sheet/#session-session |
fix: #14287 |
sure! thanks for the quick response! you're doing great and important work guys!! :) |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
:latest
)[x]
):Description
2FA seems to be broken in the current dev version.
I've had 2FA enabled and couldn't log in anymore after I updated the Docker image. After some debugging I disabled 2FA for my account (by deleting the corresponding line in the
two_factor
table) and was able to login again. (Actually, I needed to clean cookies as well, as it was then asking me for a scratch code...)When trying to re-enable 2FA I get a 500 at the frontend (I can reproduce that at https://try.gitea.io -- at least I'll get a 500 as well if I try to setup 2FA there). The logs show
see: https://gist.github.com/binfalse/2ca6706fb1244545649f218af1c6bce2 -- please note:
COLORIZE = false
the messages are apparently still colorized.. not sure what's going wrong there...? Just ignore the#011
commands..To me it looks like there is an issue with 2FA...? Let me know if you need further information or if I can do anything else to debug the issue! :)
Screenshots
Web interface just shows a 500..
The text was updated successfully, but these errors were encountered: