Don't touch WP-Config!
Migrate to GoDaddy Managed WordPress Manually
Don't touch WP-Config!

Don’t touch WP-Config!

Wanna waste about 2 hours like I did trying to accomplish what’s supposed to be maybe a 30-minute job? Then by all means, replace the wp-config.php file that GoDaddy creates when a user signs up for their Managed WordPress Hosting account!

Not having migrated too many WordPress websites manually, I spent some time reading up on how to do so before pulling the trigger and beginning the process. The consensus across the internet (roughly), seemed to be:

1. Back up all existing WordPress files
2. Back up existing database
3. Edit the database file if the URL will be different from the original
4. Drop the entire GoDaddy database via PhpMyAdmin
5. Upload your old database to GoDaddy’s
6. Upload the old wp-content folder to GoDaddy, replacing the current one
7. Replace/update your wp-config.php file with your new GoDaddy database credentials

See how number 7 above is struck-through and in red? DON’T DO IT! It took me forever to randomly stumble across this article (only after entering the correct Google search terms… this article definitely didn’t show up via searching through GoDaddy’s articles on their own site): https://my.godaddy.com/help/move-your-wordpress-site-manually-12371.

The issue was with the database host name. Instead of the typical ‘localhost’, or even the IP address of your new site, GoDaddy uses a special, unique hostname. The one that worked for me was ‘test3290301462.db.3290301.hostedresource.com:3310’, as in:

/** MySQL hostname */
define('DB_HOST', 'test3290301462.db.3290301.hostedresource.com:3310');

As far as I can tell, this information isn’t listed ANYWHERE within your GoDaddy account, so, whatever you do, don’t touch the GoDaddy-generated wp-config.php file for your managed WordPress account.

0 replies

Leave a Reply

Want to join the discussion?
Feel free to contribute!

Leave a Reply

Your email address will not be published. Required fields are marked *