Upgrade Can Not Connect to Database
News and General
Hello,
I am running MySQL Server version: 5.5.50-cll and PHP 5.4.37 and trying to upgrade an EE install version 2.11.3 to 3.4.2. I am following the steps outlined here:
https://docs.expressionengine.com/latest/installation/upgrade_from_2.x.html
I have uploaded my database.php and config.php from my 2.11.3 install into the new system/user/config/ folder, but when I go to http://<domain>/admin.php, I get the following error during pre-flight checks:
Unable to connect to your database using the configuration settings found in the following file: config/config.php file. Please correct the settings so that the update can proceed.
Technically there are no database settings in config.php because in 2.11.3, they were stored in database.php. Any advice would be appreciated.
Thank you.
Hey gtruta! Sorry you’re having difficulties. Let’s first make sure that this environment can run ExpressionEngine 3. Please download the server wizard and follow those instructions to see if a more specific problem is revealed.
Thanks Derek,
I have run the Server Compatibility Wizard, and all checks pass.
Is the server you are performing the upgrade / trying to install v3 the same as the one currently running v2? Or are you doing this in different environments?
Yes, there is only one server involved.
I’ve never seen the wizard work and connect to the DB while the installer does not; the connection method is the same. Are you sure you’re inputting identical server, db name, user, and password for the database? If so, you may need to put in a support ticket so one of our engineers can debug your environment.
Good catch! There were two databases on the server. I was using the connection details for one database to do the integrity check, but not the one the upgrade was running on. When I ran it on the upgrade database, it could not connect. I reset the password for the user to what it was in database.php and the upgrade proceeded as expected.
Not sure why/how the password would stop working, but if it helps anyone else that’s what solved the issue.
Glad you sorted it out!