Setting up the QUIC.cloud CDN on WordPress with LiteSpeed Cache

QUIC.cloud can serve static resources and compatible WordPress pages from its CDN network, working together with LiteSpeed Cache. How useful it is depends on where your visitors are, what content can be cached and the cost of the service.

Connecting the QUIC.cloud services and activating its CDN are separate steps. You can use optimisation services without moving the website's traffic to the CDN.

Before you start

Update WordPress and LiteSpeed Cache with a recoverable backup. Check that the website works over HTTPS on the hosting and note its origin IP, the main domain and the current DNS records. Keep access to the DNS provider and the registrar.

On a shop, identify the cart, checkout, account and personalised content. The integration is no reason to force public caching for every page or for every logged-in user.

Connect WordPress to QUIC.cloud

1. In WordPress, open LiteSpeed Cache > General > Online Services.
2. Click Enable QUIC.cloud services and follow the wizard to link the domain to your QUIC.cloud account.
3. Check that the correct domain has been linked, including its variant with or without www.
4. If you want to distribute the traffic, continue with activating the CDN. If you were only after image or CSS optimisation, do not change the DNS for that reason.

Older guides showed Request Domain Key. The current procedure starts in online services; see the official onboarding wizard if your screen looks different.

Choose how to connect the domain

The wizard offers alternatives depending on the domain and the DNS provider. Do not copy a CNAME target from another installation: use the one assigned to your website.

Keep your DNS provider

For a subdomain such as www.tudominio.com, set up the CNAME that QUIC.cloud provides at the authoritative DNS provider. That will be the cPanel Zone Editor only if the zone the domain uses is managed there.

On the root domain, an ordinary CNAME cannot coexist with the other records you need. Some providers allow an equivalent solution through CNAME flattening. Check the DNS method compatibility before changing it.

If you use Cloudflare for DNS, follow QUIC.cloud's specific integration. Do not chain two proxies by turning on options at both providers without checking that this setup is supported.

Use the QUIC.cloud DNS

Before changing the domain's DNS servers, reproduce the complete zone in QUIC.cloud. Automatic detection may miss records.

Compare the website and subdomains, MX, mail server addresses, SPF, DKIM, DMARC, verifications and CAA. Email must keep pointing to its service, not to the web CDN. If you have DNSSEC, also coordinate the change of signatures and DS records with the providers; a delegation with an incorrect DS can leave the domain unresolvable.

Then replace the DNS servers with the ones assigned to the domain. Keep the previous zone during the transition and check propagation; the time depends on DNS caches, not on a fixed period in this guide.

Check the go-live

Check in QUIC.cloud that the domain, its origin and HTTPS are correct. Open the website from a private session and check several public pages, resources, a form and, if relevant, the checkout process without making a real payment.

Check email and subdomains too. If something fails after changing DNS, first compare the zone and the origin IP; do not turn off the server's protections blindly.

An error about access to the REST endpoints may be caused by restrictions in the application or the firewall. Compare against the IPs and communication requirements published by QUIC.cloud and give support the domain, the time and the error, without sharing keys.

Purges, usage and going back to the origin

After changing a template or content, you may need to purge the plugin's cache and the CDN's. Start with the affected pages: a full purge forces many responses to be generated again and can temporarily increase the load on the hosting.

Review the current tiers, quota, credit and conditions in the panel before activating paid services. Measure usage and response times from the regions where your visitors are; do not choose a tier just by the number of locations advertised.

If you decide to remove the CDN, first prepare the records that will send the website back to the hosting and verify the origin's certificate. If you changed the DNS servers, also reproduce the whole zone at the destination provider. Keep the CDN running during the transition so visitors with old DNS are not left without service.