Scope

This troubleshooting guide applies only to the following environment having this specific issue:

  • Openlitespeed and Litespeed server.
  • Ubuntu 22.04+
  • The affected site is using Cloudflare
  • The site has successfully been migrated.
  • Your site uses the Litespeed Cache plugin.
  • The site uses 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 permalinks don’t cause the problem at first.

  • As an administrator, log in.
  • Go to Settings -> Permalinks and select Permalinks.
  • Don’t change anything; scroll 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 the “Pause” button.
  • Now login to your site and make sure you have the Litespeed Cache WordPress plugin activated.
  • Purge all caches on your site using the LiteSpeed Cache plugin.
  • Once purged, wait for 5 to 10 minutes for the entire Cloudflare to be flushed from the system (depending on the size of your site).
  • Log out 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:

How to fix cloudflare and litespeed cache clashing?
byu/Dapper_Run_2423 inWordPress

This is also confirmed in Litespeed documentation itself. This is unrelated to Prime Mover plugin migration or any migration.

Last updated: November 30, 2024

Was this article helpful?
YesNo