LSCWP Error Codes

This page will explain the error codes received in the plugin in detail and any possible fixes, if available.

The installed PHP version is too old for the LiteSpeed Cache Plugin.

The LiteSpeed Cache Plugin requires at least PHP 5.3. The currently installed version is PHP <PHP_VERSION>, which is out-dated and insecure. Please upgrade or go to active plugins and deactivate the LiteSpeed Cache plugin to hide this message.

Upgrade the PHP version used. If needed, set up a new PHP version here.

Select an upgraded PHP version if possible. If not, please contact the server administrator for options.

The installed WordPress version is too old for the LiteSpeed Cache Plugin.

The LiteSpeed Cache Plugin requires at least PHP 3.3. Please upgrade or go to active plugins and deactivate the LiteSpeed Cache plugin to hide this message.

Upgrade the WordPress version used.

Something went wrong with the form! Please try again.

Refresh the page and try the purge action again.

This error indicates that something went wrong in the action submission. If refreshing does not work, please contact us.

Tried to purge list with empty list.

Purge list requires a list of entries to purge.

Bad Purge By selected value.

Somehow, an invalid Purge By type was selected. Refresh the page and try again. If that does not work, please contact us.

Failed to purge by category, invalid category slug.

Purging by category should use the category slug. Check the category list to make sure that the slug is correct. If it still does not work, please contact us.

Failed to purge by tag, invalid tag slug.

Purging by tag should use the tag slug. Check the tag list to make sure that the slug is correct. If it still does not work, please contact us.

Failed to purge by url, contained “<”.

One or more of the URLs listed contained a “<”. This is strictly forbidden. Please try listing the URLs again, making sure to avoid using this character.

Failed to purge by Post ID, given ID is not numeric: <ID>

One or more of the Post IDs listed is not numeric. Please try listing the IDs again, making sure that all IDs listed are numeric.

Failed to purge by Post ID, given ID does not exist or is not published: <ID>

One or more of the Post IDs listed does not exist or the post is not published. Please verify the ID list with the Posts list to make sure that the correct IDs are used.

Failed to purge by URL, invalid input: <URL>

One or more of the URLs listed has an invalid format. As an example, /2016/02/24/hello-world/ should be used for http://www.myexamplesite.com/2016/02/24/hello-world/.

Failed to purge by category, does not exist: <CATEGORY>

The given category slug does not exist. Check the category list to make sure that the slug is correct. If it still does not work, please contact us.

Failed to purge by tag, does not exist: <TAG>

The given tag slug does not exist. Check the tag list to make sure that the slug is correct. If it still does not work, please contact us.

Invalid data in Admin IPs.

One of the entered IPs returned as an invalid IP. Re-enter the list of IPs again. If it still does not work and they are all valid IPs, please contact us.

Invalid data in Test IPs.

One of the entered IPs returned as an invalid IP. Re-enter the list of IPs again. If it still does not work and they are all valid IPs, please contact us.

Invalid Site IP: 1.2.3.4

The IP address 1.2.3.4 (for example) is not valid. Check your site's IP address and try again.

Can not fetch Custom Sitemap: http://www.example.com/sitemapfile.xml

The sitemap file name you entered is invalid or the file is unavailable. Double-check the URL and try again. Be sure that you are entering the full URL to the file.

Can not parse custom sitemap xml file: http://www.example.com/sitemapfile.xml.

The sitemap file was fetched but cannot be read. Make sure the sitemap is in XML format and that you have installed the php-xml extension on your server.

<TTL NAME> TTL must be an integer between <MINIMUM> and 2147483647.

The <TTL NAME> TTL entered was either not an integer or did not fit within the range listed. Please try a different value.

Removed category “<CATEGORY>” from list, ID does not exist.

The input <CATEGORY> is not a valid category. It was removed from the input list.

Removed tag “<TAG>” from list, ID does not exist.

The input <TAG> is not a valid tag. It was removed from the input list.

Invalid login cookie. Invalid characters found: <LOGIN COOKIE>

The login cookie entered has invalid characters. The accepted characters are: alphanumeric characters, '_', and '-'.

Invalid Rewrite List. Empty or invalid rule. Rule: <OPTION>, list: <LIST>

The input is tested on save. If this message is displayed, that means that the input entered is not a valid one. If <LIST> is EMPTY, that means the rewrite list was empty at a point when it cannot be empty, such as when the Enable Separate Mobile Views is checked. At that point, the List of Mobile View User Agents must not be empty.

Tried to parse for existing login cookie. .htaccess file not valid. Please verify contents.

On upgrade, check to see if a login cookie was manually inserted. If the .htaccess file is corrupted in any way, this warning will output. This may indicate mismatched tags.

Could not find <CONTENT>.

Receiving this error message means that the .htaccess file was modified in an unexpected manner. This resulted in missing tags, rules, or comments that are expected to be there. The easiest way to resolve this is to:

1. Back up the .htaccess file
2. Delete the contents including and within the LSCACHE START PLUGIN/LSCACHE END PLUGIN comments.
3. In the wp-admin, change a LSCWP setting and save.
4. Revert the change if required (optional step).

This should result in the plugin adding back the missing pieces. If this produces another error or if you would like us to take a look, just contact us, we'll be happy to help.

This site is a subdirectory install. Login cookies do not match. Please remove both and set the login cookie in LiteSpeed Cache advanced settings.

On upgrade, check to see if a login cookie was manually inserted. The plugin detected that this was a subdirectory install and determined that the login cookie for the two .htaccess files did not match.

Notice: This plugin requires a LiteSpeed Server with the LSCache Module enabled. If you are unable to change your server stack, please contact your hosting provider to request the required changes. This plugin will NOT work properly.

As the error states, this plugin requires a LiteSpeed Server with the LSCache Module enabled.

If a LiteSpeed Server is already installed, it may just require switching from Apache to LiteSpeed. Note: If the license that is being used is not at least a 2-CPU license, then the LSCache Module may be not included. In this case, either upgrade the license to a 2-CPU+ license or purchase the LSCache Module addon.

As a LiteSpeed Server is required, please contact the server admin for the possibility of switching to a LiteSpeed Server.

LiteSpeed Cache was unable to write to the wp-config.php file. Please add the following to the wp-config.php file: define('WP_CACHE', true);.

Check the wp-config.php file permissions. This error indicates that we attempted to set WP_CACHE to true, but was unable to write to the file.

Failed to back up file, aborted changes.

The plugin attempted to make changes to the .htaccess file, however in its attempt to create a backup, it failed. Please check the permissions of the WordPress root and .htaccess files to make sure that the directory/files are writable. If assistance is required, feel free to contact us.

Failed to put contents into .htaccess.

The plugin attempted to make changes to the .htaccess file, however in its attempt to save the file, it failed. Please check the permissions of the WordPress root and .htaccess files to make sure that the directory/files are writable. If assistance is required, feel free to contact us.

Failed to get .htaccess file contents.

The plugin attempted to read the .htaccess file, however in its attempt to open the file, it failed. Please check the permissions of the WordPress root and .htaccess files to make sure that the directory/files are readable. If assistance is required, feel free to contact us.

.htaccess file not readable or not writable.

The plugin attempted to read or write to the .htaccess file, however in checking the file permissions, it returned either not readable or not writable. Please check the permissions of the WordPress root and .htaccess files to make sure that the directory/files are readable. If assistance is required, feel free to contact us.

.htaccess file not readable.

The plugin attempted to read the .htaccess file, however in checking the file permissions, it returned not readable. Please check the permissions of the WordPress root and .htaccess files to make sure that the directory/files are readable. If assistance is required, feel free to contact us.

.htaccess file not writable.

The plugin attempted to write to the .htaccess file, however in checking the file permissions, it returned not writable. Please check the permissions of the WordPress root and .htaccess files to make sure that the directory/files are writable. If assistance is required, feel free to contact us.

Prefix was found after suffix.

Receiving this error message means that the .htaccess file was modified in an unexpected manner. This resulted in missing tags, rules, or comments that are expected to be there. The easiest way to resolve this is to:

1. Back up the .htaccess file
2. Delete the contents including and within the LSCACHE START PLUGIN/LSCACHE END PLUGIN comments.
3. In the wp-admin, change a LSCWP setting and save.
4. Revert the change if required (optional step).

This should result in the plugin adding back the missing pieces. If this produces another error or if you would like us to take a look, just contact us, we'll be happy to help.

Failed to overwrite .htaccess.

The plugin attempted to make changes to the .htaccess file, however in its attempt to save the file, it failed. Please check the permissions of the WordPress root and .htaccess files to make sure that the directory/files are writable. If assistance is required, feel free to contact us.

The wp-config file not writeable for 'WP_CACHE'.

Check the wp-config.php file permissions. This error indicates that we attempted to set WP_CACHE to true, but was unable to write to the file. If this doesn't work, please contact us.

wp-config file did not find a place to insert define.

Please contact us, this error indicates that there is a custom wp-config.php set up. Alternatively, please add the define in the desired customized location. A suggested location is just above where $table_prefix is set.