Differences
This shows you the differences between two versions of the page.
| Next revision | Previous revision Next revision Both sides next revision | ||
|
litespeed_wiki:cache:litemage:troubleshooting:installation-litemage-not-enabled-no-cache-hit-header [2017/05/02 18:05] Jackson Zhang created |
litespeed_wiki:cache:litemage:troubleshooting:installation-litemage-not-enabled-no-cache-hit-header [2017/05/03 14:37] (current) Michael Alegre [Solution] |
||
|---|---|---|---|
| Line 1: | Line 1: | ||
| - | ===== Why I can not see “X-LiteSpeed-Cache: hit,litemage” header? ===== | + | ~~NOTOC~~ |
| - | I believe I followed [[litespeed_wiki:cache:litemage:installation|this wiki]]to install LiteMage for Magento 1, however, I still can not see “X-LiteSpeed-Cache: hit,litemage” header? Why? | + | |
| - | There could be due to various reasons. It could be some important steps which might have been missed. It is worthy to check the following again: | + | ====== “X-LiteSpeed-Cache: hit,litemage” Header Not Appearing (Magento 1.x) ====== |
| - | * Do you have LiteMage enabled for your license? For 1-CPU and lower licenses, you will need to purchase litemage as an add-on, while LiteMage starter license has been included in 2-CPU and above license automatically. If you just recently upgraded your license by adding LiteMage, you will need to register a new license key through **bin/lshttpd -r** and restart LSWS. | + | ==== Symptoms ==== |
| - | * Have you placed "LiteMage On" in .htaccess? | + | * ''X-LiteSpeed-Cache: hit,litemage'' header is missing (LiteMage is not working properly) |
| - | * If you power your Magento store on a shared hosting service account, please contact your hosting company to ensure they enable LiteMage feature for your account. | + | |
| - | * Have you/or your host set server level and virtual host level of cache root and cache policy? | + | ==== Cause ==== |
| - | * In “LiteMage Configuration” within Magento admin, has "Enable LiteMage Cache" been set to “Yes”? | + | There can be various causes for this problem, but most likely a step was missed in the **[[litespeed_wiki:cache:litemage:installation|LiteMage 1.x Installation Guide]]**. |
| - | * Has other full page cache been disabled? | + | |
| - | * Has the "Enable LiteMage Cache Only for Listed IPs" been set while your IP is not in that list? | + | ==== Solution === |
| - | * For LiteMage to work correctly, you must have both “Configuration” and “Layouts” enabled under System → Cache Management. If you are using Magento Enterprise, you must also disable “Page Cache”. | + | Please double check the following: |
| - | * Did you try “Flush Cache Storage”? | + | |
| - | * Navigate to the app/ directory from ssh command line and execute the following command to see if layout/default.xml contains cacheable=“false”. | + | * Do you have LiteMage enabled for your license? For 1-CPU and lower licenses, you will need to purchase LiteMage as an add-on, while LiteMage starter is included in all 2-CPU and above license. If you just recently upgraded your license by adding LiteMage, you will need to register a new license key with command ''.../lsws/bin/lshttpd -r'' and restart LSWS. |
| - | <code>grep -r cacheable * | grep xml | grep false</code> | + | * Have you placed "LiteMage On" in your stores .htaccess file? |
| + | * If you host your Magento store on a shared hosting service account, please contact your hosting company to ensure that they have enabled LiteMage for your account. | ||
| + | * Have you or your host set the server & virtual host level cache root and cache policy? | ||
| + | * Has "Enable LiteMage Cache" been set to “Yes” under “LiteMage Configuration” in the Magento admin? | ||
| + | * Have other full page caches been disabled? | ||
| + | * Has "Enable LiteMage Cache Only for Listed IPs" been set and your IP is not listed? | ||
| + | * For LiteMage to work correctly, you must have both “Configuration” and “Layouts” enabled under **System → Cache Management**. If you are using Magento Enterprise, you must also disable “Page Cache”. | ||
| + | * Did you try flushing LiteMage Cache and Magento Cache Storage? | ||