CSS generation with quic.cloud (load css async)
-
QUIC.cloud CCSS returning
node_wpapi_failedon every attempt. SiteGround confirmed requests reach the server fine. Wordfence allowlisted. Domain reconnected. REST API responds correctly from browser. LiteSpeed log shows the job posts to eu-service-ctr2.quic.cloud successfully with usage incrementing (quota going up each attempt), but callback always fails. Self-curl also returning 202 on some URLs instead of 200.Snippets of the logs:
02/27/26 19:45:56.133 [216.128.179.195:12136 1 9K2] ❄️ posting to : https://eu-service-ctr2.quic.cloud/queue02/27/26 19:45:57.530 [216.128.179.195:12136 1 9K2] ❄️ Service TTL to save: 176102/27/26 19:45:57.532 [216.128.179.195:12136 1 9K2] ❄️ ❌ Hit err _code: node_wpapi_failed02/27/26 19:45:57.532 [216.128.179.195:12136 1 9K2] ❄️ ❌ _err: WordPress gave an unexpected response when notified with QUIC.cloud service results. Check WP API is properly configured. --- array ( '_res' => 'err', '_code' => 'node_wpapi_failed', '_msg' => 'WordPress gave an unexpected response when notified with QUIC.cloud service results. Check WP API is properly configured.', '_ttl' => 1761, )02/27/26 19:45:58.649 [216.128.179.195:12136 1 9K2] 🕸️ ❌ Response code is not 200 in self_curl() [code] 20202/27/26 19:45:45.988 [216.128.179.195:12136 1 JS1] [REST] ✅ Internal REST ON [filter] rest_request_before_callbacks02/27/26 19:45:45.989 [216.128.179.195:12136 1 JS1] [REST] ❎ Internal REST OFF [filter] rest_request_after_callbacks
-
Well it seems you were right with the URL (as you knew), but Siteground does find issues with a few of the IP’s used.
“I have reviewed the logs and can confirm that requests such as the following were flagged by our CAPTCHA system:
57.129.146.219 POWC gtaretrofits.com [01/Mar/2026:09:00:09 +0000] "POST /?rest_route=/litespeed/v1/notify_ccss HTTP/1.1" 202 216 JA4:t13d171100_5b57614c22b0_6f9e9b12b7f2 "-" "Mozilla/5.0 AppleWebKit/537.36 (KHTML, like Gecko; compatible; qcbot/1.0; +http://quic.cloud/bot.html ) Chrome/112.0.0.0 Safari/537.36" 135.125.104.145 POWC gtaretrofits.com [01/Mar/2026:09:45:11 +0000] "POST /?rest_route=/litespeed/v1/notify_ccss HTTP/1.1" 202 217 JA4:t13d171000_5b57614c22b0_78e6aca7449b "-" "Mozilla/5.0 AppleWebKit/537.36 (KHTML, like Gecko; compatible; qcbot/1.0; +http://quic.cloud/bot.html ) Chrome/112.0.0.0 Safari/537.36"Although the user agent indicates qcbot/1.0, the IP address 57.129.146.219 also generated requests using a different user agent that is considered suspicious:
Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/78.0.3904.108 Safari/537.36
Public reports associate this type of activity with irregular or potentially malicious behavior. For reference, you may review the following article, which includes examples of similar user agents:
https://tehtris.com/en/blog/our-selection-of-alerts-on-honeypots-report-4-february-2023/
A similar pattern was observed for the other IP address, which also made requests using the Go-http-client user agent.
As a temporary measure, I have removed the limits on both IP addresses. However, I strongly recommend contacting QUIC.cloud to confirm whether these suspicious user agents are legitimately used by their service.“
Look forward to your reply.
yes , when a page is queued for something , say CCSS , it will queue the page , type , requested UA (whoever triggers this queue with bot-like ua cleansing) , post it to QC node
QC node then will use this user agent to fetch page , get critical css, then use
qcbotua post it back to site.
You must be logged in to reply to this topic.
