Title: CSS generation with quic.cloud (load css async) Last modified: February 28, 2026 --- # CSS generation with quic.cloud (load css async) * Resolved [gtaretrofits](https://wordpress.org/support/users/gtaretrofits/) * (@gtaretrofits) * [3 months ago](https://wordpress.org/support/topic/css-generation-with-quic-cloud-load-css-async/) * QUIC.cloud CCSS returning `node_wpapi_failed` on 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/queue ` `02/27/26 19:45:57.530 [216.128.179.195:12136 1 9K2] ❄️ Service TTL to save: 1761 ``02/27/26 19:45:57.532 [216.128.179.195: 12136 1 9K2] ❄️ ❌ Hit err _code: node_wpapi_failed ``02/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] 202``02/27/ 26 19:45:45.988 [216.128.179.195:12136 1 JS1] [REST] ✅ Internal REST ON [filter] rest_request_before_callbacks``02/27/26 19:45:45.989 [216.128.179.195:12136 1 JS1] [REST] ❎ Internal REST OFF [filter] rest_request_after_callbacks` Viewing 12 replies - 1 through 12 (of 12 total) * Plugin Support [qtwrk](https://wordpress.org/support/users/qtwrk/) * (@qtwrk) * [3 months ago](https://wordpress.org/support/topic/css-generation-with-quic-cloud-load-css-async/#post-18837042) * please provide the report number * you can get it in toolbox -> report -> click “send to LiteSPeed” * Thread Starter [gtaretrofits](https://wordpress.org/support/users/gtaretrofits/) * (@gtaretrofits) * [3 months ago](https://wordpress.org/support/topic/css-generation-with-quic-cloud-load-css-async/#post-18837044) * **NSBGFBZT** * Plugin Support [qtwrk](https://wordpress.org/support/users/qtwrk/) * (@qtwrk) * [3 months ago](https://wordpress.org/support/topic/css-generation-with-quic-cloud-load-css-async/#post-18837055) * ![](https://i0.wp.com/i.imgur.com/GvdEjip.png?ssl=1) * i think this is what blocks node connection * Thread Starter [gtaretrofits](https://wordpress.org/support/users/gtaretrofits/) * (@gtaretrofits) * [3 months ago](https://wordpress.org/support/topic/css-generation-with-quic-cloud-load-css-async/#post-18837074) * So quic’s own bot detection has been driving me insane for hours. Phenomenal. Once I added the quic ip list (well 100 of the 154) to my allow list, I don’t have the issue. That is insanely frustrating. * Plugin Support [qtwrk](https://wordpress.org/support/users/qtwrk/) * (@qtwrk) * [3 months ago](https://wordpress.org/support/topic/css-generation-with-quic-cloud-load-css-async/#post-18837082) * ```wp-block-code