Scope
This troubleshooting guide applies only to the following environment having this specific issue:
- Openlitespeed and Litespeed server.
- Ubuntu 22.04+
- CloudFlare is being used by the affected site
- The site has successfully been migrated.
- Your site uses the Litespeed Cache plugin.
- The site is using custom permalinks, which are non-default WordPress permalinks.
- The homepage is loading correctly.
- The other pages have a 404 error message.
Step 1: Troubleshooting the problem
Check if the problem isn’t caused by permalinks at first.
- As an administrator, log in.
- Go to Settings -> Permalinks and select Permalinks.
- Don’t change anything, just scroll down to the bottom and click “Save changes.”
- Check if the pages are still 404s. If the problem is still not fixed, move on to Step 2.
Step 2 – Pause Cloudflare implementation
- Login to your Cloudflare account.
- Click “Overview“.
- Scroll down to the bottom and find “Advanced Actions”.
- Click “Pause Cloudflare“.
- Confirm by clicking “Pause” button.
- Now login to your site and make sure you have Litespeed Cache WordPress plugin activated.
- Purge all cache in your site using LiteSpeed Cache plugin.
- Once purged – wait for around 5 to 10 minutes for the entire Cloudflare to be flushed from the system (depending on the size of your site).
- Logout and clear your browser cache.
- Check the pages affected with 404 – it should now be accessible and visible (200 OK status).
Cause of the issue
This is a conflict between Cloudflare and LiteSpeed cache plugin as mentioned by this Reddit user:
This is also confirmed in Litespeed documentation itself. This is not related to Prime Mover plugin migration or any sort of migration.
Was this article helpful?
YesNo