Mysql Error: 'Access denied for user 'root'@'localhost'

The underpinnings of 'Access Denied'

"Access Denied" is the database's clinical way of saying "No trespassing!" This could be due to an incorrect password, a misconfigured authentication plugin, or you're simply not in the VIP list (user privileges).

Swapping authentication to native

Switch the root metadata to mysql_native_password for compatibility and reliability:

ALTER USER 'root'@'localhost' IDENTIFIED WITH 'mysql_native_password' BY 'new_password'; # Rebranding "root", like going from Clark Kent to Superman


Quick fix: Disable authentication

In crunch time, consider bypassing authentication. In the MySQL config file under the [mysqld] section add skip-grant-tables, or use this at startup:

mysqld_safe --skip-grant-tables --skip-networking &  # This is like going undercover, use responsibly!


My buddy Mr. GDPR wants me to remind you to use this sparingly and with caution due to potential security risks.

Sealing the deal with FLUSH PRIVILEGES

Post authentication method alterations, don't forget to seal the deal:

FLUSH PRIVILEGES;  # Like refreshing a web page, but with more privileges.


This will lock your changes into MySQL's memory bank, making your hard work permanent.

Cross-validation with user account info

You can double-check the root account by questioning the user table directly:

SELECT user, authentication_string, plugin, host FROM mysql.user WHERE user='root';  # The equivalent of asking "root": Who are you really?


Restoring order

After any fleeting changes, remember to restore balance in the force, remove temporary changes and restart the MySQL service:

sudo service mysql restart  # CTRL+ALT+DELETE for MySQL


And to enter the MySQL console with the superuser privileges:

sudo mysql -u root -p  # It's time for root to step into the limelight


A tale of strong passwords

Choosing a mighty password is like choosing your superhero name. The root password is the scepter to your database kingdom – guard it fiercely.