Onboarding

Litespeed's QUIC.cloud CDN is a new way to supercharge your website.

QUIC.cloud, with an intelligent cache CDN based on LiteSpeed Cache, is the only CDN service that can accurately cache dynamic pages (pages that can change frequently). LSCache for WordPress knows when to automatically purge and sync data in QUIC.cloud, giving it the upper-hand on all other CDN providers. Users can now provide anyone across the globe access to their sites in less than 100ms!

After reading through this tutorial, if there is something you do not understand, please let us know by sending email to support[at]litespeedtech.com.

Preparation

You will need to be logged into your WordPress admin and your DNS management page. Check what your TTL value is and adjust it to the smallest value possible (if not already). You will need to wait until the old DNS records expire before you can use QUIC.cloud. After the old value expires, every record should be using the new value. Example: previous value: 1 hour, new value: 2 minutes. If it is 3pm when you change the value to 2 minutes, you must wait until 4pm to be sure that all the records now use the 2 minute value.

Step 1: Register

You need to register an account to access the service. This is a one-time process, and you can add multiple domains inside the same account. Register here.

Enter your desired Email address and Password.

Check your email for a message from QUIC.cloud and confirm your account.

Proceed to the login page, enter your email and password to log in and access your Dashboard.

Step 2: Add Your Domain to QUIC.cloud

Click on the Add Domain button within the Domains section of the Dashboard and enter your domain name.

Next, you'll see some domain-specific settings to configure, like so:

Server IP: Enter your origin server IP here in this field (i.e. the actual IP address on which the website is hosted). If you're unsure which IP that is, please consult with your hosting provier.

SSL: This option defines the level of encryption your website will have. There are three options:

  • Both - If you want to use your website with both HTTP and HTTPS, choose this.
  • Yes - This will redirect all HTTP requests to your domain to HTTPS. It will connect to your server using HTTPS, and also only serve your website through HTTPS. This is recommended.
  • No - This will also redirect your HTTP requests to HTTPS on your domain, but will connect to your server using HTTP. You can use this if your domain has no HTTPS on the origin server.

Auto Certificate: This option defines if your want Litespeed to handle your Certificate via Lets Encrypt.

  • OFF - This will allow you to use your own certificate, If you select this you will have the option to enter your Certificate and Key files.
  • ON - If you select this, the CDN will automatically manage the certificate for you and will use Letsencrypt to issue certificates. Renewal is also handled automatically.

Next, You will be given a CNAME subdomain where you will point your domain.

Step 3: Configure DNS Records and Verify

Configure your domain's CNAME DNS record as follows:

  • Host - @ or www (This depends on what you use for your domain by default.)
  • TTL - The smallest value possible (This should have already been changed to the smallest value in the preparation step.)
  • Record - XX.quic.cloud (This is the subdomain you've recieved from QUIC.cloud during the domain-add process.)

Tip

If you use a domain without "www" by default, aka the root domain, you might have problems adding a CNAME record in many DNS Providers. Until we have a better solution for this, you can use Cloudflare to manage your DNS. This allows a CNAME to be added to the root domain. Just ensure that the cloud is set to "Grey" (i.e. you are not actually using Cloudflare for anything other than the DNS).

Once this setup is done you can go to Dashboard > Domain Management > Verify the Domain.

You can revert to the old value of the TTL now if you want, but it is unnecessary.

After the verification succeeds, click on the Generate Cert Button below to Generate a certificate for your domain.

Tip

If you are using a root domain for your website and you used Cloudflare to setup your DNS CNAME as defined in the previous tip, you might get a CNAME not Parsed error while attempting to verify. This does not in any way hamper the working of your website! Cloudflare does CNAME Flattening for root domains, hence it is shown as an A record to the world. This is why our verification button fails. To verify that your domain is actually pointed properly, ping your domain using the default www or non-www as appropriate, and ping the CNAME record QUIC Cloud has given to you. If both point to the same IP, then you are good to go. Do not worry if CNAME does not appear verified on the dashboard. Proceed with the Generate Cert button as normal, and feel free to ignore the CNAME Verification process.

Tip

The Generate Cert step will not be needed if you've set Auto Certificate to OFF during the domain addition process, and have configured your own SSL Certificate on the CDN.

Step 4: Manage Settings

This page allows you to manage your domain settings on the CDN.

Click the Edit button.

We already set Server IP, SSL and Autocert in Step 2. You can modify them here, if necessary.

The new option, Recaptcha Defence, allows your website to be protected by implementing ReCAPTCHA site-wide in case of a DoS attack. Turn this on if your website is under attack.

Configure QUIC Cloud API for Wordpress Users

One of the very special features of this CDN is that it allows full-page caching with support for automatic purge on CDN via the LiteSpeed Cache Plugin for WordPress. This step is strongly recommended for all WordPress, WooCommerce and bbpress users.

To use this functionality, you first need to generate an API Key: Go back to your QUIC.cloud Dashboard, and click on the option Generate API Key.

Tip

Do not share your API key with anyone else! Treat it like a password.

Once the API key is generated, Go to your Wordpress Admin Dashboard, and navigate to Litespeed Cache > Settings > CDN.

Tip

If you don't see a CDN tab on your Settings screen, click the Show Advanced Options button to the right of the visible tabs, and it should appear.

Set QUIC Cloud API to ON. (If you don't see that option, make sure you have updated LSCWP to at least version 2.9.7.)

Enter your QUIC.cloud Email Address and User API Key, and click Save.

QUIC.cloud CDN and LiteSpeed Cache for WordPress are now integrated for your site.

Verify Your Website is Using QUIC

You must have a valid SSL Certificate to use QUIC.

If QUIC.cloud is working properly, your site should be using QUIC. You can use a browser extenstion to verify this, such as this for Google Chrome. It will show a Green lightning bolt indicator, if your website is using QUIC.

Frequently Asked Questions

How do I verify my DNS setting is correct if the Verify button fails?

Even if the Verify button fails, your site may still be set up properly. Here are two ways to check:

  1. The simplest way to check your DNS setting is to ping your domain and see if the IP address matches the IP of the CDN node. Ping your domain from the Windows command line or Linux SSH terminal against the CNAME record assigned to your domain (e.g. c123.tier4.quic.cloud)
  2. Use the online DNS checker tool. If you see different IPs listed globally, that means the site is on our CDN network.

If one of the above methods checks out, it's ok to ignore the results of the Verify button.

How do I handle an Invalid Error Certificate?

If you see an Invalid Certificate issue, go to the QUIC.cloud Domain Management page, and click Generate Certificate to set your certificate. If you are using your own SSL, Please ensure that it is valid.

My website isn't using QUIC, what should I do?

If you have verified your domain from inside the CDN's Domain Management Panel, it is mostly tha the DNS has not yet propagated. Wait a while and check again. If it's still not working, check if your browser has QUIC Support.

If you're unable to verify your domain, ensure that your DNS records are set correctly