After migrating your website, you may encounter issues affecting its functionality. This article provides a detailed troubleshooting guide to help resolve common post-migration problems.
Step 1: Purge Cache Using Cache Manager
Caching can sometimes cause issues when migrating a website. If your site is still showing old content or experiencing slow performance, it might be related to cache.
At Hostinger, you have a Cache Manager that supports all frameworks (HTML, WordPress, Laravel, etc.) and eliminates the need to manage the cache on a different platform. However, this feature is not supported with Hostinger Website Builder.
To enable it, go to Websites → Dashboard, and search for Cache Manager:
Next, click on the Automatic cache toggle. Once activated, Cache Manager will store your website's static content, updating it every 30 minutes to ensure the latest version is visible.
If you want to display a recent change, you can also manually purge the cache for your whole website or just a specific URL:
If you still see outdated content after purging the cache, make sure to clear your local cache as well.
If you are using LiteSpeed Cache on WordPress:
Go to Websites → Dashboard, and search for WordPress -> Overview. There, you will find an option to Flush the Cache
Alternatively, if you are using another caching plugin or a different type of caching mechanism, ensure that you clear the cache properly. This will help eliminate any stored data that might be causing the issue.
Step 2: Try Changing PHP Version
The version of PHP running on your server can affect how your site behaves, especially after migration. Some older versions of PHP may be incompatible with your new server environment or website setup.
Change PHP Version:
Most WordPress websites recommend using PHP 7.4 or under PHP 8.0.
If you are running an older WordPress version (e.g., 6.1.x, 5.x.x, or 4.x.x), you may need to switch to an earlier version of PHP, such as:
PHP 7.2
PHP 7.0
PHP 5.6
To change the PHP version of your hosting plan, go to the Websites section and click on Dashboard next to the website in question. Then, search for PHP Configuration on the sidebar and click on the given result to access those settings:
On the PHP Configuration page, select the PHP version you wish to use and click on Update:
The PHP version will be updated within a couple of minutes.
After switching, check if your website functions correctly.
Step 3: Fix File Permissions
Incorrect file permissions can prevent the server from reading or writing necessary files. This can cause issues such as broken images, missing content, or the inability to upload files.
To quickly fix all your file permissions, go to Websites → Dashboard, search for Fix File Ownership on the sidebar and click on it:
Next, mark the checkbox to confirm that you want to set the files and folders to default permissions and click on Execute:
After making the changes, check if the issue persists.
Step 4: Replace .htaccess with Default
The .htaccess file is a configuration file used by Apache servers to handle important server-side settings. If this file has been altered during migration, it may cause errors.
To replace .htaccess:
To replace an .htaccess file from your panel, go to Websites → Manage, search for File Manager on the sidebar and click on it:
Navigate to the public_html folder.
Locate the .htaccess file.
Rename the current .htaccess file to something like .htaccess_old (as a backup).
Create a new .htaccess file with the default WordPress rules:
# BEGIN WordPress<IfModule mod_rewrite.c>
RewriteEngine On
RewriteBase /
RewriteRule ^index\.php$ - [L]
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteRule . /index.php [L]
</IfModule>
# END WordPress
Save and upload the new file to your server.
Visit your website again to see if the issue is resolved.
Step 5: If you notice that the current content does not match the old website
If your website's current view does not match the expected one, please create a new migration request by uploading different backups: How to migrate the website?
Step 6: Further Troubleshooting
If the above steps do not resolve the issue, it may depend on the specific error message you are encountering. We recommend checking other relevant articles in our knowledge base which address common issues:
If the issue persists, please contact our support team for further assistance.