Fix “Domain Key is invalid” in LiteSpeed Cache (QUIC.cloud)

If you are wondering what is broken: your page cache is usually fine. It is the link between LiteSpeed Cache and QUIC.cloud that is failing. QUIC.cloud is rejecting the domain key your plugin is sending.

Why this error shows up

The domain key is a small token that:

• Proves “this WordPress site really owns this domain” to QUIC.cloud.
• Allows QUIC.cloud to attach usage, quotas, and services to your site.

“Domain Key is invalid” means QUIC.cloud does not accept the key stored in your plugin. Common reasons:

• You changed domain, protocol, or moved to staging and the key no longer matches.
• You reset or reinstalled LiteSpeed Cache and the old key is still registered at QUIC.cloud.
• QUIC.cloud’s callback to your site /wp-json/litespeed/v1/token is blocked by a firewall, security plugin, or disabled REST API.
• You are behind Cloudflare or another proxy and the Server IP is wrong, so IP checks fail.
• You are on LiteSpeed Cache v7 or later, where the old “Domain Key” field is deprecated and the integration needs to be re linked.

Step 1: Quick reset from LiteSpeed Cache

Start with the fastest fix. Often you just need to re link the site so a new key is issued.

1.1 If you are on LiteSpeed Cache v7 or later

1. In WordPress, go to LiteSpeed Cache → General → Online Services.
2. If you see that QUIC.cloud is linked, click the option to Disconnect or disable QUIC.cloud services.
3. Save changes.
4. Click Enable QUIC.cloud services again and follow the prompts to:
   • Log in to your QUIC.cloud account, or
   • Continue anonymously if you are not using the CDN account features.

This process requests a fresh token from QUIC.cloud and stores the new domain key automatically.

1.2 If you are on an older LiteSpeed Cache version with a “Domain Key” field

1. Go to LiteSpeed Cache → General.
2. Under Domain Key, click Request Domain Key.
3. Wait until you see the message that the key has been approved, then refresh the page.
4. Confirm the field is now filled with a key string (not empty).
5. Click Link to QUIC.cloud if that button is present and complete the link.

If “Domain Key is invalid” disappears after this, you are done. If it comes back or the request never completes, move on.

Step 2: If you changed domain, URL, or cloned the site

This error is very common after:

• Changing from http:// to https://.
• Switching between www.example.com and example.com.
• Cloning live to staging or moving to a new domain.

QUIC.cloud expects the domain in your WordPress and in your QUIC.cloud dashboard to match.

2.1 Check your WordPress URLs

1. In WordPress, go to Settings → General.
2. Confirm WordPress Address (URL) and Site Address (URL) match the exact domain you want to use (including https:// and www vs non www).
3. Fix them if needed, then save.

2.2 Check your domain in QUIC.cloud

1. Log in to your QUIC.cloud dashboard at my.quic.cloud.
2. On the Domains or Sites page, find your domain.
3. Confirm the domain there matches what you just saw in WordPress (no typos, correct protocol, correct main domain vs dev subdomain).

If you see multiple entries for the same site, or the wrong domain is listed:

• Remove or disable the old or incorrect domain entries.
• Back in WordPress, disconnect and re enable QUIC.cloud services so the correct site is linked.

After that, reload LiteSpeed Cache settings. If “Domain Key is invalid” came from a simple mismatch, it should clear now.

Step 3: Fix REST API and callback issues

If QUIC.cloud cannot call back to your site to validate the key, it will treat the key as invalid or never approve it.

3.1 Make sure the REST API is reachable

1. Open a private browser window.
2. Visit:https://your-site.com/wp-json/
3. You should see a JSON index, not a 403, 404, or “REST API disabled” message.
4. Then visit:https://your-site.com/wp-json/litespeed/v1/token
5. You should see a small JSON response. If you get a 403, 404, or some security splash, QUIC.cloud cannot validate the domain key.

3.2 Temporarily disable anything that blocks the REST API

• Deactivate security plugins that block REST API access or “hide” wp-json.
• Check firewall or WAF rules (including Cloudflare Page Rules or WAF rules) that might block /wp-json/ or /wp-json/litespeed/v1/token.

After adjusting, reload the two URLs above in a private window. Once they return OK, go back and repeat the quick reset in Step 1 so a new key can be issued and validated.

Step 4: Allowlist QUIC.cloud and fix Server IP behind proxies

If your site is behind Cloudflare, Sucuri, or another reverse proxy, the plugin may see the proxy IP instead of the QUIC.cloud server IP and fail stricter checks.

4.1 Set the correct Server IP in LiteSpeed Cache

1. In WordPress, go to LiteSpeed Cache → General.
2. Find the Server IP field.
3. Enter your origin server’s public IP (not the Cloudflare IP). You can get this from your hosting control panel or host support.
4. Save changes.
5. Repeat the QUIC.cloud connect or domain key request process.

4.2 Allowlist QUIC.cloud IPs in firewalls

At any layer that filters by IP (host firewall, security appliance, web server rules), QUIC.cloud’s IPs must be allowed.

• Ask your host to allowlist all QUIC.cloud server IPs according to the official allowlist documentation.
• Make sure no “block unknown IPs” rule is catching QUIC.cloud requests.

Once allowlisted, try connecting again from LiteSpeed Cache → General → Online Services.

Step 5: Clean up old installs and staging sites

If you cloned your site or used the same domain key on:

• A staging or dev copy, or
• A previous install on another server,

QUIC.cloud may see conflicts and treat the key for that domain as invalid.

Do this:

1. Log in to my.quic.cloud.
2. Remove any old or unused entries for this domain or dev copies you no longer use.
3. On each live WordPress site that should use QUIC.cloud:
   • Disconnect QUIC.cloud from LiteSpeed Cache → General → Online Services.
   • Then re enable and link again so each site gets its own clean connection.

After cleanup, the “Domain Key is invalid” notice should disappear and quotas should attach to the correct domain.

If you cannot tell what is wrong

If you have tried the steps above and the error still shows, gather a bit more information so we can dig deeper.

Scroll down, click Continue Chat, and send me:

1. Your LiteSpeed Cache plugin version.
2. A screenshot of LiteSpeed Cache → General → Online Services (or the Domain Key section on older versions).
3. Whether you use Cloudflare or another CDN or proxy.
4. Whether any security or firewall plugins are active.
5. A copy of any LiteSpeed Cache or QUIC.cloud related messages from Tools → Site Health.

Verification

You know the problem is fixed when:

• No more “Domain Key is invalid” notice appears in LiteSpeed Cache.
• LiteSpeed Cache reports QUIC.cloud services as Enabled and linked for your domain.
• Image optimization, critical CSS, or CDN usage in the QUIC.cloud dashboard starts updating for your site.
• QUIC.cloud related tests in Site Health no longer show API or REST errors.

Still stuck?

For AI help

Hit Continue Chat below and I will walk you through your LiteSpeed Cache settings, REST API status, and QUIC.cloud dashboard until the domain key is valid again.

For expert human help

Scroll down to the contact form below. Enter your name, email, and WordPress needs. Atiba will get back to you as soon as possible.