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 17:59] Lisa Clarke Replaced "folder" with "directory" |
litespeed_wiki:cache:lscwp:troubleshooting:general [2019/07/08 20:54] Jackson Zhang [A Scheduled Event has Failed] |
||
|---|---|---|---|
| Line 1: | Line 1: | ||
| ====== Troubleshooting Guide For LSCWP ====== | ====== Troubleshooting Guide For LSCWP ====== | ||
| 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 84: | Line 86: | ||
| 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 92: | Line 105: | ||
| * 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 ==== | ||