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

[E] Failed to initialize ORM engine: this user requires mysql native password authentication. #3876

Closed
2 of 7 tasks
brian9206 opened this issue May 1, 2018 · 3 comments · Fixed by #4161
Closed
2 of 7 tasks
Labels
type/enhancement An improvement of existing functionality
Milestone

Comments

@brian9206
Copy link

  • Gitea version (or commit ref): 1.4
  • Git version:
  • Operating system: CentOS 7
  • Database (use [x]):
    • PostgreSQL
    • MySQL
    • MSSQL
    • SQLite
  • Can you reproduce the bug at https://try.gitea.io:
    • Yes (provide example URL)
    • No
    • Not relevant
  • Log gist:

Description

MySQL version: 8.0

The server won't start up and the log shows the following error message:

[...itea/routers/init.go:60 GlobalInit()] [E] Failed to initialize ORM engine: this user requires mysql native password authentication.

This error is caused by the go-sql-driver/mysql.
It seems there is no way to set AllowNativePasswords in gitea config

Is there any workaround for this issue?

@lunny lunny added the status/blocked This PR cannot be merged yet, i.e. because it depends on another unmerged PR label May 2, 2018
@lunny
Copy link
Member

lunny commented May 2, 2018

It seems gitea could add allowNativePasswords options on connstr to do that.

@lunny lunny added type/enhancement An improvement of existing functionality and removed status/blocked This PR cannot be merged yet, i.e. because it depends on another unmerged PR labels May 2, 2018
@brian9206
Copy link
Author

so there is no workaround for now? my server is down because of that at the moment

@silverwind
Copy link
Member

there is no workaround for now?

See gogs/gogs#5187 (comment)

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
type/enhancement An improvement of existing functionality
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants