Forum Replies Created

Viewing 1 replies (of 1 total)
  • Thread Starter somethingintheweb

    (@somethingintheweb)

    Hello,

    Thank you for your analysis and for checking the endpoint from your side.

    I just wanted to let you know that the issue is now resolved.

    After further investigation, the problem was caused by an inconsistent LiteSpeed Cache state following the manual removal of the wp-content/litespeed directory. This seems to have broken the internal QUIC.cloud linkage (tokens / generated data), which resulted in QUIC.cloud nodes being unable to properly reach the REST endpoints.

    I fixed the issue by:

    • Resetting LiteSpeed Cache settings
    • Fully uninstalling and reinstalling the LiteSpeed Cache plugin
    • Re-linking the site to QUIC.cloud

    After that, QUIC.cloud connectivity was restored and CCSS / UCSS generation is working normally again. The warning message no longer appears.

    For clarity: no changes were made to the hosting firewall configuration. TigerProtect and its existing security rules (including badbots protection) were left exactly as they were before the issue and remain enabled.

    Thanks again for your support and for pointing out the firewall behavior during your test.

    Best regards,
    Aurélien

Viewing 1 replies (of 1 total)