Fix “Mod_Rewrite is not working” in WP Fastest Cache

Why this error shows up

mod_rewrite is an Apache feature that reads rules from .htaccess and rewrites URLs. WordPress uses it for pretty permalinks. WP Fastest Cache uses it to serve static HTML files directly from disk instead of running PHP on every request.

When you see “Mod_Rewrite is not working” in WP Fastest Cache, it means:

• The plugin wrote its rewrite rules, or tried to.
• It then tested them.
• The test failed, so the server is not applying those rules.

Most of the time, it comes down to one of these:

• You are not really on Apache or LiteSpeed, or .htaccess is ignored on your plan.
• Apache’s mod_rewrite module is not enabled.
• .htaccess exists but Apache is not allowed to obey it (AllowOverride None).
• The WP Fastest Cache block is missing, in the wrong place, or conflicts with other rules.
• .htaccess is not writable, so the plugin never saved its rules correctly.

Step 1: Check that rewriting works at all

Before touching the plugin, make sure your server can handle basic URL rewriting.

1.1 Test pretty permalinks

1. In WordPress, go to Settings → Permalinks.
2. Select Post name (or any option that is not “Plain”).
3. Click Save Changes.
4. Visit a few posts and pages on the front end.

Now check what happens:

• If pretty permalinks work (no 404 errors): basic rewriting is working. The problem is more specific to .htaccess or the plugin’s rules. Go to Step 2.
• If pretty permalinks break and only “Plain” works: your server is not applying rewrite rules at all. In this case, WP Fastest Cache cannot use mod_rewrite until the server is fixed. Skip to Step 4 and talk to your host.

1.2 Confirm what server you are on

WP Fastest Cache’s mod_rewrite mode is designed for Apache and LiteSpeed. Nginx does not read .htaccess at all.

If you are not sure what you are running:

• Check your hosting control panel or welcome email for “Apache”, “LiteSpeed”, or “Nginx only”.
• Or ask your host: “Is my site served by Apache or LiteSpeed with .htaccess support, or Nginx only?”

If you are on Nginx only: the plugin cannot apply mod_rewrite rules by itself. You will either need host level rules or a different cache method. Keep that in mind when you reach Step 5.

Step 2: Make sure .htaccess exists and is writable

WP Fastest Cache stores its rewrite rules in the same .htaccess file WordPress uses for permalinks.

2.1 Find .htaccess in your site root

1. Open your hosting File Manager or connect with FTP/SFTP.
2. Go to the folder that contains wp-config.php. This is your WordPress root.
3. Look for a file named .htaccess.

If you do not see it, enable “show hidden files” in your file manager. If it still does not exist:

1. Go back to Settings → Permalinks in WordPress.
2. Click Save Changes once. WordPress will try to create a fresh .htaccess with its default rules.

2.2 Fix .htaccess permissions

WP Fastest Cache needs to be able to update this file.

• In your file manager, right click .htaccess.
• Set its permission to 644 (or “owner writable, group and public readable”).
• Click save or apply.

If permissions are too strict (for example 444), the plugin cannot add or update its rules and you will keep seeing the error.

Step 3: Let WP Fastest Cache rewrite its rules

Now that .htaccess is in place and writable, let the plugin try again.

3.1 Save WP Fastest Cache settings again

1. In WordPress, go to WP Fastest Cache → Settings.
2. Make sure Cache System is checked.
3. Click Submit or Save at the bottom.
4. Click Delete Cache to clear any existing files.

After saving, refresh the settings page. If the “Mod_Rewrite is not working” notice disappears, you are done with the core issue. Skip to Verification.

3.2 Check that the plugin rules are actually in .htaccess

If the notice is still there, open .htaccess again in a text editor.

• Look for a block that mentions WP Fastest Cache in comments, and paths like /wp-content/cache/all/.
• It should appear after the main WordPress permalink block in most setups.

If there is no WP Fastest Cache block at all, the plugin still cannot write to .htaccess. In that case:

• Double check permissions on .htaccess and the site root folder.
• Disable any security plugin setting that blocks .htaccess edits.
• Try saving WP Fastest Cache settings once more.

Step 4: When the rules are there but mod_rewrite still fails

At this point you may have:

• A valid .htaccess file.
• WP Fastest Cache rules present.
• Pretty permalinks working.
• But the plugin still says “Mod_Rewrite is not working”.

This usually means Apache is not applying those rules, even though basic rewriting works.

4.1 Check for rule order and conflicts

Some other plugin or the host may have placed rules above the WP Fastest Cache block that “catch” requests first.

In .htaccess look for:

• Other cache plugin blocks (WP Super Cache, W3 Total Cache, WP Rocket, etc).
• Security or firewall rules.
• Redirect rules that run before the cache block.

If you see multiple cache plugins writing rules, pick one caching plugin to keep, disable the others, then clean up their blocks in .htaccess. After that, resave WP Fastest Cache settings.

4.2 Ask your host to confirm Apache settings

If you are comfortable editing server config you can do this yourself, but on most shared hosting you will need support to check it.

Open a ticket with wording like this:

“I am using the WordPress plugin WP Fastest Cache, which relies on Apache’s mod_rewrite rules in my site’s .htaccess file. WordPress permalinks work, but the plugin reports ‘Mod_Rewrite is not working’. Can you confirm:

• That mod_rewrite is enabled for my virtual host, and
• That AllowOverride All (or at least AllowOverride FileInfo Options) is set so .htaccess rewrite rules can run, and
• That no server level rule is stripping or overriding the WP Fastest Cache rules?”

If your host says mod_rewrite is disabled or .htaccess overrides are blocked for your plan, WP Fastest Cache cannot use its fastest method on that server. You will need their help to change that, or to use a different cache strategy.

Step 5: If you are on Nginx, OpenLiteSpeed, or locked down hosting

Some environments do not use Apache style .htaccess at all, or only read it after extra configuration.

• Nginx only: all rewrite rules live in the main Nginx config. mod_rewrite is not available.
• OpenLiteSpeed: may not reload .htaccess automatically until the service is restarted.
• Managed hosting: some providers disable custom .htaccess rules for security reasons.

In these cases:

• Ask your host if they officially support WP Fastest Cache’s mod_rewrite mode on your plan.
• If they do, ask them to place the plugin’s rewrite rules into the server config and reload the service.
• If they do not, follow their cache recommendation instead, or use a plugin they support for your stack.

If you cannot tell where it is failing

If you are still staring at “Mod_Rewrite is not working” after the checks above, I will need a bit more context to help you narrow it down.

Scroll down, click Continue Chat, and send me:

1. Your hosting provider and plan (shared, VPS, managed WordPress, etc).
2. Whether pretty permalinks work when “Post name” is selected.
3. Whether your site runs on Apache, LiteSpeed, or Nginx (your host can confirm).
4. The contents of your current .htaccess file from the WordPress root.
5. A screenshot or copy of the WP Fastest Cache settings page.

Verification: how to know it is fixed

You are in good shape if:

• The “Mod_Rewrite is not working” message no longer appears in WP Fastest Cache.
• Your site loads fine with pretty permalinks enabled.
• You see WP Fastest Cache HTML comments in your page source on cached pages (unless you have disabled those comments).
• The folder /wp-content/cache/all/ fills up with cached HTML files after a few visits.
• Page load times improve for logged out visitors and speed tests report more cache hits.

Still stuck?

For AI help

Hit Continue Chat below and I will walk you through your .htaccess, server type, and plugin settings until we find the exact reason mod_rewrite is failing.

For expert human help

Scroll down to the contact form below. Enter your name, email, and WordPress needs. Atiba will get back to you as soon as possible.