Differences

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

--- litespeed_wiki:cache:lscwp:troubleshooting:image_optimize_error [2018/02/20 15:40]
Lisa Clarke [Image Groups Notified] Proofreading
+++ litespeed_wiki:cache:lscwp:troubleshooting:image_optimize_error [2019/07/02 15:09]
Lisa Clarke [Generic Solution] Proofreading
@@ Line 1: / Line 1: @@
 ======How to Fix Image Optimization Errors ======
 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.
+===== Generic Solution =====
+If your error message is not found below, please first try this, which should fix most issues you may encounter:
+  - Press the **Clean up Unfinished Data** button
+  - Re-send optimization request
+{{:litespeed_wiki:cache:lscwp:troubleshooting:img-opt1.png|}}
+Other things you may need to check:
+  - Security plugins may interfere in the image optimization process. Try disabling your security plugin temporarily
+  - Plugins that control page access, like maintenance mode, spam shield, additional authentications page, HTTP/HTTPS alteration, hot-link protection rewrite rule, etc. could also interfere with image optimization. If you have these, try disabling them temporarily.
 ===== Too Many Errors =====
@@ Line 10: / Line 25: @@
 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.
+If you haven't optimized your images with another plugin, please try the following:
+  - Press the **Clean up Unfinished Data** button
+  - Press the refresh icon next to **Optimization Summary** to reset your IAPI key.
+{{:litespeed_wiki:cache:lscwp:troubleshooting:lscwp-image.png?600|}}
 ===== Previous Requests in Queue =====
 ==== Error Message ====
@@ Line 60: / Line 80: @@
-''\ufeff'' is a Byte Order Mark (BOM) which causes the problem. Check wp-config.php
+''\ufeff'' is a Byte Order Mark (BOM) which causes the problem. Check wp-config.php in your WP site's root directory in the file system:
 <code>file wp-config.php</code>
@@ Line 92: / Line 112: @@
 The only solution is to destroy all optimization data and re-do it.
+===== Failed to push to LiteSpeed IAPI server =====
+==== Error Details ====
+The screen displays ''Failed to push to LiteSpeed IAPI server: "Too many errors while fetching image source files for previous request."''
+==== Solution ====
+Press the **Clean Up Unfinished Data** button, and then press the refresh icon next to **Optimization Summary**. You should now be able to send a new optimization request.
+{{:litespeed_wiki:cache:lscwp:troubleshooting:1.png|}}
+===== Error when handling your previous requests =====
+==== Error Details ====
+This error is similar as above one, and displays ''Error when handling your previous requests [Send request to reset fetch error count]''
+==== Solution ====
+Press the **Send request to reset fetch error count** button in notification bar. Then, press the **Clean Up Unfinished Data'** button, and press the refresh icon next to **Optimization Summary**. You should now be able to send a new optimization request.
+{{:litespeed_wiki:cache:lscwp:troubleshooting:1.png|}}
+===== Lot Of Images Pushed And Pulled Back Immediately  =====
+==== Error Details ====
+When you send an optimization request, it returns a success message, and then all of the images are immediately pulled without having been optimized.
+You will also see a message like ''Missing: XX groups (YY images)'' on the optimization page.
+The debug log shows the following:
+<code>07/21/18 18:07:17.125 [IP:26247 1 gmZ] [Img_Optm] bypass image due to file not exist: pid 3434 /website/wp-content/uploads/2017/09/1-768x910.jpg</code>
+This is typically due to a change in the image file path, for example in a WordPress site migration, where the file moves, but the database is not properly updated. When LSCWP uses the database to look for the images, it will not find them and will report them missing.
+==== Solution ====
+Update or repair the WordPress database.
+===== cURL error 28: Operation timed out after 15001 milliseconds with 0 bytes received  =====
+==== Error Details ====
+Firewall blocked curl communication to our image optimization servers.
+==== Solution ====
+Add our image optimization server [[https://wp.api.litespeedtech.com/ips|IPs]] to firewall white-list.