WordPress not accepting QUIC.cloud REST API callbacks
-
LiteSpeed Cache version: 7.8.1
Hosting: FastComet (shared hosting)
Other relevant plugins: WordFence Security (Pro), WooCommerce, Rank Math SEO
Cloudflare: DNS only (not proxied) — not the cause of any REST blockingThe problem:
QUIC.cloud is able to send optimization work to my site (VPI/CCSS requests are going out, and Image Optimization has completed successfully — 53,900+ images pulled), but when QUIC.cloud’s servers try to call back into my site’s REST API to deliver finished results, that callback fails.Symptoms:
- LiteSpeed Cache dashboard shows: “WordPress gave an unexpected response when notified with QUIC.cloud service results. Check WP API is properly configured.”
- The
node_wpapi_failedflag appears persistently across the LiteSpeed Cache dashboard (visible in the query string of every action link — Refresh Usage, Refresh Status, etc.) - QUIC.cloud dashboard shows repeated “Invalid WP API response” entries and “CCSS generation failed” errors across multiple pages/templates (not limited to one template type)
Diagnostic steps already taken:
- Manually tested the plugin’s REST endpoint directly:
/wp-json/litespeed/v1/notify_vpiResponse:
{"code":"rest_no_route","message":"No route was found matching the URL and request method.","data":{"status":404}}This suggests the route isn’t registered with WordPress’s REST API at all (a 404
rest_no_route, not a 403 firewall block).- Flushed permalinks (Settings → Permalinks → Save) — no change.
- Allowlisted LiteSpeed’s REST namespace (
/wp-json/litespeed/v1/,/wp-json/litespeed/v3/,/wp-json/litespeed/*) in WordFence’s firewall, plus allowlistedcheck.lscache.io— no change. - Applied the community-documented
disabled_nodereset fix:
php
add_action('init', function() { if (class_exists('\LiteSpeed\Cloud')) { \LiteSpeed\Cloud::save_summary(['disabled_node' => []]); } });This has been running in my child theme’s
functions.phpfor several years, with no change to the underlying problem.Question for support:
Since this has persisted for years despite the standard fixes, and the REST endpoint itself returnsrest_no_routerather than a firewall-style block, could you check server-side whether this route is registering correctly for my site/hosting environment? Happy to send an Environment Report (Toolbox → Report → Send to LiteSpeed) if that helps.Feel free to send the Environment Report alongside this note if their ticket form allows an attachment — I mentioned it at the end so they know it’s available.
The page I need help with: [log in to see the link]
You must be logged in to reply to this topic.