Support » Plugin: LiteSpeed Cache » Warning: fsockopen():

  • Resolved Alain Aubry

    (@caban13)


    Hi

    Since yesterday, every 30 mins, I am receiving an email with this text:

    "Warning: fsockopen(): unable to connect to node5.quic.cloud:443 (Connection timed out) in /home/xxx/public_html/domain.com/wp-content/plugins/litespeed-cache/src/utility.cls.php on line 169"

    Together, in the “LiteSpeed Cache General Settings” page I see:

    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://www.domain.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.:

    Please explain, what am I supposed to do, I don’t know anything about “POST callback” oe “allowlisted”.

    Thanks

    Alain

Viewing 5 replies - 1 through 5 (of 5 total)
  • RK

    (@rirgang)

    Same error since yesterday.

    HP Warning: fsockopen(): Unable to connect to node5.quic.cloud:443 (Connection timed out)

    Thread Starter Alain Aubry

    (@caban13)

    No answer here ?
    I still have the same problem …

    It looks similar to: https://wordpress.org/support/topic/unable-to-request-domain-key-error-503/
    so I whitelisted your IPs in CF firewall, just in case, no results

    Thread Starter Alain Aubry

    (@caban13)

    I allowlist your IPs in WordFence… no results…

    Still:

    Failed to communicate with QUIC.cloud server: The callback validation to your domain failed. Please make sure there is no firewall blocking our servers. Response code: 503

    • This reply was modified 4 months, 4 weeks ago by Alain Aubry.
    Plugin Support qtwrk

    (@qtwrk)

    Hi,

    apologize for the inconvenience

    this is known issue as some of the nodes are under heavy load

    we are also working on expanding our nodes

    best regards,

    Thread Starter Alain Aubry

    (@caban13)

    Hi

    Ok, so there is nothing I can do, just wait …

    Any prevision of a fix ?

    Thanks

    Alain

Viewing 5 replies - 1 through 5 (of 5 total)
  • You must be logged in to reply to this topic.