Which web servers is WP Rocket compatible with?

This article contains information about the web servers WP Rocket is compatible with, as well as the list of Apache modules and directives required for the optimization features to work properly.

In this Article

Server compatibility

WP Rocket is compatible with these web servers:

  • Apache
  • Microsoft IIS
  • LiteSpeed
  • OpenLiteSpeed

Did you know? If LiteSpeed cache is activated on your server, WP Rocket will automatically purge that cache whenever WP Rocket's is purged. (The LiteSpeed Cache WordPress plugin is not required.)

Apache modules

On Apache servers WP Rocket will look for these modules and utilize them if available:

  • mod_alias
  • mod_deflate
  • mod_expires
  • mod_filter
  • mod_headers
  • mod_mime
  • mod_rewrite
  • mod_setenvif

Apache directives

If you are getting an error: Options not allowed here when WP Rocket is enabled, it can happen if the server disallows option override for any reason. In these cases, you need to ask your hosting provider if they can allow the following directives to be overridden by our htaccess rules:

  • AddCharset
  • AddDefaultCharset
  • AddEncoding
  • AddOutputFilterByType
  • AddType
  • ExpiresActive
  • ExpiresByType
  • ExpiresDefault
  • FileETag
  • FollowSymLinks
  • Header
  • Indexes
  • RewriteBase
  • RewriteCond
  • RewriteEngine
  • RewriteRule
  • SetEnvIf
  • SetEnvIfNoCase
  • SetOutputFilter

Unsupported setups

Load balancing

WP Rocket is not designed to work with load balancing by default. Our guidance for this setup can be found here: Using WP Rocket with load balancing

Proxied domains

WP Rocket is designed to work on one domain per WordPress installation (with exceptions for supported multilingual plugins). If you are using a proxy to manipulate the domains used on your WordPress site, you will need to use this helper plugin:
Multiple configuration files for WP Rocket
But, we cannot provide further support or troubleshooting for proxy setups.

Did this answer your question? Thanks for the feedback There was a problem submitting your feedback. Please try again later.