Support » Plugin: LiteSpeed Cache » Failed to notify WP to pick up optimized images

  • Resolved rafaucau

    (@rafaucau)


    For about five days I have a problem with image optimization. The following errors appear in my.quic.cloud/msg:

    Failed to notify WP to pick up optimized images
    Unable to notify WordPress to pick up images. Check QUIC.cloud IPs are whitelisted at the firewall.

    I checked the IP addresses on this page https://api.quic.cloud/ips and they are all whitelisted on my Cloudflare. I also asked my hosting to whitelist these addresses on the server.
    Unfortunately, errors are still appearing and pulling doesn’t work

    Report number: WMJOSIUB

Viewing 15 replies - 1 through 15 (of 19 total)
  • Your website returns a “404 page not found” on the notify URL: /wp-json/litespeed/v1/notify_img, thus notifying about optimized images fails.

    If your IP for your site has changed recently, you have to make sure it’s updated on my.quic.cloud, by going to the domain -> [6] Settings, and update the “Server IP”, since this is the one we use to communicate with.

    If the IP is correct, then you’ll have to check with your hosting provider why the URL returns a 404.

    Trying to do a test request currently to the endpoint, it does seem to return a “200 OK”.

    Thread Starter rafaucau

    (@rafaucau)

    @lucasrolff
    I checked the IP and it is correct.
    My hosting provider doesn’t know why there is a 404 error.

    Plugin Support qtwrk

    (@qtwrk)

    Hi,

    Please try clean up unfinished images and try again , the notify URL seems to be normalized now.

    Best regards,

    Thread Starter rafaucau

    (@rafaucau)

    @qtwrk
    It didn’t help, still the same notifications in https://my.quic.cloud/msg.
    At /wp-json/litespeed/v1/notify_img still 404

    • This reply was modified 1 year, 11 months ago by rafaucau.
    Plugin Support qtwrk

    (@qtwrk)

    Hi,

    please try refresh the domain key , then try again.

    Best regards,

    Thread Starter rafaucau

    (@rafaucau)

    @qtwrk
    Still 404 :<

    Thread Starter rafaucau

    (@rafaucau)

    @qtwrk
    The same problem also occurs on my two other websites.
    It stopped working on its own a few days ago. It’s weird.

    • This reply was modified 1 year, 11 months ago by rafaucau.
    Plugin Support qtwrk

    (@qtwrk)

    Hi,

    Please confirm that your origin IP is 109.9x.1xx.9 ?

    because if that so , you seems to have a invalid cert on your backend

    root@test:~# curl -i -d "test" --resolve a_____d.com.pl:443:109.xx.xxx.9  https://a_____d.com.pl/wp-json/litespeed/v1/notify_img -v
    * Added a_____d.com.com.pl:443:109.xx.xxx.9 to DNS cache
    * Hostname a_____d.com.com.pl was found in DNS cache
    *   Trying 109.xx.xxx.9:443...
    * TCP_NODELAY set
    * Connected to a_____d.com.pl (109.xx.xxx.9) port 443 (#0)
    * ALPN, offering h2
    * ALPN, offering http/1.1
    * successfully set certificate verify locations:
    *   CAfile: /etc/ssl/certs/ca-certificates.crt
      CApath: /etc/ssl/certs
    * TLSv1.3 (OUT), TLS handshake, Client hello (1):
    
    * TLSv1.3 (IN), TLS handshake, Server hello (2):
    * TLSv1.3 (IN), TLS handshake, Encrypted Extensions (8):
    * TLSv1.3 (IN), TLS handshake, Certificate (11):
    * TLSv1.3 (OUT), TLS alert, certificate expired (557):
    * SSL certificate problem: certificate has expired
    * Closing connection 0
    curl: (60) SSL certificate problem: certificate has expired
    More details here: https://curl.haxx.se/docs/sslcerts.html
    
    curl failed to verify the legitimacy of the server and therefore could not
    establish a secure connection to it. To learn more about this situation and
    how to fix it, please visit the web page mentioned above.

    Please fix this invalid cert on origin first

    Best regards,

    Thread Starter rafaucau

    (@rafaucau)

    @qtwrk

    My hosting provider has fixed the invalid cert.
    Running command curl -i -d "test" --resolve a_____d.com.pl:443:109.xx.xxx.9 https://a_____d.com.pl/wp-json/litespeed/v1/notify_img -v now returns status 200 OK

    I have refreshed my key, cleared unfinished data, and still have the same notifications on my.quic.cloud

    • This reply was modified 1 year, 11 months ago by rafaucau.

    When the actual request is made for the notify to happen, the 404 page returned refers to our hosting providers 404 page, and not the 404 page your website has.

    So likely the specific request being made towards them are blocked, or results in a 404 due to rules or configuration on your providers server.

    The notify request are coming from either 51.68.231.18 or 51.222.28.21, so they may be able to check the logs for requests from one of those IPs, to see what virtual host it hits on the server, or what rule might be triggered and thus blocking the request.

    Plugin Support qtwrk

    (@qtwrk)

    Hi,

    I’m going to mark this topic “Resolved,” due to lack of activity.

    If you still need help, please feel free to re-open the topic.

    Best regards,

    Thread Starter rafaucau

    (@rafaucau)

    @qtwrk
    I still need help.
    My hosting provider searched for the cause of the problem for quite a long time and couldn’t find it. The problem occurs only in one domain on all websites – GAJTARPE and SMKERJHK reports.

    My hosting support is asking how they can debug the connectivity problem, for more information from you or from the website. They do not have details of these requests in their logs.
    The address /wp-json/litespeed/v1/notify_img only returns {"_res": "err", "_ msg": "wrong_key"}. Of course, this error shows up because we don’t have a key to send in a request, but we don’t have any 404 error there.

    Maybe the problem is on the quic.cloud side?

    Neither of the sites linked in GAJTARPE and SMKERJHK reports have done any requests the past 13 days to the image optimization service.

    You’d have to do more requests for debugging to take place.

    Thread Starter rafaucau

    (@rafaucau)

    I cleaned up unfinished data and this time the optimization started working. I don’t know why it didn’t work before.

    Thread Starter rafaucau

    (@rafaucau)

    @qtwrk @lucasrolff
    The problem is back. Cleaning up unfinished data doesn’t help. Refreshing the domain key doesn’t help. I also checked the IP whitelist on Cloudflare and they are all added. My website’s IP address at my.quic.cloud is valid.
    What can cause this problem?

    Report number: GPLBYMSI

Viewing 15 replies - 1 through 15 (of 19 total)
  • The topic ‘Failed to notify WP to pick up optimized images’ is closed to new replies.