Database login failures after an upgrade can result from changed authentication requirements, outdated client software or an account configuration problem. Identify the actual error before resetting credentials or changing database users.
Check the connection details
- Record the exact application or database-client error.
- Confirm the database server version and the application’s MySQL client or PHP driver version.
- Check the application uses the correct database hostname, full database name and full username, including any control-panel prefix.
- In cPanel’s database management interface, confirm that the user is assigned to the intended database with the required privileges.
An Error establishing a database connection message is general and does not by itself prove that the password hash is incompatible.
Check authentication compatibility
Ask the administrator to compare the account’s authentication plugin with the server and client versions. For example, MySQL 8.4 disables the older mysql_native_password plugin by default. The appropriate correction depends on the actual server and driver; it is not the same for every upgrade.
Prefer updating supported client software and using the server’s supported authentication method rather than enabling a retired method globally.
Reset credentials only if required
If the password needs resetting, use the hosting panel’s password-change option for the existing database user, then update every application that uses it. Test access and retain the user’s required database assignments.
Do not delete the database to repair a login failure. Deleting and recreating a user can also remove grants and affect other applications. Back up and record dependencies before any administrator-approved account change.
If the failure remains, provide support with the exact error and versions. Keep passwords out of logs, screenshots and support messages.