• <span style=”background-color: rgb(251, 251, 251); font-family: Inter, sans-serif; white-space: normal;”>Hi,</span>

    <span style=”background-color: rgb(251, 251, 251); font-family: Inter, sans-serif; white-space: normal;”> I have this alert message “LiteSpeed Cache: QUIC.cloud service nodes cannot reach your WP REST endpoints. Please check your WordPress or firewall setup. Check your QUIC.cloud dashboard for more details.”</span>

    Please advise <span style=”background-color: rgb(251, 251, 251); font-family: Inter, sans-serif; white-space: normal;”>how to fix it?</span>

    Report number HIFMHBPT was sent although i had this message :

    “NOTICE:

    To generate a passwordless link for LiteSpeed Support Team access, you must install DoLogin Security.” however, i did not install the plugin Dolofin security.

    thanks

Viewing 13 replies - 1 through 13 (of 13 total)
  • Thread Starter rawan2021

    (@rawan2021)

    oh i copied and pasted the error message from my site, can you guys read the above? not sure why is it coded.

    Thread Starter rawan2021

    (@rawan2021)

    can someone tell me if the above message is readable for you ?

    Plugin Support litetim

    (@litetim)

    @rawan2021
    I am able to read the message

    ONE THING that is important: we do not ask for password or access. Please read forum guidelines before writting anything about password or access.

    I see your site was connected to QC before.
    Looking over the report(thank you) I see that Server IP is empty, please make sure you have the server direct IP added(IP V4). Clear cache
    Disable Object cache too, BUT is should not create errors, but in worst case, please test this.
    Also follow this guide: https://wordpress.org/support/topic/troubleshooting-guide-wpapi-echo-data-failure/

    • This reply was modified 3 weeks, 4 days ago by litetim.
    Thread Starter rawan2021

    (@rawan2021)

    thank you .

    can you please explain in steps how and where to add the IP V4 ?

    regards

    Plugin Support litetim

    (@litetim)

    @rawan2021 you get the server IP from hosting, where it was registered and bought from

    Thread Starter rawan2021

    (@rawan2021)

    Hi

    I updated the IP address in lightspeed settings which now matches the QC IP address details for my site, yet, the error message is still present.

    Can you assist in solving this please?

    Thanks

    Plugin Support litetim

    (@litetim)

    @rawan2021 something is blocking LSC WP rest API.
    I see the WP API are accessible and working.

    Make sure you have the latest version of plugin
    Make sure there is no code(in theme that will block these)
    Also make sure wp-2fa plugin do not limit these API.

    Thread Starter rawan2021

    (@rawan2021)

    hi,

    yes lightspeed version is 7.9

    theme and 2FA has no blocking codes

    yet , warning message still there;(

    Thread Starter rawan2021

    (@rawan2021)

    I have contacted Quic Cloud and they guided me to adding their IPs to the firewall allowlist.

    Their guidelines suggests the following:

    LiteSpeed Web Server

    IP list automatically updated

    The latest versions of LiteSpeed Web Server will automatically update the QUIC.cloud IPs for you. No action is required.”

    So with the above version , why it isn’t updated ? I have error 520 on my site now , please advise the solution.

    Awaiting you’re response

    thanks

    Plugin Support litetim

    (@litetim)

    Hi @rawan2021,

    There are two separate layers here, and that’s where the confusion is coming from:

    1. LiteSpeed Web Server maintains its own allowlist automatically.
      Recent versions of LiteSpeed Web Server and OpenLiteSpeed keep the QUIC.cloud IP list updated by themselves — no action needed on that layer.

    One thing to double-check: “LiteSpeed 7.9” is the plugin version. The automatic IP updating is a feature of the web server, not the plugin. If your host runs Apache or nginx (with the plugin only), or an older LSWS build, nothing is updating those IPs for you and they have to be added manually. Ask your host which web server and version they run.

    1. Every other firewall keeps its own separate list.
      LSWS updating itself does not update anything else. If there is a server/network firewall (CSF, Imunify360, BitNinja, the cPanel/WHM firewall), a security plugin (Wordfence), a host-level WAF, a load balancer or reverse proxy, or Cloudflare in front of your origin, each one has to be allowlisted separately. Our IPs change often, so a one-time copy-paste is not enough — use the firewall’s auto-update option where it has one, or run the update script from cron.
    1. Find out which layer is producing the 520.
      A 520 means a proxy reached your origin but got no valid response back — i.e. something between QUIC.cloud and your server is refusing the connection. Identify which thing before changing settings:
    • Look at the error page and the response headers — they normally identify the service issuing it (QUIC.cloud vs Cloudflare vs your host’s WAF).
    • Then check that layer’s block/deny log around the same timestamp; you’ll usually see a QUIC.cloud IP being dropped or rate-
    • Ask your host directly whether they run any firewall or WAF in front of the server, and have them allowlist our IPs there.

    This is the same root cause as the original “QUIC.cloud service nodes cannot reach your WP REST endpoints” warning — our nodes are being blocked before they ever reach WordPress.

    1. If you’d like us to look at it directly, please open a ticket with QUIC.cloud support so we can check the node logs for your domain from our side:
      https://quic.cloud/support
    Thread Starter rawan2021

    (@rawan2021)

    Hi,

    A ticket was already opened with QC and here is the answer from yesterday’s conversation:

    Your ticket ” #8187170 Lightspeed warning message ” has been updated.
     

    Hi Rawan,

    As of now, I do not see any issues, and your domain is using the QUIC.cloud CDN.

    Regards

    Ashok

    Do you want me to open another ticket ?
    awaiting your reply.

    Thanks

    Rawan

    Plugin Support litetim

    (@litetim)

    @rawan2021 Let me talk to team and see what have been found.

    @rawan2021 could you confirm if you have dismissed that last error message?

    If you’ve already dismissed the old error message and received the new one, it means something is blocking our IPs on your server side, and unfortunately, when we’re blocked, there’s nothing we can do on our end.

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

You must be logged in to reply to this topic.