Image Pull not working

When I try to give next optimization request, following is the error message:

Failed to communicate with QUIC.cloud server: There is proceeding queue not pulled yet. [server] https://node4.quic.cloud [service] img_optm

(i.is.cc/2kOJMETE.png)

Kindly look into it.

Thanks

Same problem here.
Cloud Error: Please try after 3m 54s for service img_optm-new_req.
then
Failed to communicate with QUIC.cloud server: There is proceeding queue not pulled yet. [server] https://node8.quic.cloud [service] img_optm

Adding these IP addresses to the Cloudflare whitelist did not help:
https://api.quic.cloud/ips
https://wp.api.litespeedtech.com/ips

• This reply was modified 4 years, 7 months ago by Rafa? Ca?ka.

Hi,

Please make sure your wp-cron is working and pulling back images.

Please kindly try system cron job instead of wp cron job.

Best regards,

Hi,

If the cron was not working, then how the 66% of images were pulled?

I started pulling all the images from 1% to 66%. It stopped automatically at 66% and not proceeding further.

Kindly look into it.

Thanks

Hi @qtwrk

I confirm that system cron also works for me.
The optimization worked on version 2.9 (with some problems, but it was possible to fix it by cleaning the unfinished data. Now nothing helps). After upgrading to 3.0 it broke.

On my.quic.cloud, I see that once in a few hours, a few old gifs are sent and then the optimization hangs again

Report number: LNTPQJUY

• This reply was modified 4 years, 7 months ago by Rafa? Ca?ka.
• This reply was modified 4 years, 7 months ago by Rafa? Ca?ka.
• This reply was modified 4 years, 7 months ago by Rafa? Ca?ka. Reason: More info

If you meet that error, showing proceeding queue not pulled, in v3, can use same way, clean up unfinished data. That will clear your unfinished queue on the node. Next request will not see that error.

Hi @hailite

On v3 it doesn’t help.

I have this errors:
Cloud Error: Please try after 3m 54s for service img_optm-new_req.

Failed to communicate with QUIC.cloud server: There is proceeding queue not pulled yet. [server] https://node8.quic.cloud [service] img_optm

• This reply was modified 4 years, 7 months ago by Rafa? Ca?ka.

@hailite The basic suggestions made by you were already done. Still no change or improvement.

Check the time of last submit and pull (i.is.cc/2mC9B3hD.png)

In my opinion, the pull job is not working properly in both ways (either by cron or my manual pull)

Kindly have a look into it.

Thanks,

W/ v3.0.8.5, you will be able to see the details on the previous request current status.

Hi

Thanks for the update. Now pulling is working properly (i.is.cc/2mXzzBf6.png)

Regards,

Vijila

@hailite I think, I found the basic problem for this image pulling. It is because of QUIC cloud Fast Queue Usage. From the QUIC dashboard, you can see the In queue & In processing as “0”

As per the screen shot, the images can be uploaded unlimited. But when the threshold of 5000 is reached, it immediately stops the upload as well as pull.

Kindly see the following two screenshots:

1) i.is.cc/2nXsDXKz.png
2) i.is.cc/2nXAznTe.png

Last time also, this issue happened when the threshold limit of 5000 is reached.

Kindly have a look into this.

Thanks,

Vijila

P.S.
If possible can we link it to Cloudfare instead of QUIC ?

• This reply was modified 4 years, 6 months ago by Home Remedies and Natural Treatments.
• This reply was modified 4 years, 6 months ago by Home Remedies and Natural Treatments.

@hailite

Following is the code error which I get when I try to manually send request

Failed to communicate with QUIC.cloud server: There is proceeding queue not pulled yet. Queue info: s3moved 200 [priority] 101000. [server] https://node4.quic.cloud [service] img_optm

Also, “Pull Images” is not getting enable for manual pulling.

Thanks

Hi,

when you have fast queue run out , it will still work with standard queue.

If possible can we link it to Cloudfare instead of QUIC ?

it’s different thing, you can use CF if you wish , link to QUIC is just mean to enabling you detailed dashboard for online services.

Also, “Pull Images” is not getting enable for manual pulling.

what do you mean ? you mean manual pull doesn’t work ?

Best regards,

1) It is not working with standard queue (screenshot – i.is.cc/2rDus9Sw.png)

2) Manual pull means, user manually clicking the pull button (it is not possible because the pull button is always disabled) (screenshot – i.is.cc/2rDq8lBO.png)

3) In the optimization summary in the dashboard, you can see only 16% of images are shown as prepared, I don’t understand that, because images requested are 91%, then what about the remaining images?

4) Likewise, the page speed score has decreased from 70 to 64.

Kindly guide me how to resolve the above 4 issues.

Thanks

Hi,

Could you please upgrade v3.0.8.6 , clean up unfinished data, then try again ? it fixes some image opt related issue.