-
-
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
500 Server Error after login if User has no allowed visibility mode #23211
Comments
I also noticed this problem when I use helm chart to deploy gitea server. I don't think it is safe to change |
I experienced this problem on the instance installed on my k3s cluster using helm chart. Aside from the BIG 500, login page will report |
Could you give some logs about the 500 error. |
@lunny just grabbed the most relevant part
Edit: add a slightly different log
|
…itea#24903) Backport go-gitea#24867 by @lunny Fix go-gitea#23211 Replace go-gitea#23496 --------- Co-authored-by: Lunny Xiao <xiaolunwen@gmail.com> (cherry picked from commit 275abd6)
Description
I would expect to see some message, that tells the user, that his visibility is not allowed or something else more useful than an Internal Server Error, so he knows, he can change his visibility to avoid this error the next time.
The Admin will see the error and the reason for it the next time he checks the logs.
It would also make sense to add the information to the documentation of app.ini, so if someone makes a change on ALLOWED_USER_VISIBILITY_MODES, he knows about that.
Gitea Version
1.18.5
Can you reproduce the bug on the Gitea demo site?
No
Log Gist
No response
Screenshots
No response
Git Version
No response
Operating System
Cent OS 7
How are you running Gitea?
i use an release from Github on Uberspace
see this Guide for more info:
https://lab.uberspace.de/guide_gitea/
Database
MySQL
The text was updated successfully, but these errors were encountered: