This article addresses common errors after moving a website from a competitor, whether manual or automatic according to the guides for migration in basic and expert mode.
In this article you will learn:
- How to prevent errors during migration
- Common problems and their solutions
- Frequently asked questions
Prevention of errors during website migration
The most common sources of errors during website migration that you can prevent are:
- Differences in PHP versions and missing modules
- Database transfer and configuration of its connection
- Forbidden commands in .htaccess files
- Paths in the file system (open_basedir error)
PHP configuration
If your website uses PHP (common for content management systems such as WordPress, Joomla, Drupal, …), check the configuration with your current provider and, before 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 webhosting use the same PHP version.
Check and, if necessary, change the PHP version on the webhosting according to the guide Webhosting – PHP Configuration.
Also check that the webhosting parameters meet the requirements of the content management system, or its plugins. Parameters determined by the service plan, which are not shown in the customer administration, can be found on the page comparison of webhosting plans ⧉.
Database
Before performing the import, verify that your website supports the database version running on the webhosting. You can find this out according to the guide Webhosting – Databases.
If you use automatic migration, the system will try to adjust the website configuration to the new database login details.
After the migration itself, 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 commands from the list in the guide Webhosting – .htaccess File. A website with .htaccess containing forbidden commands will display Error 500 instead of the content.
Disable forbidden commands by placing the # character on the 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.
In some content management systems, you may find in the database addresses that contain internal paths of the original webhosting. 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 content management system 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, check DNS:
- 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 there to the new webhosting. Propagation of DNS record changes usually takes tens of minutes to hours; propagation of DNS server changes can take up to 48 hours.
- Check whether you have the old webhosting IP address listed in the hosts file.
The website shows errors
Problem: The website works, but it shows errors that were not present on the original one.
Cause: Some webhostings may have error output disabled; WEDOS webhosting has it enabled in the default settings.
Solution: We recommend resolving errors according to the instructions of the website creator or the support of the content management system, or the plugin. If the error cannot be resolved, and neither 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.
Do you need help with the website? Find your specialist at VEDOS Profi ⧉.
Files are not loading
Problem: Some files are not loading, and Error 403 or 404 appears.
Solution: First make sure the files were migrated correctly and that you are not loading them from unavailable external sources.
Especially in the case of Error 403, fix file permissions according to the guide Webhosting – File Management.
If the original website worked only over HTTP and you now have HTTPS enabled, 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 get the website working for me?
Yes, we also offer a paid transfer from a competitor ⧉.