Failed to request via WordPress: cURL error 28: Operation timed out after 15001

  • Resolved zorrofes

    (@zorrofes)


    11 months, 2 weeks ago

    Dear Support,

    Some days ago, when i open my WordPress Dashboard, i have this message:

    Failed to request via WordPress: cURL error 28: Operation timed out after 15001 milliseconds with 0 bytes received [server] https://node117.quic.cloud [service] img_optm

    Also, when i tried to Refresh Domain Key, i have this message:

    Notice:

    There was a problem with retrieving your Domain Key. Please click the Waiting for Refresh button to retry.

    There are two reasons why we might not be able to communicate with your domain:

    1) The POST callback to https://genialmall.com/wp-json/litespeed/v1/token failed.

    2) Our Current Online Server IPs was not allowlisted.

    Please verify that your other plugins are not blocking REST API calls, allowlist our server IPs, or contact your server admin for assistance.

    I searched in lot your forums and others, i didn’t find the solution.

    I already disabled plug-ins security, also i add whitelist IP in Wordfence.

    My Litespeed Cache is 6.0 || But i have always this message in wordpress:

    LiteSpeed Cache: New Version Available

    “Good news! A new version of LSCWP is available now. Please upgrade to v5.7.0.1 for some important bug fixes.”

    Please, i need your help asap.

    Best regards & Have a nice day.

    Thanks.

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

  • The cURL error 28 already has an open thread…

    cURL error 28 (img_optm)

    They are blaming the amount of traffic to the node causing the error that didn’t exist before this last update.

    Plugin Support qtwrk

    (@qtwrk)

    yes , because in v6.0 , there is a new feature “Parallel pull” for image optm

    before it was single-thread , which means images are being pulled back one by one , but with this new release , it can do multiple pulls at once , which also means multiple loads put on our image servers

    this was not expected and our developers are exploring all the possibility to improve the situation.

    Thread Starter zorrofes

    (@zorrofes)

    thank you for answer.

    i see the other Topic after opening my thread.

    Thanks.

    Plugin Support qtwrk

    (@qtwrk)

    we’ve released v6.0.0.1 as hotfix , in next couple days the load will stablize and everything will back to normal

    Thread Starter zorrofes

    (@zorrofes)

    Hi qtwrk,

    Yes, i see. But i tested a lot of times, i dont have:

    Failed to request via WordPress: cURL error 28: Operation timed out after 15001 milliseconds with 0 bytes received.

    But, NO COMMUNICATION and after 15min, i have this message:

    There was a problem with retrieving your Domain Key. Please click the Waiting for Refresh button to retry.

    There are two reasons why we might not be able to communicate with your domain: ….. Like before.

    And i receive a message in my email from Quic Cloud:

    CDN Setup Error

    The CDN setup for the domain https://Mydomain.com has been paused due to an error. Please resolve the error and try again.

    Error: ‘Failed in an unexpected state.’.

    Sincerely,
    The QUIC.cloud Team

    I disabled Firewall, same problem.

    I have now 6.0.0.1, but always wordpress ask me to upgrade to v5.7.0.1 ??

    https://i.ibb.co/5TKGr3D/litespeed-upg.jpg

    Thank you very much.

    Thread Starter zorrofes

    (@zorrofes)

    A Domain Key is required for QUIC.cloud online services.
    ?? Main domain not generated yet

    ?? For online services to work correctly, you must allowlist all QUIC.cloud server IPs.

    Plugin Support qtwrk

    (@qtwrk)

    interesting issue , I see our request was stuck on a redirection

    please create a ticket by mail to support at litespeedtech.com with reference link to this topic , we will investigate further.

    Thread Starter zorrofes

    (@zorrofes)

    Thank you qtwrk.

    I sent email and i’m waiting the answer.

Viewing 8 replies - 1 through 8 (of 8 total)
  • The topic ‘Failed to request via WordPress: cURL error 28: Operation timed out after 15001’ is closed to new replies.