• Resolved mazze5

    (@mazze5)


    Hi,

    I am using LiteSpeedCache the first time. Version v3.0.8.5 and since yesterday 3.0.8.6.

    From Request to Pull it seems to be really slow. But maybe thats normal?

    I could optimized a few images(11), but now I get the following error in wordpress:
    Images failed to fetch

    And on quic.cloud I see something like that:

    Error: Fetched md5 mismatch: [latest] d41d8cd98f00b204e9800998ecf8427e [ori] d26bb563a3fa5e186385b66d02cdd24f
    https://....jpg
    	04.05.2020, 13:58

    If I clean up unfinished data und restart request. Then sometimes some optimizations work and then the same error again.

    The status in wordpress and my.quic.cloud do not match.
    WP says 94 images requested and my.quic.cloud RequestsStatus show only 0?
    my.quic
    wordpress-image-opt

    Its unpossible to optimize all images this way…. and if I clean up unfinished, then the counter

    Can someone help with this problem?

    Last Request: 44m 50s ago and nothing seems to happen

    • This topic was modified 4 years, 6 months ago by mazze5.
    • This topic was modified 4 years, 6 months ago by mazze5.
Viewing 8 replies - 1 through 8 (of 8 total)
  • Thread Starter mazze5

    (@mazze5)

    I hav purged and uninstalled v3.0.8.6 and installed v2.9.9.2. This version works without problems. My pictures were all optimized in 8 minutes.

    It seems to be a problem with the new v3 version.

    Plugin Support qtwrk

    (@qtwrk)

    Hi,

    Do you have any kind of security plugin or access-control plugin ? that’s a typical reason for such error.

    Best regards,

    Thread Starter mazze5

    (@mazze5)

    Hi,

    no, I have not such a plugin. The only pluign for security is at the moment “WPS Hide Login”, but I think that shouldn’t the problem.
    I have tested it with I clean WP installation without any plugin and had the same problems. So plugins shouldn’t be the problem at all, I think.

    I am wondering as I said in my last comment, because with the older version v2.9 it works. I could yesterday optimize all of my 2500 images, without any error.

    Maybe I make a backup and then upgrade the litespeed-plugin to v3 and test it again.

    Plugin Support qtwrk

    (@qtwrk)

    Hi,

    Yes

    d41d8cd98f00b204e9800998ecf8427e

    this is md5sum for empty string , that means , something stopped image server from fetching images from your site.

    Maybe firewall of some sort.

    Please make sure our image server IPs are whitelisted.

    Best regards,

    Thread Starter mazze5

    (@mazze5)

    Hi,

    yes I have read this. So the frist thing was to ask my hosting provider about this. And they told me, that no IPs are blocked.

    So I have to trust this answer…

    Plugin Support qtwrk

    (@qtwrk)

    Hi,

    You said you tried on a clean WP without any plugin and still hit this issue, could you please try again , and see you can still reproduce it ?

    Also , please ask your provider to check mod_security rule , see if it hits some false-positive alert.

    Best regards,

    Thread Starter mazze5

    (@mazze5)

    Hi,

    ok I will ask my provider. I have tried this morning again, fresh WP Install 5.4.1 with no Plugin, latest Version of LiteSpeed-Cache installed.
    First 6 images worked, But then request with 93 images, it starts “Images failed to fetch”

    Maybe it only happens when more images are requested…

    Error on quic:

    07.05.2020, 11:08
    Error: Fetched md5 mismatch: [latest] d41d8cd98f00b204e9800998ecf8427e [ori] 863b9a7de59d343fdc8e4adde4df4ad6
    https://dabbnei.de/wp-content/uploads/2020/05/lebensmittelpreise-3-768x768.jpg
    

    But after that the next 15 images were pulled without erros.

    • This reply was modified 4 years, 6 months ago by mazze5.
    Thread Starter mazze5

    (@mazze5)

    But 2 hours ago the last request was started, after the fetch error a few images of the request were optimized and pulled. But after that nothing happend. In the request are still 79 not finished images and after 1 hour of waiting nothing happen. Still 79 images…

    Afer a clean up and new request it worked.

    I close this issue. Maybe this was a temporarly problem.

Viewing 8 replies - 1 through 8 (of 8 total)
  • The topic ‘ImageOptimization: Failed to fetch’ is closed to new replies.