Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
Next revision Both sides next revision
litespeed_wiki:cache:lscwp:troubleshooting:general [2018/08/14 20:33]
Lisa Clarke [Troubleshooting Guide For LSCWP] Added link to Premium Support
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. ​
  
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 =====
Line 94: Line 107:
   * In the **Debug** settings tab, disable **Check Advanced Cache**.   * In the **Debug** settings tab, disable **Check Advanced Cache**.
   * Verify that the cache directory (found in ''​wp-content/​cache''​) 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 ====
  • Admin
  • Last modified: 2020/11/14 15:43
  • by Lisa Clarke