Skip to content
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

Closed
2 of 6 tasks
binfalse opened this issue Jan 6, 2021 · 4 comments · Fixed by #14287
Closed
2 of 6 tasks

2FA issues in dev version #14271

binfalse opened this issue Jan 6, 2021 · 4 comments · Fixed by #14287
Labels

Comments

@binfalse
Copy link

binfalse commented Jan 6, 2021

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

[E] PANIC: interface conversion: interface {} is nil, not string

see: https://gist.github.com/binfalse/2ca6706fb1244545649f218af1c6bce2 -- please note:

  • I replaced sensitive information with placeholders
  • even though I set COLORIZE = false the messages are apparently still colorized.. not sure what's going wrong there...? Just ignore the #011 commands..
  • logs went through rsyslog -> extra syslog prefixes, see https://binfalse.de/2018/02/21/logging-with-docker/

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

@techknowlogick
Copy link
Member

@6543
Copy link
Member

6543 commented Jan 8, 2021

@binfalse can you use memory instead of file to fix it until it is fixed on master?

https://docs.gitea.io/en-us/config-cheat-sheet/#session-session

@6543
Copy link
Member

6543 commented Jan 8, 2021

fix: #14287

@binfalse
Copy link
Author

binfalse commented Jan 8, 2021

sure! thanks for the quick response!

you're doing great and important work guys!! :)

@go-gitea go-gitea locked and limited conversation to collaborators Feb 11, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants