Identify the full database username and all applications that use it. Prepare a unique new password and a coordinated configuration update. Keep a working panel session and recent backup, and schedule a brief maintenance window if applications cannot switch credentials seamlessly.

1. Open MySQL Management and select the relevant database. Review its user list to find the exact account.
2. Choose the password-change action for that database user. Enter the new value or use the password generator, then save it securely.
3. Update each dependent application configuration promptly using its supported method. A WordPress installation, for example, needs its configured database credential to match the actual database user.
4. Protect configuration-file permissions and avoid leaving a temporary copy containing the password in a public directory.
5. Test the application and any background jobs, workers or integrations that use the same credential. Restart persistent application workers only when their configuration-loading behavior requires it.

Confirm normal reads and writes work and that scheduled tasks no longer produce authentication errors. Test a new connection, since an existing pooled session can hide a configuration problem temporarily.

If access fails, compare the complete prefixed username, connection host and saved password rather than repeatedly changing unrelated database names. If several applications shared the user, update all of them or plan a move to separate users. Do not paste the password into support logs; provide the sanitized error and account reference.

• Creating a MySQL or MariaDB database in DirectAdmin
• Setting database-user privileges in DirectAdmin
• Creating an additional database user in DirectAdmin
• Checking and optimizing database tables in DirectAdmin

• DirectAdmin: Mariadb MySQL