{"id":3729,"date":"2023-04-04T18:13:48","date_gmt":"2023-04-04T17:13:48","guid":{"rendered":"https:\/\/www.dpscomputing.com\/blog\/?p=3729"},"modified":"2023-04-04T18:19:19","modified_gmt":"2023-04-04T17:19:19","slug":"access-denied-for-user-rootlocalhost-mysql-error","status":"publish","type":"post","link":"https:\/\/www.dpscomputing.com\/blog\/2023\/04\/04\/access-denied-for-user-rootlocalhost-mysql-error\/","title":{"rendered":"Access denied for user ‘root’@’localhost’ – MySQL Error"},"content":{"rendered":"
\n
\"\"<\/figure><\/div>\n\n\n

You’ve landed here in frustration whilst developing your latest database-driven creation and want an answer to the question – how to fix “Access denied for user ‘root’@’localhost'”. Well, you’ve come to the right place. <\/p>\n\n\n\n

As we’re sure you are aware, this error is triggered by your MySQL database<\/a> and unfortunately, as is the case for any developer, errors are a common way of life. This error can be uber-frustrating due to the fact it’s likely brought down your ENTIRE app – after all, the error literally means that your application or website cannot connect successfully to your database. <\/p>\n\n\n\n

Let’s fix it. <\/p>\n\n\n\n

Check your creds!<\/h2>\n\n\n\n

Firstly, before we move on – and we know it’s the standard level one tech support answer (but it’s this because it’s so often right!), check your credentials – i.e. your username and password. Now, you’ve either forgotten your password (you should be using a good password manager<\/a> by this point!) or you’ve never set one and aren’t sure. <\/p>\n\n\n\n

If this is a production environment, check with your dev lead. If that’s you, berate yourself for forgetting. <\/p>\n\n\n\n

If it’s a development environment and you’re thinking “but I’ve never set a ***** password” then fortunately, we are likely to know it ;). If you’re using AMPPS or similar software for local development then there’s every chance that your username and password are:<\/p>\n\n\n\n

Username – root<\/p>\n\n\n\n

Password – password<\/p>\n\n\n\n

Go check it out – and hopefully that’s the end of your nightmare with this error!<\/p>\n\n\n\n

For a bit of background, all MySQL databases come with a root password. This can be used to access any database or table on your setup. NOTE: this is NOT recommended for use in a production environment – set up a user specifically for the database\/table that your application needs to access. <\/p>\n\n\n\n

If you are in a local development and you have changed the root users password – that’s the one that you’ll need to use. If you can’t remember it, we’re going to tell you how to reset it further on so keep reading…<\/p>\n\n\n\n

MySQL Privileges<\/h2>\n\n\n\n

If it’s not the password (90% of the time it is!) then next stop is to check your MySQL privileges. Just like a child, a MySQL privilege provides permission to each MySQL user (including root users) to do something. Including logging in. <\/p>\n\n\n\n

The error message Access denied for user ‘root’@’localhost’ can appear if your MySQL user account is trying to do something (i.e. have sufficient privileges) to access the database. This is a curious one with the root user – as by default it has privileges to do anything – but if you’ve been tinkering around in your setup it IS possible that you’ve modified the privileges to lock yourself out. <\/p>\n\n\n\n

You can easily check the privileges of any user in the MySQL console. Run the following command on your MySQL server to check the root user privileges. <\/p>\n\n\n\n

SHOW GRANTS FOR 'root'@'localhost';\r\n\r<\/code><\/pre>\n\n\n\n
See ‘grants’ as like the keys to the city that your user possesses.  This will show you all privileges associated with the root user account.  Want to check out a different account?  Just replace root with the name of your user.  For example, if our user was called ‘test’ we would use the following command:<\/p>\n\n\n\n
SHOW GRANTS FOR 'test'@'localhost';<\/code><\/pre>\n\n\n\n
Granting Privileges<\/h2>\n\n\n\n
So, you’ve worked out you don’t have the privileges you thought you had?  Or you’re on a development environment and your really not sure?  Well, we can fix that using a super-special command:<\/p>\n\n\n\n
GRANT ALL PRIVILEGES ON *.* TO 'root'@'localhost' IDENTIFIED BY 'password';<\/code><\/pre>\n\n\n\n
In the above code choose a password and place it where it says ‘password’.  This should be a secure, auto-generated, long and complex password UNLESS you’re on a development environment – in which case it’s fine to use ‘password’ if security is not a concern and you value your sanity which is slowly ebbing away whilst trying to fix this error!  <\/p>\n\n\n\n
The other side effect that this command will have is it will grant ALL privileges to the root account – which is really the way it should be and the way it was configured by default.  BEWARE: the root account should be locked down if this is a Production environment!<\/p>\n\n\n\n
Check your MySQL Config<\/h2>\n\n\n\n
OK, so if it’s not the password nor the privileges it’s time for ever developers nightmare – diving into the MySQL config.  <\/p>\n\n\n\n
Open up the MySQL config file in your favourite text editor.  Sometimes the pesky “Access denied for user ‘root’@’localhost'” can be caused because your MySQL config is totally messed up.  <\/p>\n\n\n\n
Did you make changes recently?  You took a backup of course so simply replace the current file with your backup when it last worked?  Out of luck?  Well, your options are to download a default MySQL config file or try to fix the swamp of a mess you MAY have made whilst trying to tinker with it.  <\/p>\n\n\n\n
Either way, we need to check that the MySQL configuration file has the correct settings.  <\/p>\n\n\n\n
“Where is the MySQL configuration file?” I hear you ask… In the blind panic since the error appeared you’ve totally forgotten where it is.  Fear not and look under the MySQL directions (\/etc\/my.cnf or \/etc\/mysql\/) and look for the file called my.cnf.  <\/p>\n\n\n\n
Once open, we’re going to get down to business and search for this line of config:<\/p>\n\n\n\n
[mysqld]\r\nskip-grant-tables<\/code><\/pre>\n\n\n\n
Not there?  Add it in.  <\/p>\n\n\n\n
WARNING!!!!!  This config option will SKIP the password check – so if it’s in production, it is not recommended.  At least lock down your website using protected folders or similar otherwise ANYONE will be able to access your MySQL database without a password.  <\/p>\n\n\n\n
The line above skips the password check which allows you access and therefore enables you to change the root users password to something more memorable.  <\/p>\n\n\n\n
Once you’ve done this – don’t forget to actually delete the lines again:<\/p>\n\n\n\n
[mysqld]\nskip-grant-tables<\/code><\/pre>\n\n\n\n
Write yourself a reminder on a post it so that you don’t forget (please!)<\/p>\n\n\n\n
<\/p>\n\n\n\n
Reset the MySQL Root Password<\/h2>\n\n\n\n
If you’ve got to this point, you’re now desperate to fix the error.  So, as in all times of desperation, let’s just start hacking away at MySQL.  <\/p>\n\n\n\n
All has failed, all is hopeless UNLESS we reset the root users password.  to do this, you’re going to need to kill (stop) the MySQL server.  Then you can either make the config change above OR start the server with the operator –skip-grant-tables option which will have the same effect.  <\/p>\n\n\n\n
Now from the command line you’ll be able to login to MySQL without a password.  Again, please DON’T do this on a production environment!  Once you’ve ‘logged in’, run this command and you can update the root users password to something better:<\/p>\n\n\n\n
mysql> USE mysql;\r\nmysql> UPDATE user SET authentication_string=PASSWORD('new_password') WHERE User='root';\r\nmysql> FLUSH PRIVILEGES;<\/code><\/pre>\n\n\n\n
Replace ‘new_password’ in the PASSWORD() function with something awesome and hard to guess.  In development environments that are otherwise locked down you can of course use the favourite ‘password’.  The above code essentially manually updates the user table and updates password (with appropriate hashing\/salting) to the thing that you specify.  <\/p>\n\n\n\n
Final Thoughts<\/h2>\n\n\n\n
If you’re Access denied for user ‘root’@’localhost’ error hasn’t been solved by now, you’ve missed something or not done it correct.  Following the above steps is a fool-proof way to fix the access denied error no matter kind of craziness is going on in your setup.  <\/p>\n\n\n\n
If all else fails, you can always re-install your MySQL server and build it again from the ground up – but going back through and following the instructions carefully is likely to take a lot less time and cause a lot less pain!<\/p>\n\n\n\n
Let us know if the above steps have helped (or if you’ve spotted a typo) and feel free to ask us any questions below.<\/p>\n","protected":false},"excerpt":{"rendered":"
You’ve landed here in frustration whilst developing your latest database-driven creation and want an answer to the question – how to fix “Access denied for user ‘root’@’localhost’”. Well, you’ve come to the right place....<\/p>\n","protected":false},"author":1,"featured_media":3730,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"jetpack_post_was_ever_published":false,"_jetpack_newsletter_access":"","_jetpack_dont_email_post_to_subs":false,"_jetpack_newsletter_tier_id":0,"_jetpack_memberships_contains_paywalled_content":false,"_jetpack_memberships_contains_paid_content":false,"footnotes":"","jetpack_publicize_message":"","jetpack_publicize_feature_enabled":true,"jetpack_social_post_already_shared":true,"jetpack_social_options":{"image_generator_settings":{"template":"highway","enabled":false},"version":2}},"categories":[55,2138,2139],"tags":[3733,3747,2925,3734,3735,3739,3740,3741,2453,3736,3737,3744,3745,3738,3743],"class_list":["post-3729","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-articles","category-development","category-development-issues","tag-access-denied-for-user-rootlocalhost","tag-cannot-login-to-mysql","tag-mysql","tag-mysql-access-denied","tag-mysql-access-denied-error","tag-mysql-access-denied-for-user","tag-mysql-access-denied-for-user-root","tag-mysql-access-denied-for-user-rootlocalhost","tag-mysql-error","tag-mysql-errors","tag-mysql-password","tag-mysql-root-password","tag-mysql-root-password-error","tag-mysql-root-user","tag-rootlocalhost-password"],"jetpack_publicize_connections":[],"jetpack_featured_media_url":"https:\/\/www.dpscomputing.com\/blog\/wp-content\/uploads\/2023\/04\/image-9.png","jetpack_shortlink":"https:\/\/wp.me\/p3nsfA-Y9","jetpack_sharing_enabled":true,"jetpack_likes_enabled":true,"_links":{"self":[{"href":"https:\/\/www.dpscomputing.com\/blog\/wp-json\/wp\/v2\/posts\/3729"}],"collection":[{"href":"https:\/\/www.dpscomputing.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.dpscomputing.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.dpscomputing.com\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.dpscomputing.com\/blog\/wp-json\/wp\/v2\/comments?post=3729"}],"version-history":[{"count":2,"href":"https:\/\/www.dpscomputing.com\/blog\/wp-json\/wp\/v2\/posts\/3729\/revisions"}],"predecessor-version":[{"id":3732,"href":"https:\/\/www.dpscomputing.com\/blog\/wp-json\/wp\/v2\/posts\/3729\/revisions\/3732"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.dpscomputing.com\/blog\/wp-json\/wp\/v2\/media\/3730"}],"wp:attachment":[{"href":"https:\/\/www.dpscomputing.com\/blog\/wp-json\/wp\/v2\/media?parent=3729"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.dpscomputing.com\/blog\/wp-json\/wp\/v2\/categories?post=3729"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.dpscomputing.com\/blog\/wp-json\/wp\/v2\/tags?post=3729"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}