• Resolved realmranshuman

    (@realmranshuman)


    Images aren’t getting pulled. Clean Up Button, and Pull Images Button are disabled. True server cron is set and the cron job runs just fine. Tried the WordPress and the github master version of the plugin.

    Video: https://drive.google.com/file/d/1D9uyPkSV0NIN28ScEw0OupkpYwSiOBKg/view?usp=sharing

    Based on the other thread, I tried finding the reasons but I am not able to pinpoint it:

    Advanced Debugging with the url included img:

    Report Number: MKPSKKHL

    curl to ?rest_route=/litespeed/v1/notify_img with and without user agent.

    And the results for the:

    <?php

    require( './wp-load.php' );
    $args = array(
    'timeout' => 100,
    'blocking' => true,
    'sslverify' => false,
    // 'cookies' => $_COOKIE,
    );

    $url = 'https://' . $_SERVER['HTTP_HOST'] . '/wp-admin/admin-ajax.php?action=async_litespeed&nonce=123123123&litespeed_type=imgoptm_force';
    $result = wp_remote_post(esc_url_raw($url), $args);

    echo ''; var_dump($result); echo '';

    Dump’s Result

    Yes, I am using Cloudflare, but all of the QUIC cloud’s IPs are allowlisted on a regular basis, and I have compared the current list of IPs with the allowlisted one. It is in sync. The server’s own IP is also allowlisted. The server’s IP in the plugin’s settings and the QUIC Cloud is same and actual IP. Here’s how I do it in automated way: GitHub – realmranshuman/litespeed-quic-cloudflare-sync

    The hosting is shared hosting from Hostinger. They don’t have any options to block the IPs. The .htaccess is clean and doesn’t block REST endpoints, or anything similar. No security plugins, performance plugins, or any other plugins are blocking anything.

    The page I need help with: [log in to see the link]

Viewing 9 replies - 1 through 9 (of 9 total)
  • Plugin Support litetim

    (@litetim)

    @realmranshuman
    Please add this code in theme => functions.php and run it once, then remove it.

    !class_exists('\LiteSpeed\Cloud') || \LiteSpeed\Cloud::save_summary(['disabled_node' => [], 'err_domains' => []]);

    Clear cache and try connecting to QC. If this is not working please tell me.

    • This reply was modified 6 months, 4 weeks ago by litetim.
    Thread Starter realmranshuman

    (@realmranshuman)

    @litetim I added the code to the functions.php file> loaded a page > Sent Optimization Request > Removed the code from the functions.php > Toolbox > Purge All …..> Waited few minutes > Sent Optimization Request > The problem still exists. Tried multiple combinations of the steps.

    The count of the images pulled remained the same. Clean Up Finished Data numbers diminished and disappeared way too quick as shown in the attached video.

    https://ibb.co/fYKk2Sw0

    Plugin Support litetim

    (@litetim)

    @realmranshuman
    I see you wrote about logs. Can you share logs about image otpimization PULL action?

    Thread Starter realmranshuman

    (@realmranshuman)

    @litetim Well, for starters, the Pull Images button is disabled/greyed out. The cron isn’t pulling the images either. On top of that, the credits are getting spent with each “Send Optimization Request”. So, no.. I am not able to share the pull action log, as I am not able to pull the images in any capacity. I can’t even “Destroy all optimization data” because 59099 images have been optimized before using paid credits, and it will go to waste.

    But, here’s the log for the “Send Optimization Request”.

    Logs

    Plugin Support litetim

    (@litetim)

    @realmranshuman I will ask colleagues from QC and see what happens.

    Until then:
    is your quota being used?
    I see 10k left, yesterday were 6k+.

    • This reply was modified 6 months, 4 weeks ago by litetim.
    Thread Starter realmranshuman

    (@realmranshuman)

    @litetim Yes, the quota is being used. All the images before this problem began, are optimized and their optimized and backup versions exist on the disk.

    For some reason, LiteSpeed cache plugin stopped recognizing the last 20-25% images as optimized.. even though the optimized versions of the files exist on the disk.

    And now when it sends the request> uses the quota> finds that there is no need to pull the images as the images exist on the disk> doesn’t pull the images > increases the id counter (images pulled counter remains unchanged)> The percentage circle increases (over several hours just a percent.. we have lot of images)

    My hypothesis based on what I can read in the logs: it is just building the part of the database that it doesn’t recognize any longer at the expense of QUIC Cloud credits. There are thousands of images that are optimized, and their files exist on the disk, but the litespeed tables/rows all of a sudden lost the data, or aren’t able to recognize the data for those last 20-25% of images.

    So how do I fix this? I can’t possibly destroy all the optimization data… there are over 100K images, and it will cost Quic Cloud credits. Not to mention that it will take weeks worth of time.

    Plugin Support litetim

    (@litetim)

    @realmranshuman change this to OFF https://docs.litespeedtech.com/lscache/lscwp/imageopt/#auto-request-cron and I am looking into, to see what we can resolve

    Thread Starter realmranshuman

    (@realmranshuman)

    @litetim any updates for the codeblock that can fix this? Since it can take time on your end, we are letting the cron run at the cost of credits so altleast the images that already have their optimized files on the disk, can get served.

    Plugin Support qtwrk

    (@qtwrk)

    please try this

    go to toolbox -> debug setting -> set debug log to ON , debug level to advance

    set log size to 30 M

    add litespeed_type=new_req , and notify_img and litespeed_type=imgoptm into Debug Include URI

    then go to log view, clean up existing log if any

    then go to image optm summary page , click “clean up unfinished data” if you have any

    then send request again

    wait for 10 minutes

    go back to log view again ,copy paste and share the log

Viewing 9 replies - 1 through 9 (of 9 total)

The topic ‘Images aren’t getting pulled.’ is closed to new replies.