-
-
Notifications
You must be signed in to change notification settings - Fork 5.4k
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 #6475
Comments
|
Gitea 1.5 is now very old. Please could you update to 1.7.5. Our development is very rapid and there have been a number of security issues discovered since 1.5. |
Yesterday I executed the code At the bottom of the page is written 1.5.0-dev.
I'm confused. |
So am I! Ok how did you build Gitea? What If you're using sqlite you need to build: TAGS="bindata sqlite sqlite_unlock_notify" make generate build |
I didn’t use any tags when installing, I just executed command I do not use sqlite, I use MySQL . |
Ok please read: https://docs.gitea.io/en-us/install-from-source/ |
Yes, I watched it. |
It seems sometimes connecting your mysql databases failed? |
In var/log/mysql/error.log there are no errors during the appearance of Error-500. The database is located on the same server as Gitea. |
In the file var/log/syslog, I found some more such errors: .../log/gitea.log Maybe this concerns my problem? go-sql-driver/mysql#674 |
I think gitea should add |
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. |
[x]
):gitea.log:
2019/03/31 04:00:19 [...routers/user/auth.go:90 checkAutoLogin()] [E] AutoSignIn: GetUserByName: invalid connection
Description
New installation, 1 user, 0 repositories.
Appears in a variety of places. When you refresh the page, the error disappears.
I installed from source code.gitea,io, the domain is linked via nginx, there are no errors in nginx (error.log).
Help, please and sorry for my english.
The text was updated successfully, but these errors were encountered: