We're now moving hosting accounts to the new hosting servers and in relation to this I'd like to outline how you can deal with database-driven sites and user generated content during the move.
Hosting accounts are moving from 22.214.171.124 to 126.96.36.199.
It will take some time for all computers around the world to be aware of this change, sometimes up to 24 hours. This is not something we can control.
For a day or so after the move, visitors to your websites may end up reaching either the old hosting server or the new hosting server.
If you deal with frequent user generated content, such as discussion forums or blog comments, you may find content to be inconsistent. If user A reaches the old hosting servers and makes a blog comment and user B reaches the new hosting servers and makes a blog comment, each comment will be stored in a different place, neither will be visible to all users and over time the comment from user A will be lost.
Ensuring All Of Your Content Ends Up In The Same Database
For a couple of days after your hosting accounts have been moved, we cannot control whether it is the old hosting servers or the new hosting servers that are reached by visitors to your websites.
It is possible, however, to control into which database such user generated content is stored.
You can change the database configuration for your websites on the old hosting servers so as to use the correct database on the new hosting servers.
How you do this depends entirely on the web applications you are running. We can't tell you where to make this change, but we can tell you what to change and how you can go about doing that.
Applying Database Configuration Changes On The Old Hosting Servers
Note: this only applies after your hosting accounts have been moved. We will send you an email directly once your hosting accounts have been moved.
To apply database configuration changes for a given hosting account:
Establish a FTP connection to 188.8.131.52, using the relevant hosting account username and password.
Navigate to your database configuration settings file. What this is called and where is located depends entirely on the web application you are running. If you're not sure, Google is your friend.
Change the database host from the current setting (most likely 'localhost') to 184.108.40.206.
Save and upload your changes.
Verifying That Remote MySQL Connections Are Allowed
The above changes will ensure that your web applications running on the old hosting servers will use the relevant database on the new hosting servers.
We have configured the MySQL server on the new hosting servers to allow remote connections from the old hosting servers.
This may not work as expected if you have ever set up additional MySQL access hosts.
To verify your current MySQL access hosts settings:
Log in to cPanel on the new hosting servers. The cPanel address will have changed. Log in to your Hosting Reborn account to determine the correct cPanel address.
Navigate to the additional MySQL access hosts section. Refer to the relevant cPanel documentation if you are not sure where this is and what it does.
Check that 220.127.116.11 is listed as an allowed host. Add this if missing.