In this article you will learn:
Prevention of website migration errors
The most common sources of website migration errors that you can prevent are:
- Differences in the PHP version and missing modules
- Database transfer and its connection configuration
- Forbidden directives in .htaccess files
- Paths in the file system (open_basedir error)
PHP configuration
If your website uses PHP (common with content management systems such as WordPress, Joomla, Drupal, …), check the configuration at your current provider and before performing the migration set it on the Webhosting you want to migrate to.
The PHP version is especially important. Make sure that both the original and the new web hosting use the same PHP version.
Check and, if necessary, change the PHP version on the web hosting according to the guide Webhosting – PHP configuration.
Also check that the web hosting parameters meet the requirements of the CMS or plugins. The service plan parameters that are not listed in the customer administration can be found on the page web hosting plan comparison ⧉.
Databases
Before performing the import, verify that your website supports the database version running on the web hosting. You can find this out according to the guide Webhosting – Databases.
If you are using automatic migration, the system will try to adjust the website configuration to the new database login credentials.
After the migration itself has been completed, but before launching the website, make sure that the database is:
.htaccess files
Check the .htaccess files to make sure they do not contain forbidden directives from the list in the guide Webhosting – .htaccess file. A website with an .htaccess containing forbidden directives will display Error 500 instead of content.
Disable the forbidden directives by placing the # character on the line with such a directive, for example #Options -MultiViews.
Paths in the file system
Incorrect configuration of these paths usually leads to the open_basedir error.
With some CMSs, you may encounter addresses in the database that contain internal paths of the original web hosting. For Webhosting, such a path may look like, 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 CMS or plugin.
Common problems
Common problems with migrated websites include:
The original website is displayed
Problem: After migration, the website on the original hosting is still displayed.
Cause: The most common cause is caching of the website content in the browser, or incorrect DNS settings.
Solution: Use the keyboard shortcut Ctrl+Shift+R to load the website without browser cache.
If the problem persists, perform a DNS check:
- Find out which DNS servers the domain uses and whether changes to the IP addresses of A records (or AAAA if you use it) have propagated to the new web hosting. Propagation of DNS record changes usually takes tens of minutes to hours, while propagation of DNS server changes can take up to 48 hours.
- Check whether your hosts file contains the old web hosting IP address.
The website shows errors
Problem: The website works, but it displays errors that were not present on the original one.
Cause: Some web hosting services may have error display disabled; WEDOS web hosting has it enabled by default.
Solution: We recommend resolving the errors according to the instructions from the website creator or the support of the CMS or plugin. If the error cannot be resolved, nor can the code causing it be disabled, you can turn off error display according to the guide Webhosting – PHP configuration. However, we do not recommend this setting.
Files are not loading
Problem: Some files are not loading, Error 403 and 404 messages appear.
Solution: First make sure the files have been migrated correctly and that you are not loading them from unavailable external sources.
Especially in the case of Error 403, fix the file permissions according to the guide Webhosting – File management.
If the original website worked only over HTTP and you now have HTTPS activated, make sure the website loads all resources over this secure protocol; files with http:// addresses are blocked by a website running over https.
More information about Errors 403 and 404 can be found in the corresponding articles:
Frequently asked questions
Can you migrate and make the website work for me?
Yes, we also offer a paid transfer from a competitor ⧉.