This article addresses common mistakes after moving a site from a competitor, whether manual or automatic, by following the basic and expert mode migration guides.
In this article you will learn:
Preventing errors during site migration
The most common sources of preventable site migration errors are:
- PHP version differences and missing modules
- Moving a database and configuring its connection
- Disabled commands in .htaccess files
- File system paths (open_basedir error)
PHP Configuration
If your website uses PHP (common with WordPress, Joomla, Drupal, ...), check the configuration with your current provider and set it up on the Webhost you want to migrate to before performing the migration.
In particular, the PHP version is key. Make sure that the original and new web hosts use the same version of PHP.
Verify the PHP version on the webhost and change it if necessary according to the Webhosting - PHP Configuration instructions.
Next, check that the web hosting parameters match the requirements of the editorial system or plugins. Parameters given by the service tariff, which are not specified by the customer administration, can be found on the web hosting tariff comparison page ⧉.
Database
Before performing the import, verify that your website supports the version of the database hosted on the web host. You can find out by following the instructions Webhosting - Database.
If you use automatic migration, the system attempts to adjust the site configuration to the new database credentials.
After performing the actual migration, but before launching the site, make sure the database is:
- successfully imported and
- using a configuration file attached to the site.
.htaccess files
Check your .htaccess files for the prohibited commands listed in the Web Hosting - .htaccess file instructions. A site with a .htaccess file containing prohibited commands will display Error 500 instead of the content.
Exclude prohibited commands by placing a character # to a line with such a command, for example #Options -MultiViews.
Paths in the file system
Incorrect setting of these paths usually leads to an open_basedir error.
For some content management systems, you may encounter addresses in the database that contain the internal paths of the original web host. For Webhosting, such a path may take the form of, for example /data/web/virtuals/123456/virtual/www/domains/wds-test.cz.
Update these paths to the correct ones, or handle them according to the instructions of the editorial system or plugin.
Common problems
Common problems with migrated sites include:
The original site is displayed
Problem: After the migration, the website is still displayed on the original hosting.
Cause: The most common cause is caching of web content in the browser or incorrect DNS settings.
Solution: use the Ctrl+Shift+R keyboard shortcut to load the website without the browser cache.
If the problem persists, perform a DNS check:
- Find out which DNS servers the domain is using, and whether there are any changes to the IP addresses of Type A (or AAAA, if you are using it) records on those servers to the new web host. DNS record changes typically take tens of minutes to hours to propagate, and DNS server changes can take up to 48 hours to propagate.
- Make sure you do not have an old IP address of the web host in your hosts file.
The website lists errors
Problem: The website works, but shows errors that were not present on the original website.
Cause: Some web hosts may have error reporting disabled, WEDOS web hosting has reporting enabled by default.
Solution: We recommend that you resolve errors according to the instructions of the site creator or the support of the editorial system or plugin. If you cannot resolve the error or disable the code that is causing it, you can disable the error display by following the instructions in Webhosting - PHP Configuration. However, this setting is not recommended.
Files not loading
Problem: Some files do not load, Errors 403, 404 appear.
Solution: First, make sure the files are properly migrated and not loaded from unavailable external sources.
Especially in the case of Error 403, correct the file rights according to the Webhosting - File Management instructions.
If the original site was running only over HTTP and you now have HTTPS enabled, make sure the site is loading all resources over this secure protocol, files with http:// addresses are blocked by the site running over https.
For more information on Errors 403 and 404, see the corresponding articles:
Frequently Asked Questions
Can you migrate the site and make it work for me?
Yes, we also offer a paid transfer service from a competitor ⧉.