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
litespeed_wiki:cache:lscwp:troubleshooting:image_optimize_error [2018/02/19 23:28]
qtwrk 		litespeed_wiki:cache:lscwp:troubleshooting:image_optimize_error [2020/11/16 21:26] (current)
Lisa Clarke Redirect to new Documentation Site
Line 1: Line 1:
-======How to Fix Image Optimization Errors ====== +~~REDIRECT>https://docs.litespeedtech.com/lscache/lscwp/ts-media/~~
-There are a number of different warning/​error messages you may see after you've sent an image optimization request. This is your guide to those messages. +
- +
-===== Too Many Errors ===== +
-==== Error Message ==== +
-<code> +
-Too many errors when try to fetch image source files from your previous request, please check if you have any other optimization plugin. +
-</​code>​ +
-==== Solution ==== +
-Have you already optimized your images with another plugin? This can cause a conflict. Please restore the images to their original sizes and try requesting LiteSpeed optimization again. +
- +
-===== Previous Requests in Queue ===== +
-==== Error Message ==== +
-<​code>​ +
-Previous optimization requests remaining in queue: xxx +
-</code> +
-==== Solution ==== +
-All good things are worth waiting for... The previously-requested images are still waiting to be processed. Please give the process 24 hours to complete. +
- +
-===== Previous Requests Processing ===== +
-==== Error Message ==== +
-<​code>​ +
-Previous requests in optimizing process: xxx +
-</code> +
-==== Solution ==== +
-Your images are currently being processed. Please give the process 24 hours to complete. +
- +
-===== Too Many Notification Errors ===== +
-==== Error Message ==== +
-<​code>​ +
-Too many errors when try to notify your server for your previous request, please check your firewall settings. +
-</code> +
-==== Solution ==== +
-We've tried to contact you, but are having difficulty. Chances are your firewall is blocking us. Verify that it is set up to allow http/https protocols, both inbound and outbound. +
- +
-===== Previous Requests Not Pulled ===== +
-==== Error Message ==== +
-<​code>​ +
-Previous requests that optimized but not pulled: xxx  +
-</​code>​ +
-==== Solution ==== +
-Your images are finished being processed, but they have not been pulled back to your site. Please run your ''​wp-cron.php''​ or other WordPress cron job to pull all your finished images from the LiteSpeed Image server. +
- +
-===== Too Many Pull Errors ===== +
-==== Error Message: ====  +
-<​code>​ +
-Too many errors when pull optimized images from image optimization server. +
-</​code>​ +
-==== Solution ==== +
-Click the link in the message to reset it. +
- +
-===== Hash Does Not Match / No Auth Key ===== +
-==== Error Message: ==== +
-    +
-<​code>​IAPI Error "hash does not match: ClientCB[\ufeffHMAVDipkPeetCbz1] Server[HMAVDipkPeetCbz1]"​ +
-Failed to communicate with LiteSpeed IAPI server: "no auth_key"</​code>​ +
- +
-{{ :​litespeed_wiki:​cache:​lscwp:​configuration:​cache:​iapi-no-auth.jpg?​direct |}} +
-==== Solution ==== +
- +
- +
-''​\ufeff''​ is a Byte Order Mark (BOM) which causes the problem. Check wp-config.php +
- +
-<​code>​file wp-config.php<​/code>  +
- +
-The following result is returned: +
- +
-{{ :​litespeed_wiki:​cache:​lscwp:​configuration:​cache:​iapi-no-auth2.jpg?​direct |}} +
- +
-Removing BOM in /wp-config.php will fix this problem. Run this command: +
- +
-<​code>​sed -i $'​1s/​^\uFEFF//'​ wp-config.php</​code>​ +
-   +
-Check again afterwards:​ +
- +
-{{ :​litespeed_wiki:​cache:​lscwp:​configuration:​cache:​iapi-no-auth3.jpg?​direct |}} +
-   +
-Now the **Update Reduction Status** button should work fine. +
- +
- +
-===== Image groups notified to pull: X ; but pull never worked ===== +
-==== Error Details ==== +
-Image groups notified to pull: X , but never be able to pull the images , cron job start for few minutes and notified image groups number still remains same. +
- +
-Check debug.log with pull action shows: +
- +
-<​code>​IAPI failed to decode post json: "​missed data"​ +
-Media: Failed to pull optimized img: --- '"​missed data"'</​code>​ +
- +
-==== Solustions ==== +
-Image optimization server keeps optimized images for 20 days ,and images will be removed if not be pulled in 20 days, but client side is not aware of it so it keeps try to pull images that not longer exists in server. +
- +
-Destory all optimization data and re-do it. +
  • Admin
  • Last modified: 2018/02/19 23:28
  • by qtwrk