Current Cloudflare users can try QUIC.cloud CDN with no risk, and without the hassle of changing their DNS setup using the Cloudflare Integration option.
CDN Onboarding for Cloudflare users consists of four steps:
- Pairing WordPress and QUIC.cloud
- Creating a QUIC.cloud Account
- Adding your assigned QUIC.cloud CNAME to Cloudflare DNS
- Enabling the CDN
The Cloudflare Integration feature combines the last two steps to simplify setup for those who are coming over from Cloudflare.
Pairing WordPress and QUIC.cloud
Log into the 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.
You will see a notification at the top of the page, indicating that the application was successful. Wait a few minutes and then refresh the page. The Domain Key setting will have been automatically updated with the new key.
(See Pairing WordPress and QUIC.cloud if you need more information about this step.)
Creating a QUIC.cloud Account
You should still be in the LiteSpeed Cache for WordPress General section from the previous step. If you are not, please navigate there now.
To register your QUIC.cloud account, click the Link to QUIC.cloud button.
You will be redirected to QUIC.cloud to register.
Choose a password, agree to the QUIC.cloud terms and conditions, and click Register.
Check your email for a validation message from QUIC.cloud, and confirm your account by clicking the activation link within.
(See Creating a QUIC.cloud Account if you need more information about this step.)
On your QUIC.cloud Dashboard, click the name of your domain to be brought to a Services Overview. Click CDN. Click the Enable CDN button to begin the simplified setup for Cloudflare users.
You’ll be asked what method you want to use for enabling the CDN. Choose the third option:
I'm switching from Cloudflare, but I want to continue using it for DNS
Next, you’ll be asked how you wish to integrate with Cloudflare. Choose the first option:
I want to use Cloudflare Integration
Enter your Cloudflare API Token, which you can generate from your Cloudflare dashboard under My Profile > API Tokens . Please make sure that the token has
Edit DNS Zone permission. (See Cloudflare’s documentation for more information.)
Click the Continue button.
With the help of your Cloudflare API token, we can take care of several configuration steps on your behalf.
- We’ll use your API token to back up the existing DNS
Arecords for the domains that are using QUIC.cloud CDN; then we will insert the QUIC.cloud
CNAMErecord, so you don’t have to do it manually.
- We’ll use Certbot with DNS verification to generate a wildcard SSL certificate, using the API token to create the
TXTrecord Certbot requires.
- We’ll turn on the CDN, and use your API token to point the newly added
CNAMErecord to a CDN edge node.
Once these steps are completed, you will be up and running with QUIC.cloud CDN. Congratulations! If you’d like to verify that QUIC.cloud is active on your domain, please see Verifying the CDN is Working.
Please note: If you look at your Cloudflare DNS after QUIC.cloud setup is complete, you may see
A records and
CNAME records with the
qcbackup prefix. Do not delete these records! They are maintained by Cloudflare Integration. We keep these records so that we may properly restore your original settings, if necessary.
What are the benefits of Cloudflare Integration?
The two biggest benefits are ease of setup, and immediate SSL coverage for your domain.
Ease of setup: When you enable Cloudflare Integration, your Cloudflare API token allows QUIC.cloud to automatically take care of any required DNS maintenance on your behalf. You can confidently set it and forget it.
Immediate SSL coverage: When you set up QUIC.cloud CDN manually, you must point your DNS to QUIC.cloud before we can generate the SSL certificate. This potentially leads to a short period of time where your domain does not have a valid SSL certificate. However, with Cloudflare Integration, the API token allows us to generate an SSL certificate before we point the DNS to QUIC.cloud. This means, there is no gap in SSL coverage for your domain.
What if I want to stop using QUIC.cloud CDN?
If you decide that QUIC.cloud CDN is not for you, simply click the Disable CDN link on the CDN Config page on your Dashboard.
All of the changes that QUIC.cloud made to your DNS configuration using your Cloudflare API token will automatically be reversed. We’ll remove the
CNAME record we added and restore your backed-up
A records. Your DNS setup will go back to what it was before QUIC.cloud.
Can I temporarily bypass the CDN?
Sure. If you want to turn off QUIC.cloud CDN on a temporary basis, visit the CDN Config section of your Dashboard and set Bypass CDN to
ON. This has no impact on your DNS records.
To resume using the CDN, set Bypass CDN back to
Do you need my API token after setup is complete
Yes. We use the API token to renew your wildcard SSL certificate when it expires.
And if you toggle the Map Both www/non-www setting, we use the API token to automatically add or remove the appropriate
CNAME record in your Cloudflare DNS.
Can I turn off Cloudflare Integration
Sure. In the CDN Config area of your Dashboard, navigate to the Cloudflare section. There you can set Cloudflare Integration to
This does not disable the CDN, nor does it change your DNS configuration. This just means that QUIC.cloud is no longer in charge of maintaining your DNS
CNAME record, or generating the SSL certificates for your domain. If your domain requires DNS changes you will need to handle it manually, unless you turn Cloudflare Integration back on.
Can I use domain aliases with Cloudflare Integration?
It depends. If the alias belongs to the same DNS zone as the main domain, then yes. When you add the domain alias, Cloudflare Integration will automatically add the appropriate
However, if there are multiple DNS zones involved, it is not possible to use Cloudflare Integration. When you add the domain alias, Cloudflare Integration will be disabled, and you will be expected to manually set up the
CNAME for the domain alias.