This article covers common errors after moving a website from a competitor, whether manually, or automatically using the guides for migration in basic and expert mode.
In this article, you will learn:
Preventing website migration errors
The most common preventable causes of website migration errors are:
- Different PHP versions and missing modules
- Database migration and connection configuration
- Prohibited directives in .htaccess files
- File system paths (open_basedir error)
PHP configuration
If your website uses PHP (common with WordPress, Joomla, Drupal, etc.), check the configuration at your current provider and configure the destination Webhosting accordingly before migration.
The PHP version is especially important. Make sure the original and new Webhosting use the same PHP version.
Check and, if necessary, change the Webhosting PHP version using the guide Webhosting – PHP Configuration.
Also check that Webhosting parameters meet the requirements of your CMS and any plugins. Parameters determined by the service plan but not listed in Customer Administration are available on the Webhosting plan comparison ⧉.
Databases
Before importing, check that your website supports the database version running on Webhosting. Find it using the guide Webhosting – Databases.
If you use automatic migration, the system attempts to update website configuration with the new database login details.
After migration but before launching the website, make sure the database is:
- successfully imported and
- connected to the website through the configuration file.
.htaccess files
Check .htaccess files for prohibited directives listed in the guide Webhosting – The .htaccess File. A website whose .htaccess contains prohibited directives displays Error 500.
Disable prohibited directives by placing the character # on the line containing the directive, for example #Options -MultiViews.
File system paths
Incorrect paths usually cause the error open_basedir.
In some content management systems, database entries may contain internal paths from the original Webhosting. A Webhosting path might look like /data/web/virtuals/123456/virtual/www/domains/wds-test.cz.
Update these paths or handle them according to your CMS or plugin instructions.
Common issues
Common migrated website problems include:
The original website appears
Problem: After migration, the website on the original hosting is still displayed.
Cause: The most common cause is website content cached in the browser or incorrect DNS configuration.
Solution: Use the keyboard shortcut Ctrl+Shift+R to load the website without the browser cache.
If the problem persists, check DNS:
- Find out which DNS servers the domain uses and whether changes to the IP addresses in A records (or AAAA records, if used) have propagated to point to the new Webhosting. DNS record changes usually take tens of minutes to hours; DNS server changes may take up to 48 hours.
- Check that your hosts file does not contain the old Webhosting IP address.
The website displays errors
Problem: The website works but displays errors not shown on the original hosting.
Cause: Some Webhosting services disable error display; WEDOS Webhosting enables it by default.
Solution: We recommend resolving errors according to the website developer’s or CMS/plugin support instructions. If you cannot resolve the error or disable the code causing it, turn off error display using the guide Webhosting – PHP Configuration. However, we do not recommend this setting.
Need help with your website? Find your specialist on VEDOS Profi ⧉.
Files do not load
Problem: Some files do not load; Errors 403 and 404 appear.
Solution: First, make sure files were migrated correctly and are not being loaded from unavailable external sources.
Especially for Error 403, repair file permissions using the guide Webhosting – File Management.
If the original website used only HTTP and you now have HTTPS enabled, make sure all resources load over this secure protocol. A website running over https blocks files with http:// addresses.
For more information about Errors 403 and 404, see the corresponding articles:
Frequently asked questions
Can you migrate the website and get it running for me?
Yes, we also offer a paid migration service from competitors ⧉.