• Resolved fabsberry

    (@fabsberry)


    Hello,

    I’m a new LSCache user and I installed the WordPress plugin yesterday for the first time. But the image optimisation doesn’t work.

    After my optimisation request, I get an error:

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

    “Cloud Error: Please try after 5m 00s for service img_optm-new_req.”

    I have absolutely no idea what I can do to fix that ??
    The other chache functions seem to work.

Viewing 11 replies - 1 through 11 (of 11 total)
  • Plugin Support LiteSpeed Lisa

    (@lclarke)

    Hi, @fabsberry and welcome to LSCache ??

    Have you already submitted one request?

    The way Image Optimization works, all images from the previous request must be optimized and pulled before a new request can be sent, so usually, that message you are getting indicates that the previous optimization cycle is not yet complete. It should jut be a matter of waiting for it to finish up.

    This can take anywhere from 30 seconds to (worst case) multiple hours if the queue is unusually busy.

    If you don’t have a request in progress, let us know and we’ll investigate further.

    I’m currently experiencing the same issue with node8. Waiting several hours for a few images, and still waiting. This is with the “Fast Queue”.
    Another site that is connected to node5 has no issues at all.

    Maybe you could have a look into node8 as it seems to be struggling?

    Thread Starter fabsberry

    (@fabsberry)

    Hello, @lclarke

    I uploaded a screenshot of the current status: https://ibb.co/JFHZwzn

    It looks like I can’t pull the other requested images(?). I already destroyed the optimised images but every time I get only 5 optimised images and not more.

    I′m getting this error on the wordpress dashboard when I′m editing an article:

    Cloud Error: Please try after 18s for service lqip.

    Plugin Support qtwrk

    (@qtwrk)

    Hi,

    @fabsberry there was an issue with node , please try upgrade to v3.0.8.6 , then clean up unfinished data, then try again, it should work now.

    @luis1950 please open a separated. topic for your issue.

    Best regards,

    Using plugin version 3.0.8.6 I still have issues with node8:

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

    It seems like some of the images are processed almost immediately, and the process then stops. This is based on the “Last Optimized Images” in the dashboard.
    Cron is running every 10 minutes, and a manual pull doesn’t seem to do anything. Even after waiting 3 hours.

    Plugin Support qtwrk

    (@qtwrk)

    Hi,

    please submit a ticket here , we will investigate it further.

    best regards,

    Hi
    I am getting the same error from last three days
    Failed to communicate with QUIC.cloud server: There is proceeding queue not pulled yet. Queue info: raw 11 [priority] 8180. [server] https://node16.quic.cloud [service] img_optm

    Another problem when I enable LiteSpeed plugin images not load in China.
    My friends in china not able to see the website Images. but no problem with another country users.
    When I disable Litespeed plugin images start showing on my website in China too.

    I’ve just installed and had this same problem

    Failed to communicate with QUIC.cloud server: Unknown error: Array [server] https://node2.quic.cloud [service] health

    Plugin Support Hai Zheng?

    (@hailite)

    @diyhobbies Since v3.2+, should have no that img_optm issue anymore. The new image optimization process is changed.

    @brian_milnes Can you tell which operation you did when seeing that error?

    When I clicked on Gather Image Information (after setting up Quic Cloud) it returned the button in the same state, and no collection occurred.
    When I clicked on one of the options (page speed, I think) on the Quic Dashboard (in Litespeed) it then returned the error at the top of the Dashboard.
    I have now, disappointingly, had to remove the Plugin.

Viewing 11 replies - 1 through 11 (of 11 total)
  • The topic ‘Image optimisation: cloud error’ is closed to new replies.