Any known issues with WP API? VPI queue not clearing

  • Resolved pineapplepalm

    (@pineapplepalm)


    8 months, 3 weeks ago

    Case number: GDJYNTXR

    Having persistent issue with WP API nodes giving 401 error.

    Cloudflare is all clearing these (all 146 nodes are in IP list allow on Cloudflare), our server shows
    2025-09-18 09:53:10.880118 [INFO] [1610946] [T3] [162.158.10.176:18602:HTTP2-1#APVH_ourdomain.app:443] Error while parsing request: (null)!

    I removed our domain and replaced with “ourdomain” for privacy.

    I am using new rewrite rules also to ensure it runs:

    2B. — 18 SEPT 2025 ALLOW LiteSpeed/QUIC API calls before global blocks —

    RewriteEngine On # Allow LiteSpeed Cache + QUIC.cloud callbacks RewriteCond %{REQUEST_URI} ^/wp-json/litespeed/ [NC] RewriteRule .* – [L] — END allow —

    2C. — 18 SEPT 2025 Also allow the rest_route form used by QUIC

    RewriteEngine On RewriteCond %{QUERY_STRING} (^|&)rest_route=/litespeed/ [NC] RewriteRule .* – [L]

    Can you advise why these nodes are still being problematic? Which is leading to 255 in the VPI queue and the CCSS queue with 137 (though this has been increasing and decreasing over the last 20 hours)

    Standing by for feedback and support

    • This topic was modified 8 months, 3 weeks ago by pineapplepalm.
Viewing 15 replies - 1 through 15 (of 19 total)
1 2
  • Plugin Support qtwrk

    (@qtwrk)

    8 months, 3 weeks ago

    for 401 error, it’s either rest api is disabled rest api , or our IP verification failed

    please go to toolbox -> debug setting -> set debug log to ON , debug level to advance, add rest_route=/litespeed into debug include uri ,

    then go to log view , clean up existing log if any

    once you have prepared, please let me know, I will send a test request

    Thread Starter pineapplepalm

    (@pineapplepalm)

    8 months, 3 weeks ago

    Hi, all done. but I think it’s worth knowing that, prior to getting your email my hist suggested disconnecting from QUIC, and then reconnecting. I disconnected, however reconnecting has proven impossible.

    I was getting this for a while:

    Failed to communicate with QUIC.cloud server: Unknown error: unknown [server] https://wpapi.quic.cloud [service] tool/wp_rest_echoDismiss this notice.

    QUIC.cloud’s access to your WP REST API seems to be blocked.

    ===== but I ensured that was resolved on Cloudflare. It wont connect to QUIC, but also wont give me any clear reason I could see as to why. I am now getting the same error message “Failed to communicate with QUIC.cloud server: Unknown error: unknown [server] https://wpapi.quic.cloud [service] tool/wp_rest_echoDismiss this notice.”

    So now, I have done what you said and here is the

    Last Report Number: EWZMHYYZ

    Last Report Date: 09/19/2025 04:47:16

    Standing by for your assistance. Thank you.

    • This reply was modified 8 months, 3 weeks ago by pineapplepalm.
    • This reply was modified 8 months, 3 weeks ago by pineapplepalm. Reason: editing the report number
    • This reply was modified 8 months, 3 weeks ago by pineapplepalm.
    Thread Starter pineapplepalm

    (@pineapplepalm)

    8 months, 3 weeks ago

    and one more:

    Last Report Number: BPTDMDUF

    Last Report Date: 09/19/2025 04:57:00

    Plugin Support qtwrk

    (@qtwrk)

    8 months, 3 weeks ago

    I just sent a test request at Fri Sep 19 11:33:43 PM UTC 2025 , please check the debug log and share it to me

    Thread Starter pineapplepalm

    (@pineapplepalm)

    8 months, 3 weeks ago

    the report got flagged and is being held for volunteer moderation. Please share an email address if you want me to send it directly more quickly

    Moderator Support Moderator

    (@moderator)

    8 months, 3 weeks ago

    @pineapplepalm: I have archived your post because it contained far too much unformatted code, including strange graphics. I would recommend using https://pastebin.com, https://gist.github.com/ or similar platforms to show source code.

    Thread Starter pineapplepalm

    (@pineapplepalm)

    8 months, 3 weeks ago

    Yeah the strange graphics come from the report itself, and I just tried Pastebin it wont accept @qtwrk Litespeed support please provide some other way for me to send the report

    Thread Starter pineapplepalm

    (@pineapplepalm)

    8 months, 3 weeks ago

    @qtwrk upon checking I see one of the issues is “not our IP” is coming as the issue. In the echo, our Cloudflare IP address is echoed back since we’ve scoped traffic to CF IP ranges for security hardening, but LS Cache /QUIC is unable to see past that despite having CF in our settings within the LSCWP with API in the cloudflare settings page.

    This seems to be why it’s being blocked.
    “09/19/25 19:33:33.637 [172.70.111.34:56886 1 sIs] 2nd time: Not our cloud IP” (i removed the snoflake and red x emojis to prevent this post being flagged).

    Can you note if theres a way around this without us having to change our server settings?

    Thread Starter pineapplepalm

    (@pineapplepalm)

    8 months, 3 weeks ago

    Hi, just to advise. I have resolved this problem.

    Resolution was CF Connecting For on our server needed to reflect real origin IP in order to echo. the problem is resolved as of now. I will contact again if it reoccurs. QUIC is reconnected and no more WP API errors present.

    Only last thing oto wait out is if the VPI and CCSS queues clear

    Thread Starter pineapplepalm

    (@pineapplepalm)

    8 months, 3 weeks ago

    Hi still seeing errors on our server:

    Critical CSS Requests in queue: 46

    Viewport Image (VPI) STILL not changed Requests in queue: 255

    I have added Last Report Number: LYTDQOSY Last Report Date: 09/23/2025 12:19:22

    Server errors shown:

    [22-Sep-2025 17:47:07 UTC] Cron unschedule event error for hook: litespeed_task_ccss, Error code: could_not_set, Error message: The cron event list could not be saved., Data: {“schedule”:”litespeed_filter”,”args”:[],”interval”:60}
    [22-Sep-2025 18:01:06 UTC] Cron reschedule event error for hook: llms_end_idle_sessions, Error code: could_not_set, Error message: The cron event list could not be saved., Data: {“schedule”:”every_five_mins”,”args”:[],”interval”:300}
    [22-Sep-2025 18:01:06 UTC] Cron unschedule event error for hook: llms_end_idle_sessions, Error code: could_not_set, Error message: The cron event list could not be saved., Data: {“schedule”:”every_five_mins”,”args”:[],”interval”:300}
    [22-Sep-2025 18:18:06 UTC] Cron reschedule event error for hook: better_messages_send_notifications, Error code: could_not_set, Error message: The cron event list could not be saved., Data: {“schedule”:”bp_better_messages_notifications”,”args”:[],”interval”:120}
    [22-Sep-2025 18:18:06 UTC] Cron unschedule event error for hook: better_messages_send_notifications, Error code: could_not_set, Error message: The cron event list could not be saved., Data: {“schedule”:”bp_better_messages_notifications”,”args”:[],”interval”:120}
    [22-Sep-2025 18:18:06 UTC] Cron reschedule event error for hook: litespeed_task_imgoptm_req, Error code: could_not_set, Error message: The cron event list could not be saved., Data: {“schedule”:”litespeed_filter”,”args”:[],”interval”:60}
    [22-Sep-2025 18:18:06 UTC] Cron unschedule event error for hook: litespeed_task_imgoptm_req, Error code: could_not_set, Error message: The cron event list could not be saved., Data: {“schedule”:”litespeed_filter”,”args”:[],”interval”:60}
    [22-Sep-2025 18:18:06 UTC] Cron reschedule event error for hook: litespeed_task_ucss, Error code: could_not_set, Error message: The cron event list could not be saved., Data: {“schedule”:”litespeed_filter”,”args”:[],”interval”:60}
    [22-Sep-2025 18:18:06 UTC] Cron unschedule event error for hook: litespeed_task_ucss, Error code: could_not_set, Error message: The cron event list could not be saved., Data: {“schedule”:”litespeed_filter”,”args”:[],”interval”:60}
    [22-Sep-2025 18:18:06 UTC] Cron reschedule event error for hook: litespeed_task_vpi, Error code: could_not_set, Error message: The cron event list could not be saved., Data: {“schedule”:”litespeed_filter”,”args”:[],”interval”:60}
    [22-Sep-2025 18:18:06 UTC] Cron unschedule event error for hook: litespeed_task_vpi, Error code: could_not_set, Error message: The cron event list could not be saved., Data: {“schedule”:”litespeed_filter”,”args”:[],”interval”:60}
    [22-Sep-2025 18:18:06 UTC] Cron reschedule event error for hook: litespeed_task_lqip, Error code: could_not_set, Error message: The cron event list could not be saved., Data: {“schedule”:”litespeed_filter”,”args”:[],”interval”:60}
    [22-Sep-2025 18:18:06 UTC] Cron unschedule event error for hook: litespeed_task_lqip, Error code: could_not_set, Error message: The cron event list could not be saved., Data: {“schedule”:”litespeed_filter”,”args”:[],”interval”:60}
    [22-Sep-2025 18:18:06 UTC] Cron reschedule event error for hook: litespeed_task_avatar, Error code: could_not_set, Error message: The cron event list could not be saved., Data: {“schedule”:”litespeed_filter”,”args”:[],”interval”:60}
    [22-Sep-2025 18:18:06 UTC] Cron unschedule event error for hook: litespeed_task_avatar, Error code: could_not_set, Error message: The cron event list could not be saved., Data: {“schedule”:”litespeed_filter”,”args”:[],”interval”:60}
    [22-Sep-2025 18:18:06 UTC] Cron reschedule event error for hook: litespeed_task_ccss, Error code: could_not_set, Error message: The cron event list could not be saved., Data: {“schedule”:”litespeed_filter”,”args”:[],”interval”:60}
    [22-Sep-2025 18:18:06 UTC] Cron unschedule event error for hook: litespeed_task_ccss, Error code: could_not_set, Error message: The cron event list could not be saved., Data: {“schedule”:”litespeed_filter”,”args”:[],”interval”:60}

    Appreciate a solution

    Plugin Support litetim

    (@litetim)

    8 months, 3 weeks ago

    @pineapplepalm cron error is known issue in WP code. We have looked into and we need to wait for WP to fix the issue.

    Thread Starter pineapplepalm

    (@pineapplepalm)

    8 months, 3 weeks ago

    Right… Can you advise about the VPI and CCSS queues AND the last report I provided also please?

    How can I get the 255 VPI to clear the queue and the 46 CCSS to clear too?

    Plugin Support litetim

    (@litetim)

    8 months, 3 weeks ago

    @pineapplepalm There is a Clear button on the right side of the list.

    Thread Starter pineapplepalm

    (@pineapplepalm)

    8 months, 3 weeks ago

    Clearing isnt the issue I want the queues to actually PROCESS to QUIC (we dont use CDN) please advise

    Plugin Support litetim

    (@litetim)

    8 months, 2 weeks ago

    @pineapplepalm
    I would clear the lists(both) to make sure it starts fresh.
    I looked over settings and connection to your site.
    I see that our API requests hit 404, meaning that links are not accessible from the site. Please make sure that firewall is not blocking WP API requests.

    Also I see some nodes in use are disabled too. Please add this code to theme => functions.php. Clear cache, run any page once and remove the code from functions.php
    !class_exists('\LiteSpeed\Cloud') || \LiteSpeed\Cloud::save_summary(['disabled_node' => []]);
    Then create a new report to see if the code has made the changes.

Viewing 15 replies - 1 through 15 (of 19 total)
1 2

The topic ‘Any known issues with WP API? VPI queue not clearing’ is closed to new replies.