Could not connect to database-server (when authenticating) after moving website to new host

Post

Posted
Rating:
#7213 (In Topic #1787)
I finally commited to moving to a new hosting company. Old host was Arvixe, new host is MDDHosting.

MDD was able to move my webstites from the old host to my new hosts account. so far I was happy! I even checked  and the database shows up. Yipee!

Now I go and get the domain pointed to the new website location but when I go to access the website at its new location I get an error message from Composr… now what do I do?

Critical error – bailing out

Could not connect to database-server (when authenticating) (Access denied for user 'disciple_askinp7'@'r2.supportedns.com' (using password: YES))

Details here are intended only for the website/system-administrator, not for regular website users.
» If you are a regular website user, please let the website staff deal with this problem.

Depending on the error, and only if the website installation finished, you may need to edit the installation options (the _config.php file).

ocProducts maintains full documentation for all procedures and tools (including disaster recovery). These may be found on the Composr website. If you are unable to easily solve this problem, we may be contacted from our website and can help resolve it for you.


Post

Posted
Rating:
Item has a rating of 5 Item has a rating of 5 Item has a rating of 5 Item has a rating of 5 Item has a rating of 5 (Liked by Adam Edington)
#7214
I'm turing off the lights and sirens. Problem solved.

Actually, I begain to read the small print and decided to take a look at the _config_php file. Thankfully I had kept the master password so I was able to access the file. Soon I saw that the site host was listed as my previous webhost so I was able to change (in 2 places) the site host to localhost.

Although when I was leaving (saving changes) the program asked me, Are you sure you want to use such an insecure password? In my mind I thought it was because I had not filled in the password space (although the instructions said I would only need to fill out that space if I wanted to change it). so I went back and filled in the space with the same password it had before (believe me it was an overperforming awesome password) and then clicked save... it repeated the cautionary warning. I paused, then clicked it again and it said REALLY? ARE YOU SURE? (or something like that). Anyway, it did accept my descision and updated the configuration file. Then I was able to go to the admin zone and carry on business.

Problem solved. Thanks!!!

Post

Posted
Rating:
#7238
Thanks for the explanation of the password setting issue. This is a bug which will be fixed for the next release.
1 guest and 0 members have recently viewed this.