-
-
Notifications
You must be signed in to change notification settings - Fork 4.1k
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
[Bug]: After upgrade from PostgreSQL 13 to 14, Nextcloud is KO #31030
Comments
Thank you for taking the time to report a bug! 👍 As this seems to be a setup issue I would like to ask you to raise your question in the forums: https://help.nextcloud.com |
@szaimen I am not sure why you think this is a setup issue. It seems to me that when migrating from PostgreSQL 13 to 14, it is currently not possible to have Nextcloud working with the new default authentication scheme. I have not found in the doc any information on how to support this new scheme or how to migrate to this new scheme. It is a problem to me as Nextcloud will not benefit from the new scheme which is more robust than md5. |
@szaimen after some more research (I have spent the day on this yesterday already 😉 ), I found out how to solve this. Here is the information in case somebody else needs it. It could be interesting to add it in the documentation (in a troubleshooting section). This procedure should allow you to move from
That's it. |
@doc75 What password do you use for |
|
Oh wow, I had forgotten that was a thing. Thanks a lot! |
Thanks a lot. |
Bug description
I just upgraded my installation from postgreSQL 13 to PostgreSQL 14 (without change of Nextcloud version).
After this upgrade, Nextcloud cannot connect anymore to the DB according to the message shown in the Web browser:
I found out that this is related to the change of the default authentication scheme of PostgreSQL from
md5
toscram-sha-256
.If I get back to
md5
, it is working fine.How can we make sure Nextcloud is able to work with this new default authentication scheme of PostgreSQL ?
I am not sure if this is something for Nextcloud or for a library you are using (in the last case let me know which one).
Steps to reproduce
pg_dumpall
Expected behavior
Nextcloud should run without error message
Installation method
Official Docker image
Operating system
Debian/Ubuntu
PHP engine version
PHP 8.0
Web server
Nginx
Database engine version
PostgreSQL
Is this bug present after an update or on a fresh install?
Updated from a minor version (ex. 22.2.3 to 22.2.4)
Are you using the Nextcloud Server Encryption module?
Encryption is Disabled
What user-backends are you using?
Configuration report
List of activated Apps
Nextcloud Signing status
Nextcloud Logs
Nothing found in the log, related to this issue
Additional info
The text was updated successfully, but these errors were encountered: