Differences
This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revision Next revision Both sides next revision | ||
litespeed_wiki:cache:lscwp:troubleshooting:general [2018/08/08 15:54] Lisa Clarke Added a LOT of new stuff from support team |
litespeed_wiki:cache:lscwp:troubleshooting:general [2020/05/04 13:47] Shivam Saluja |
||
---|---|---|---|
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. | ||
+ | |||
+ | Once you've looked through this guide, if you still need help, please see [[litespeed_wiki:cache:lscwp:support|our support options]]. | ||
===== Verify the Issue is Related to LSCache ===== | ===== Verify the Issue is Related to LSCache ===== | ||
Line 72: | Line 76: | ||
==== Forced Caching ==== | ==== Forced Caching ==== | ||
- | If you have a page that is always being cached, even though it shouldn't be, chances are LSCache is being forced to cache that page. | + | Sometimes, in an effort to make sure that certain pages are always cached, you erroneously force the //entire site// to be cached. Forcing this is not a good idea, because you never know when there will be individual exceptions to caching. |
- | Navigate to **LiteSpeed Cache > Settings > Excludes** and look in the **Force Cache URIs** box. Remove any string inside that box that relates to the page in question. Then, Purge All LSCache. | + | Navigate to **LiteSpeed Cache > Settings > Excludes** and look in the **Force Cache URIs** box. If you see ''/'' or ''*'' there, then you will need to remove it. Save, and then Purge All LSCache. |
==== Lazy Load ==== | ==== Lazy Load ==== | ||
Line 84: | 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 ===== | ||
Line 91: | Line 106: | ||
* Disable and then re-enable LSCache. | * Disable and then re-enable LSCache. | ||
* In the **Debug** settings tab, disable **Check Advanced Cache**. | * In the **Debug** settings tab, disable **Check Advanced Cache**. | ||
- | * Verify that the cache folder has the proper permissions (0755) | + | * Verify that the cache directory (found in ''wp-content/cache'') has the proper permissions (0755) |
+ | * Some CDNs have cache settings that can break LSCache and cause ''X-LiteSpeed-Cache: miss'' to appear at all times. However, accessing the backend server directly achieves ''X-LiteSpeed-Cache: hit''. If this happens, turn off the CDN's cache functions. | ||
==== Currency/Language Switcher Plugins ==== | ==== Currency/Language Switcher Plugins ==== |