Differences
This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revision Last revision Both sides next revision | ||
litespeed_wiki:cache:lscwp:troubleshooting:general [2018/10/31 19:08] Lisa Clarke [Cache Always Misses] Proofreading |
litespeed_wiki:cache:lscwp:troubleshooting:general [2020/05/08 19:57] Eric Leu |
||
---|---|---|---|
Line 1: | Line 1: | ||
====== Troubleshooting Guide For LSCWP ====== | ====== Troubleshooting Guide For LSCWP ====== | ||
+ | **Please Note**: This wiki is valid for v2.9.x and below of the LiteSpeed Cache Plugin for WordPress. If you are using v3.0 or above, please see [[https://docs.litespeedtech.com/lscache/lscwp/overview/|the new documentation]]. | ||
+ | |||
Here are a few common issues and how to deal with them. Please follow these steps first before logging any ticket with us since your issue might have been resolved. | Here are a few common issues and how to deal with them. Please follow these steps first before logging any ticket with us since your issue might have been resolved. | ||
Line 56: | Line 58: | ||
=== LiteSpeed Cache is disabled === | === LiteSpeed Cache is disabled === | ||
- | This is a generic error that doesn't indicate any cause. Navigate to **LiteSpeed Cache > Report** and look at the **Report Summary**. The ''Server Variables'' section right at the top can give you some helpful information. Check the values of the following variables: | + | This is a generic error that doesn't indicate any cause. Navigate to **LiteSpeed Cache > Toolbox > Report** and look at the **System Information**. The ''Server Variables'' section right at the top can give you some helpful information. Check the values of the following variables: |
* ''LSCACHE_ADV_CACHE = true'' - If this value is ''NULL'', look for the ''wp-content/advanced-cache.php'' file which should include the line ''define('LSCACHE_ADV_CACHE', true);''. If the line exists, then it may be a permissions issue. Simply fix by removing the ''advanced-cache.php'' file, and deactivating and reactivating the LiteSpeed Cache plugin. The file will be correctly regenerated. **NOTE:** Sometimes you do this, and the plugin still doesn't work. In this case, Navigate to **LiteSpeed Cache > Settings > Advanced** and disable **Check Advanced Cache**. | * ''LSCACHE_ADV_CACHE = true'' - If this value is ''NULL'', look for the ''wp-content/advanced-cache.php'' file which should include the line ''define('LSCACHE_ADV_CACHE', true);''. If the line exists, then it may be a permissions issue. Simply fix by removing the ''advanced-cache.php'' file, and deactivating and reactivating the LiteSpeed Cache plugin. The file will be correctly regenerated. **NOTE:** Sometimes you do this, and the plugin still doesn't work. In this case, Navigate to **LiteSpeed Cache > Settings > Advanced** and disable **Check Advanced Cache**. | ||
* ''LITESPEED_ON = true'' - If ''LSCACHE_ADV_CACHE = null'', then this will //always// be ''NULL''. Otherwise, if this value is ''NULL'', it means that you are not running with LiteSpeed Web Server. This is allowed, but it limits the functions that you are able to use. [[litespeed_wiki:cache:lscwp:installation|Learn more]]. | * ''LITESPEED_ON = true'' - If ''LSCACHE_ADV_CACHE = null'', then this will //always// be ''NULL''. Otherwise, if this value is ''NULL'', it means that you are not running with LiteSpeed Web Server. This is allowed, but it limits the functions that you are able to use. [[litespeed_wiki:cache:lscwp:installation|Learn more]]. | ||
Line 86: | Line 88: | ||
This problem is caused when using multiple web applications under a single domain. You can find more information on this issue and how to resolve it in our [[litespeed_wiki:cache:common:logged-in-cookie-conflicts|Handling Logged-in Cookie Conflicts page]]. | This problem is caused when using multiple web applications under a single domain. You can find more information on this issue and how to resolve it in our [[litespeed_wiki:cache:common:logged-in-cookie-conflicts|Handling Logged-in Cookie Conflicts page]]. | ||
+ | |||
+ | ==== A Scheduled Event has Failed ===== | ||
+ | |||
+ | The following notice may appear in the Health Check plugin: ''The scheduled event, litespeed_xxxx[image or ccss]_trigger, failed to run, Your site still works, but this may indicate that scheduling posts or automated updates may not work as intended'' | ||
+ | |||
+ | For example: | ||
+ | "The scheduled event, litespeed_imgoptm_trigger, failed to run." | ||
+ | |||
+ | Technically, this is not a LiteSpeed issue, but is due to WordPress itself. This usually happens when WP does a version update. It will usually clear up on its own in a day or so, once the WP-Cron is back to normal. | ||
+ | |||
+ | If you don't want to wait, you can disable WP-Cron and use a 3rd party cron like cPanel cron. | ||
===== Advanced Issues ===== | ===== Advanced Issues ===== |