UCSS Queue Stuck, CCSS API Errors, and Node

  • Resolved junsozhang

    (@junsozhang)


    9 months, 3 weeks ago

    Hello Support Team,

    I am experiencing persistent issues with QUIC.cloud and LiteSpeed Cache integration on my WordPress site. Here are the key problems I am facing:

    1. UCSS Queue Stuck in 24-Hour Loop
      The UCSS (Unique CSS) queue repeatedly shows “Run UCSS Queue Manually – Available after X seconds.” Even after waiting 24 hours, the timer resets and I am forced to wait another 24 hours. This issue has continued for 3 consecutive days, and the queue never progresses.
    2. QUIC.cloud CCSS Notification Error
      I keep receiving the following error:
      “WordPress gave an unexpected response when notified with CCSS results from node 209.124.84.191. Check WP API is properly configured.”
      This error appears every time the service tries to notify WordPress with CCSS results. My host (Hostinger) has confirmed that, on shared hosting, there is no way to whitelist or allow external IP addresses individually.
    3. LiteSpeed Cache Node Connection Error
      I am also seeing:
      “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.”
      Again, my host has indicated that server-level firewall management is not available for individual accounts on shared hosting.
    4. LiteSpeed Cache Unexpected Response Error
      There are frequent errors such as:
      “LiteSpeed Cache: WordPress gave an unexpected response when notified with QUIC.cloud service results. Check WP API is properly configured. Check your QUIC.cloud dashboard for more details.”

    My Actions So Far:

    • Confirmed with Hostinger that firewall or server-level whitelisting is not possible on my shared hosting plan.
    • Verified that my WordPress site and REST API endpoints are accessible.
    • Checked QUIC.cloud and LiteSpeed Cache settings multiple times.

    Request:

    • Could you clarify why these issues keep occurring?
    • Is there a solution or workaround on shared hosting for these QUIC.cloud and LiteSpeed Cache errors?
    • What specific server or plugin settings can I check or adjust?
    • If the problem is due to hosting limitations, what are your recommended next steps for resolving or mitigating these issues?

    Thank you for your assistance.

    The page I need help with: [log in to see the link]

Viewing 7 replies - 1 through 7 (of 7 total)
  • Plugin Support qtwrk

    (@qtwrk)

    9 months, 3 weeks ago

    please provide the report number

    you can get it in toolbox -> report -> click “send to LiteSpeed”

    Thread Starter junsozhang

    (@junsozhang)

    9 months, 3 weeks ago

    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.

    LiteSpeed Cache: WordPress gave an unexpected response when notified with QUIC.cloud service results. Check WP API is properly configured. Check your QUIC.cloud dashboard for more details.

    Last Report Number: PLUMPTKF

    Last Report Date: 08/02/2025 02:18:04

    Plugin Support qtwrk

    (@qtwrk)

    9 months, 3 weeks ago

    I don’t see anything out of ordinary for instant

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

    Thread Starter junsozhang

    (@junsozhang)

    9 months, 3 weeks ago

    Already send by email。

    Last Report Number: BLVZVNEE

    Last Report Date: 08/07/2025 01:17:46

    Additional Questions Based on My Current Issue:

    1. In recent days, every time I click “Force cron,” it only processes about 10–30 items before stopping and jumping away.
    2. I have just over 10,000 pages, but after running for more than 10 days and processing over 20,000 requests, the queue is still not finished. The “Requests in queue” are always slow, stuck at 501. Previously, it only took about 4–5 days to process everything, but now the queue only handles 800–1500 items per day.

    Could you please help analyze what might be causing these problems and advise on solutions?

    Plugin Support qtwrk

    (@qtwrk)

    9 months, 3 weeks ago

    UCSS/CCSS is expensive operation , the UCSS/CCSS generation servers have limited capacity , so depends on overall load , sometimes it runs faster, sometimes it takes more time to finish

    for example , there is a vary for mobile , for desktop , for webp browser , and non-webp browser …etc , so each page , have multiple varies , in order to delivery the best outcome to fit each situation , they all needs to be processed.

    Thread Starter junsozhang

    (@junsozhang)

    9 months, 3 weeks ago

    can you helo to check my report and find the problem?

    In recent days, every time I click “Force cron,” it only processes about 10–30 items before stopping and jumping away.

    Plugin Support qtwrk

    (@qtwrk)

    9 months, 3 weeks ago

    I wouldn’t really classify it as “problem”

    from plugin side , every time when you run it, it will need to fetch the page , fetching the original page itself would take time , and each batch is limited to 120 seconds to avoid timeout.

    from node side , it also depends on node load , I will check up with maintenance team about this part though.

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

The topic ‘UCSS Queue Stuck, CCSS API Errors, and Node’ is closed to new replies.