BugWP logo BugWP
Back to Community
Home / Community / Plugin → Litespeed cache

Troubleshooting QUIC.cloud Connection and REST API Errors in LiteSpeed Cache

44 threads Sep 7, 2025 Plugin → Litespeed cache

Content

Why Am I Seeing QUIC.cloud Connection and REST API Errors?

Many users of the LiteSpeed Cache plugin encounter two common and often related error messages when trying to integrate with the QUIC.cloud CDN and optimization service:

  • "Site not recognized. QUIC.cloud deactivated automatically. Please reactivate your QUIC.cloud account."
  • "Unauthorized access to REST API. Your token has expired."
  • "QUIC.cloud service nodes cannot reach your WP REST endpoints."

These errors prevent the plugin from communicating with QUIC.cloud's servers, halting services like CDN delivery, image optimization, and critical CSS generation. Based on community reports, these issues are rarely a bug in the plugin itself but are almost always caused by a blockage or misconfiguration on the WordPress site.

Common Causes and Their Solutions

1. Firewall or Security Plugin Blocking Access

This is the most frequent cause. Security plugins like Wordfence or server-level firewalls can block the incoming requests from QUIC.cloud's network of service nodes.

How to fix it:

  • Whitelist QUIC.cloud IPs: The most effective solution is to whitelist the entire range of QUIC.cloud IP addresses in your firewall or security plugin. You will need to consult your hosting provider or firewall documentation for the specific steps, as this is often done at the server level.
  • Temporarily Disable Security Plugins: As a quick test, temporarily disable your security plugin (e.g., Wordfence) and attempt to connect to QUIC.cloud again. If it works, you've confirmed the plugin is the culprit, and you must configure its whitelist rules.

2. REST API Accessibility Issues

For the connection to work, QUIC.cloud's nodes must be able to access your site's WordPress REST API (https://yourdomain.com/wp-json/). Many things can block this.

How to fix it:

  • Check for Under Construction Modes: If your site is in a "coming soon" or "under construction" mode, it will likely block all external API requests. Disable this mode before setting up QUIC.cloud.
  • Verify Permalinks: Ensure your permalinks are working correctly. Sometimes, resetting them (saving them again under Settings > Permalinks) can resolve REST API issues.
  • Check for Other Blockers: Other plugins that manage access or restructure URLs (like WP Hide & Security Enhancer) can interfere. Test with these plugins disabled.

3. DNS and Domain Configuration Problems

Sometimes, the issue is related to how your domain is configured and recognized by the QUIC.cloud system.

How to fix it:

  • Use the Correct Domain: Ensure the domain you are linking in the LiteSpeed Cache settings exactly matches the domain your site uses (including or excluding 'www').
  • Check QUIC.cloud Dashboard: Often, the error message in the WordPress plugin is a red herring. Log into your QUIC.cloud dashboard directly. Many users find that their CDN is actually enabled and working there despite the "paused" status in WordPress, a known UI bug that has been addressed in recent updates.
  • Re-save Settings: A simple but effective step is to go to LiteSpeed Cache > CDN > QUIC.cloud, click "Save Changes," and then run the setup again.

4. Plugin or Cache Corruption

In some cases, the stored data for the plugin connection can become corrupted.

How to fix it:

  • Generate a Report: From the LiteSpeed Cache > Toolbox > Report tab, generate a report ID. This can help in diagnosing the issue.
  • Disconnect and Reconnect: In the QUIC.cloud dashboard, you can try removing your domain and then re-adding it. Back in WordPress, use the "Release" button to disconnect the site and then go through the linking process again.

Need More Help?

If you've worked through these steps and are still encountering problems, the best course of action is to generate a detailed report from the LiteSpeed Cache plugin's Toolbox and seek advice from the wider community in support forums. When asking for help, be sure to include your report number and a clear description of the steps you've already taken.

Related Support Threads Support