Onboarding

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

QUIC.cloud CDN, 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 CDN, 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!

Also, new to QUIC.cloud is image optimization, critical CSS, and LQIP. With these new services readily available, QUIC.cloud is more customizable and efficient than ever before.

After reading through this guide, if there is something you do not understand, please let us know by sending an email to support[at]quic.cloud.

Prerequisites

-Before you can use QUIC.cloud, you must update your LiteSpeed Cache for WordPress plugin to at least v3.0.

-Ths guide also assumes you already have a domain setup with WordPress. If you do not yet, please check out WordPress’ Domains guide.

Pairing WordPress and QUIC.cloud

To pair WordPress with QUIC.cloud, you will initiate the process in WordPress, move over to QUIC.cloud to set up your account there, go back to WordPress to verify your connection, and then visit QUIC.cloud to finish up. It's easier than it sounds.

Initiate in WordPress

To begin, sign into your WordPress dashboard for the domain you’d like to use with QUIC.cloud.

Navigate to LiteSpeed Cache > General, and click the Request Domain Key button, on the right side of the Domain Key box.

!General

You will see a notification at the top indicating that the application was successful, and to wait for the result. Refresh the page.The Domain Key setting should have been automatically updated with the new key. Click the Link to QUIC.cloud button to register your account with QUIC.cloud and set up the CDN.

!Auto-filled Domain Key

You will be redirected to QUIC.cloud to sign in or sign up.

!QUIC.cloud Login

Enter your email address. If you already have an account, you will be signed in. The connection will be complete, and you will be redirected back to your WordPress dashboard. Skip the next section, and go directly to Verify Connection in WordPress.

Set up QUIC.cloud

If you need to sign up for a QUIC.cloud account, you will be asked to choose a password and to agree to the QUIC.cloud terms and conditions. Do so, and click Register.

!Create Account

You will be sent a validation email. Check your email for a message from QUIC.cloud, and confirm your account by clicking the activation link.

!Activation Complete

QUIC.cloud setup is complete. Click My Dashboard to be redirected back to WordPress.

Verify Connection in WordPress

Back in WordPress, on the LiteSpeed Cache > General page, you will see a Visit my Dashboard on QUIC.cloud button that will allow you to easily access your QUIC.cloud dashboard at any time. Press the button.

!Visit Dashboard

Finish up in QUIC.cloud

Once on the QUIC.cloud dashboard, you will see the new domain listed.

!Added Domain

When you click into the domain, you should see a list of services offered, including the CDN.

If you’d like to use the CDN, please continue on to the next section of this document. If you are not interested in using the CDN, however, then you have successfully finished your setup. Congratulations and welcome to QUIC.cloud!

Setting up the CDN

Before a domain can use QUIC.cloud CDN, the DNS for that domain must be properly set up. Please follow the instructions below to set up your DNS.

DNS Setup

If you are not sure about how the DNS works, check out our DNS Primer. You will need to be logged into your WordPress admin and your DNS management page.

Tip

The base domain, e.g. example.com is known as the Root or Apex Domain. All other usages of this domain such as sub.example.com or www.example.com are subdomains.

If you are adding the root domain to QUIC.cloud, refer to the following section. If you are adding a subdomain, refer to the subsequent section.

Adding the Root(Apex) Domain

QUIC.cloud requires that your DNS maps your domain to a domain provided during setup. This means that your DNS provider must support domain to domain mapping for the Root domain.

Warning

This is not a standard feature. If you are unable to set up your DNS in this manner, you must switch to a DNS provider that is capable of this feature or you must reconfigure your WordPress' primary accessor to use www., e.g. www.example.com and follow the subdomain instructions. We are working to provide a better option, but that is a limitation of QUIC.cloud. An example DNS that is capable of this feature is CloudFlare's DNS.

The following instructions have screenshots from the CloudFlare DNS manager.

  1. Take a screenshot of your current configurations. Keep this as a reference in case things go wrong, so you have something to go back to.
  2. 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.
  3. (Optional) If you wish to use both the root domain and the www. subdomain: Create a CNAME record pointing www. to your Root domain:

!CF CNAME Update

If you have a www. record already, edit that to look like the above screenshot. The net result is that www.example.com will target the same server as example.com. 4. Create an A record for a random subdomain that points to your origin IP. For example, origin.example.com.

!CF A Rand

  1. Convert your current record for @ to a CNAME record targeting the subdomain you created in step 4.

Deleting the root domain record:

Tip

The below screenshots are for deleting an A record and adding a CNAME record. If your current record is a CNAME record or your DNS Manager allows changing record types, you can just edit the record.

!CF Del Root

Setting the CNAME record for the root domain:

!CF CNAME Root

  1. Make sure that your site is still accessible as is. Here are some ways to test.

Tip

If you are using CloudFlare DNS, ensure that the cloud is set to "Grey" (this means you are not actually using Cloudflare for anything other than the DNS).

After performing the above steps, the following should be true: * Your site is still accessible. Nothing should have changed. * If you performed step 3, your www. subdomain should also point to your current IP. Refer to how to check the DNS. * The random subdomain should also target the same IP.

!CF Prepared

If any of the above are not true, review your DNS configurations and run through the steps again. One possible reason that the above are not true is that the TTL for the old configuration has not expired yet. Make sure that the time has elapsed.

Adding the Subdomain

The following instructions have screenshots from the Digital Ocean DNS manager. The steps should be similar for your DNS provider.

  1. Take a screenshot of your current configurations. Keep this as a reference in case things go wrong, so you have something to go back to.
  2. 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.
  3. If the subdomain points to the same origin server as the Root domain, this step is not required. Create an A record for a random subdomain that points to your origin IP. For example, origin.example.com.

!Do A Rand

  1. Convert your current record for the subdomain to a CNAME record targeting the subdomain you created in step 3. If you are using the root domain as the base, target that instead.

    The below screenshots are for deleting an A record and adding a CNAME record. If your current record is a CNAME record or your DNS Manager allows changing record types, you can just edit the record.

Deleting the old record:

!Do Del Sub

Adding the new record:

!Do CNAME Sub

  1. Make sure that your site is still accessible as is. Here are some ways to test. If you are using CloudFlare DNS, ensure that the cloud is set to "Grey" (this means you are not actually using Cloudflare for anything other than the DNS).

After performing the above steps, the following should be true: * Your site is still accessible. Nothing should have changed. * The random subdomain should also target the same IP.

!Do Prepared

If either of the above are not true, review your DNS configurations and run through the steps again. One possible reason that the above are not true is that the TTL for the old configuration has not expired yet. Make sure that the time has elapsed.

Enable CDN

When on your QUIC.cloud dashboard, click on the domain you’d like to enable the QUIC.cloud CDN service for.

Note

Domains can be listed in QUIC.cloud and use the QUIC.cloud services, without using the CDN.

Next, under the services list, click ‘CDN’.

Note

If the status of the CDN says ‘OK’, then your CDN is already enabled for that site and you do not need to continue with this guide.

On the following screen, click ‘Enable CDN’.

Next we will discuss the DNS records and verification.

Configure DNS Records and Verify

Update the DNS Manager

Note the CNAME record that we created for you, as below:

!Update CNAME Record

In your DNS Manager, change the CNAME you set up to point to this CNAME domain.

Digital Ocean DNS Example:

!Do CNAME Update

CloudFlare DNS Example:

!CF CNAME Update

At this point, nothing should have changed. Your site should still target your server. Here are some ways to test.

Configure Access for your site (Optional)

On the “CDN” page, under “Setting” -> “Connection”, there are three options that configure how the browser connects to QUIC.cloud and how QUIC.cloud connects to your origin server. Select the appropriate option.

!Connection Options

Connection Type to Origin: This option specifies the connection type between QUIC.cloud and your origin server. The available options are: match the connection type from the browser to QUIC.cloud or use HTTP Only.

Frontend Force HTTPS: This option specifies the connection type between the browser and QUIC.cloud servers. If set to ON, HTTP requests to QUIC.cloud are redirected to HTTPS automatically. Otherwise, both request types are forwarded to your backend server (depending on how Connection Type to Origin is configured).

Enable QUIC Backend: If your site offers QUIC and/or HTTP/3, you can try this option. This will let QUIC.cloud servers attempt to connect to your origin server using QUIC and/or HTTP/3.

Configure your Firewall

When your site goes through QUIC.cloud servers, all the requests will appear via QUIC.cloud IPs. This will likely trigger some firewall rules. Make sure to whitelist QUIC.cloud IPs so that the requests do not trigger the firewall.

Verify Your Website is Using QUIC

You must have a valid SSL Certificate set up on QUIC.cloud to use QUIC.

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

!Chrome QUIC Verify

Alternatively, you could use HTTP/3 Check to test it out.

That’s it. QUIC.cloud CDN should now be set up. If you have any questions or issues, please contact us at support[at]quic.cloud.


Last update: July 2, 2020