QUIC.cloud Setup Guide for Beginners

Our complete, QUIC.cloud setup guide with step-by-step illustrations makes the whole process super simple for everyone.

Let’s get started!

QUIC.cloud Features

QUIC.cloud was launched in 2019 by the same team behind LiteSpeed Web Server and LiteSpeed Cache. As a result, it leverages more than 20 years of experience in performance optimization at both the server and application level.

Given its unique features, QUIC.cloud was the first CDN to give a serious challenge to Cloudflare’s dominance.

In a nutshell, QUIC.cloud features:

1. caching for both static and dynamic WordPress content.
2. end-to-end HTTP/3 (QUIC), the next-generation transfer protocol developed by Google.
3. Edge Side Includes (ESI) caching which allows very fine-grained caching control over cache expiry times for different blocks within pages and posts.
4. built-in WordPress brute force protection with a CDN-level reCAPTCHA.
5. layer 7 DDoS protection with Web Application Firewall (WAF) and advanced security options.

QUIC.cloud is the only CDN that caches both static and dynamic WordPress content. This makes it possible for QUIC.cloud to cache the entire WordPress website at the CDN level!

This greatly reduces the amount of requests to your server not only for static assets such as images, CSS, javascript, etc. but also for dynamic content as well such as customer shopping carts, inventory counts, user dashboards, etc.

This contrasts with other CDNs that typically only cache static content and may optionally include support for some dynamic caching.

Another neat thing about QUIC.cloud is that it integrates directly with LiteSpeed Cache for WordPress and the two work seamlessly together.

Once it is setup, QUIC.cloud is very easy to use and requires just basic technical know-how to configure.

QUIC.cloud vs. Cloudflare: What’s the Difference?

As mentioned, QUIC.cloud’s game-changing feature is that it caches both static and dynamic HTML content at the CDN level. This contrasts with Cloudflare, which caches only static content.

Cloudflare recognized the threat from QUIC.cloud’s dynamic caching and responded by launching it’s own dynamic caching for WordPress: Automatic Platform Optimization (APO).

APO caches both static and dynamic WordPress assets just like QUIC.cloud, but costs an additional $5/month if you’re using Cloudflare’s Free plan. If you’re using any of Cloudflare’s paid monthly plans, then APO is included free.
In brief, here’s how QUIC.cloud and Cloudflare compare:

As we can see, Cloudflare has a much larger global presence with 330 PoPs, which is more than 4x as many as QUIC.cloud’s 79 PoPs. As QUIC.cloud is a younger and smaller company, we should expect their number of PoPs to steadily increase over time.

QUIC.cloud supports true HTTP/3 (QUIC) end-to-end: from the client to QUIC.cloud CDN node to origin server. Cloudflare also supports HTTP/3, but this is only from the client to Cloudflare’s CDN node: the connection from Cloudflare’s CDN node to the origin server is downgraded to HTTP/2 or HTTP/1.1. Hence, Cloudflare supports HTTP/3 but this is not end-to-end.

However, Cloudflare does support Early Hints which QUIC.cloud lacks at the moment.

Another important feature to highlight is that Cloudflare’s DNS is the second fastest in the world. QUIC.cloud DNS uses Amazon’s Route 53, which although is fast overall, is still slower in speed compared to Cloudflare DNS.

Cloudflare also has other advanced features as well (both free and paid) such as Zero Trust, Argo Smart Routing and many more.

Overall, Cloudflare is a large, general cloud services provider whereas QUIC.cloud CDN is a more specialized, WordPress-specific solution that integrates tightly with LiteSpeed Cache.

QUIC.cloud Free Plan vs. Standard Plan

Perhaps the most confusing aspect of QUIC.cloud is the pricing. It has a Free Plan and a Standard Plan. After completing the setup, everyone is put on the Standard Plan by default.

The Free Plan is simple to use and has absolutely no costs at all; however, it is very limited.

Most notably, it has only 6 PoPs compared to 79 PoPs for the Standard Plan. It also has fewer security features and no traffic management.

The Standard Plan includes all features and is a prepaid service. However, the Standard Plan also comes with a free monthly quota for bandwidth and image/page optimization services.

How much free monthly quota you get depends on your web host. Basically, LiteSpeed Enterprise hosts get $0.20 of free monthly bandwidth quota, LiteSpeed hosts get $0.10 and non-LiteSpeed hosts get $0.02. Likewise, you also get a free monthly image/page optimization quota.

Depending on where the traffic is served from, the price (per gigabyte) varies from $0.02 (North America and Europe), $0.04 (Russia) or $0.08 (Asia, Middle East, Africa and Oceania).

Hence, you can use QUIC.cloud Standard for free as long as you stay within your free monthly quota. As your website expands and you need more bandwidth (or more image/page optimzation), you can simply purchase more.

You can find complete details about QUIC.cloud’s plans and pricing here.

The Best of Both Worlds: Cloudflare DNS + QUIC.cloud CDN

Using QUIC.cloud requires you to make changes to your DNS records: you have a choice if you want to use Cloudflare’s DNS, QUIC.cloud DNS or continue using your existing DNS provider.

As we discussed above, Cloudflare’s DNS is actually faster than QUIC.cloud’s DNS. However, QUIC.cloud CDN is a better fit overall for WordPress-specific websites compared to Cloudflare CDN.

Is it possible to use Cloudflare’s DNS together with QUIC.cloud CDN?

Indeed, it is and this is exactly the setup we use here at WPNexus and what we recommend for our readers. This approach requires a little bit more setup, but you only need to do it once.

If you’re already using Cloudflare, then you’re ready to proceed with this approach.

See Also

• • CDN Guides

Cloudflare Setup Guide for Beginners

• Ravi Singh
• September 2, 2025

If you’re not and you want to use Cloudflare’s DNS, then we recommend completing our Cloudflare Setup Guide for Beginners before proceeding with QUIC.cloud setup below for the maximum speed benefit.

If you want to just use QUIC.cloud’s DNS (this is the easiest method) or continue with your existing DNS provider, then you can proceed straight to the setup guide below.

Our setup guide has detailed step-by-step instructions with illustrations whether you decide to use Cloudflare’s DNS or QUIC.cloud DNS.

Setup Guide

Create and Setup Your QUIC.cloud Account

The first step is to go to the QUIC.cloud website and go to the Register button in the top-right corner.

Next, enter your email, create a strong password, agree to QUIC.cloud’s terms of service and then Register.

You’ll be sent a verification email with an activation link. Once verified, you’ll be presented with the following screen confirming that your account has been activated.

Connect Your WordPress Site to QUIC.cloud

Now we need to connect LiteSpeed Cache within our WordPress website to QUIC.cloud.

Go back to your WordPress admin dashboard and in the LiteSpeed Cache General tab, go to “Enable QUIC.cloud services.”

You’ll be taken back to QUIC.cloud’s website and asked to confirm that you want to connect your WordPress website domain to QUIC.cloud.

Select Yes and then Continue.

You will then see a screen confirming that your domain has been successfully connected to your QUIC.cloud account.

Now, we need to enable the CDN on QUIC.cloud by selecting Enable CDN.

QUIC.cloud will then ask you to enter your server’s IP address to start the process of enabling the CDN.

For cPanel based hosts, you can obtain this easily within the General Information panel on the right as shown.

For other hosts, your server IP address is usually available within the control panel for your website. If you can’t find it, contact your hosting company and they will provide it for you.

Copy the value for your server IP address and paste it into the Server IP field as shown. Then, continue with Update IP.

With this done, your server IP address has now been updated within QUIC.cloud.

Update DNS Records

As QUIC.cloud is a CDN, it acts as a proxy for all your incoming traffic. In order to act as a proxy, it must make changes to your DNS records for this to take affect.

Luckily, QUIC.cloud makes this process very easy by providing you with several choices on how you’d like to go about this.

You will be presented with three choices for which DNS service you’d like to connect with QUIC.cloud:

1. Use QUIC.cloud’s own DNS (easy)
2. Use CNAME
3. Use Cloudflare DNS (best)

Using QUIC.cloud DNS is the easiest to setup but the third method using Cloudflare DNS will give you the best speed results.

QUIC.cloud’s DNS is actually Amazon’s Route 53 which overall is quite fast, but still much slower than Cloudflare’s DNS. In fact, Cloudflare DNS is almost 3x faster than Amazon Route 53 DNS, which is why we prefer the third method.

The second CNAME method is used in all other cases and basically requires you to manually makes changes to your DNS records. Due to the technical requirements of this, it beyond the scope of this basic guide. We will add instructions for this in a future update.

We will present complete instructions for both the QUIC.cloud DNS method and Cloudflare DNS method.

Option 1: QUIC.cloud DNS (easy)

Select “I want to use QUIC.cloud DNS” and then Continue.

QUIC.cloud will automatically detect your existing DNS records and import them over. Usually, it will detect all of them as long as you’re not already using a proxy server (if you are, you should disable it first).

If for whatever reason it misses some records, you can manually add them back later.

Once you’ve reviewed the records, you can go to + Add DNS Zone.

You’ll be assigned two new QUIC.cloud nameservers which will replace your existing nameservers. You will need to go to your web host or your domain registrar (wherever you registered your domain) and replace your current nameservers with the new QUIC.cloud assigned nameservers.

For example, in Namecheap, you can find your domain in the Domain List tab. Then, select Custom DNS for your Nameservers and paste both QUIC.cloud assigned nameservers. Be sure to save your changes!

Now, all you have to do is wait for your DNS changes to propagate. This usually takes about 15 minutes, but can sometimes take longer.

With your DNS records updated, continue to Finish Setup in QUIC.cloud. You’ll be taken back to WordPress and shown a success screen.

You can now continue to Step 4 below.

Option 2: Cloudflare DNS (best)

Select the “I’m switching from Cloudflare, but I want to continue using it for DNS” option and then Continue.

You’ll be asked if you want to use QUIC.cloud’s Cloudflare integration or if you’d like to update Cloudflare DNS manually.

We highly recommend the first option as QUIC.cloud will automatically create backups of the necessary DNS records and create two new updated DNS records for you.

To use Cloudflare integration, we’ll need to create a API token from within Cloudflare.

Go to your Cloudflare account and in the top-right, select the drop-down and select “My profile”.

Next, select API Tokens from the panel on the left and then continue to the Create Token.

To simplify the process, we will create the token from a template. Go to the “Use template” button under “Edit zone DNS”.

We’ll need to grant QUIC.cloud permission to edit the DNS Zone. Under Permissions, select “Zone”, “DNS” and “Edit” as shown below.

Under “Zone Resources”, select “Include”.

If you’re connecting just one domain, select “Specific Zone” and then select your domain as shown below in the third drop-down menu. If you’re connecting multiple domains, you can simply select “All zones” or create separate, individual tokens for each specific zone.

Everything else you can leave as default.

With that complete, go to “Continue to summary”.

Cloudflare will show you a summary of the API Token it will generate. Continue to “Create Token”.

Your token will be generated by Cloudflare. Next, copy this token…

… and paste it into the QUIC.cloud “Cloudflare API Token” field. Continue to “Finish Setup” and you’ll be taken back to your WordPress website.

Back in WordPress, you’ll be presented with a success screen showing that QUIC.cloud has been successfully setup with your domain.

QUIC.cloud CDN Configuration and SSL Certificate Generation

Let’s  quickly review what we’ve done so far before we continue. We have:

1. Created our QUIC.cloud account.
2. Successfully connected QUIC.cloud to our WordPress website through LiteSpeed Cache.
3. Updated our DNS records to proxy our website through QUIC.cloud CDN.

We’re almost there!

Going back to QUIC.cloud, you’ll see your domain with it’s status shown as “Bypassed: DNS Not Verified”. All we need to do is verify our DNS and all the technical aspect of the setup will be done.

Select your domain as shown below.

Next, you’ll see that QUIC.cloud’s Image Optimization, Page Optimization and LQIP services are up and running, but the CDN is bypassed with missing SSL certificate.

This is because updates to DNS records take some time to propagate. Select CDN as shown below.

Select the “Verify DNS Now” button as shown below.

QUIC.cloud will show that the DNS verification is still in progress. This usually takes about 15 minutes, but sometimes it can take much longer.

All you have to do is click on “Refresh Status” every few minutes to see if the DNS has been verified, so just be patient.

When the DNS is successfully verified, you’ll see the screen below with “DNS Verified” in Status and the Verification Status as “DNS OK”.

With this done, continue to the “CDN Config” setting in the left panel.

Here, you’ll see that the DNS has been successfully verified, but the SSL Certificate is missing. Below that it will how much time it will take for the new SSL certificate to generate.

What’s happening behind the scenes is QUIC.cloud has provisioned Let’s Encrypt to generate the new SSL certificate.

This can take a few minutes so sit back, relax and enjoy a cup of coffee while we wait for this to be completed.

Phew! It’s finally done! We’ve successfully gone through all the technical hoops to get QUIC.cloud running with our website and the status of everything is good as shown below.

All we need to do now is go through the CDN config to apply some speed and security settings.

QUIC.cloud CDN Settings

Now let’s get on to the fun part!

QUIC.cloud CDN has many advanced performance optimization and security hardening settings within its easy to use interface.

I’ll briefly go through the important settings that I personally use which should be safe for most people.

Most of the settings are self-explanatory and I provide some details for specific settings. I will follow-up with a more detailed explanation for the settings in a future update.

As always, make sure you test thoroughly that everything is working fine.

Map Both www/non-www: ON

Auto Redirect www/non-www: ON

Connection Type to Origin: MATCH

Enable QUIC Backend: ON

Frontend Force HTTPS: ON

IPv6 on CDN Edges: ON

Allow Jetpack: OFF

Turn ON only if you are using Jetpack.

Block WP API User List: ON

Block WP API Embed: ON

Block WLWManifest: ON

Block Author Scan: ON

reCAPTCHA & WP Brute Force Defense: ON

For this setting to properly work, your WordPress login URL must be the default, for example mywebsite.com/wp-admin. If you’re using any custom login URL, then QUIC.cloud’s brute force login protection won’t work.

QUIC.cloud’s brute force login protection works only if your admin login URL is the default.

Max Login Attempts: 0

This is to set how many login attempts someone is allowed before the reCAPTCHA is invoked.

I recommend setting this to 0 (zero) as it will force everyone trying to login to the WordPress backend to complete a reCAPTCHA. This will filter out bad bots and malicious traffic.

URL Flood Protection: ON

Block Brute Force by IP: ON

Restrict XML-RPC requests: ON

Block Browser XML-RPC: ON

Hotlink Protection: ON

Max Tries: 3

This is to set the maximum amount of tries for someone to pass the reCAPTCHA. If they fail all tries, their IP will be blocked for 5 minutes.

I recommend keeping this at the default 3 setting.

Be sure to save your reCAPTCHA settings by clicking the “Save reCAPTCHA Settings” button.

Cloudflare Integration: ON

This setting will automatically be on if you’re using Cloudflare integration.

Maintenance Mode: OFF

This setting is very useful when you need to temporarily make your site unavailable for maintenance.

It’ll show a QUIC.cloud “Under Maintenance” screen to everyone except for IP addresses in the “Maintenance IP Allowlist” below. Be sure to add your current IP address as shown and then “Save IP Lists”.

Be sure to toggle it OFF once you’re done your maintenance.

That’s it!

With all this completed, you’re WordPress website is now being served through QUIC.cloud CDN 🙂