error establishing a database connection 3

This error has already been faced by a lot of people, but I could not find an answer in my case. My wordpress website works perfectly in local

What I have done:

• Upload with filezila
• Create a sql database in OVH -Import all the SQL tables from local to the website with phpmyadmin
• Modify the wp-config.php file and also the wp-config-sample.php writting my informations.

Thanks for your help !!

This error has already been faced by a lot of people, but I could not find an answer in my case. My wordpress website works perfectly in local

What I have done:

• Upload with filezila
• Create a sql database in OVH -Import all the SQL tables from local to the website with phpmyadmin
• Modify the wp-config.php file and also the wp-config-sample.php writting my informations.

Thanks for your help !!

• database
• errors

Share Improve this question asked Jan 24, 2019 at 16:32 nolwwwnolwww 10111 bronze badge 14

• Right now it's a localhost link. Do I need to change with the real website name? – nolwww Commented Jan 24, 2019 at 16:54
• Just tried to modify siteurl and home in the wp_options with the real website name. But it didn't work. – nolwww Commented Jan 24, 2019 at 17:04
• Can you change the name wp-config.php and enter the DB credentials in the installation wizard to see if it will connect? Don't finish installation, just check DB connection. – nmr Commented Jan 24, 2019 at 17:15
• I already modified the wp-config but it didn't work, I get this error. Maybe the localhost is wrong though. The host is OVH. I tried mysql5-21. – nolwww Commented Jan 24, 2019 at 17:18
• I modified the localhost in wp-config.php , and now, I don't have the same error, but a: 504 gateway time out – nolwww Commented Jan 24, 2019 at 17:39

 |  Show 9 more comments

1 Answer 1

Sorted by: Reset to default 0

I too had faced the same issue many times but after refreshing the browser it solved my problem.

Kindly check the wp-config file and verify if the database name and other information is correct.

Another thing you can try is restarting your local host.