Frequently Asked Questions

About QUIC.cloud CDN

General

What is QUIC.cloud?Link to question

QUIC.cloud CDN is a high-performance Content Delivery Network service created by the team at LiteSpeed Technologies. QUIC.cloud provides cutting-edge HTTP/3 support and important WordPress security features, and is the first and only CDN to partner with LiteSpeed Cache to deliver both static and dynamic WordPress content. QUIC.cloud is capable of serving tens of thousands of simultaneous requests, via a network of nodes distributed strategically around the world.

Which CMSs does QUIC.cloud support?Link to question

QUIC.cloud was built exclusively for WordPress sites and integrates seamlessly with the LiteSpeed Cache plugin for WordPress.

Can I host my website with QUIC.cloud?Link to question

No. QUIC.cloud provides CDN service and does not host your site. If you do not currently have a host for your website, you might like one of these LiteSpeed Partners.

How much free bandwidth does QUIC.cloud give me?Link to question

QUIC.cloud provides free bandwidth quota that resets every month. Beyond that, you are free to purchase additional bandwidth as necessary, without limit. The amount of free bandwidth your site receives is controlled by a Tier System, which depends on the site’s origin server. If you feel that your domain has been assigned an incorrect tier, please follow these steps to reassign it to the correct tier.

Is QUIC.cloud bandwidth calculated per domain or per server?Link to question

Bandwidth is calculated per domain.

Do I need to register on QUIC.cloud to use the CDN?Link to question

Yes. You must be registered at my.quic.cloud in order to use QUIC.cloud CDN.

What happens if I use more than the allotted data?Link to question

If you exceed your allotted free bandwidth quota before the end of the month (and you have not purchased PAYG quota), the CDN will be bypassed automatically and visitor requests will be directed to your domain’s origin server. When the quota refreshes at the beginning of the next month CDN service will be restored automatically.

To maintain uninterrupted service, you can purchase additional pay-as-you-go (PAYG) quota with credits. Learn more about credits in our Knowledgebase.

How does using QUIC.cloud speed up my site?Link to question

QUIC.cloud uses servers around the world to reduce the physical distance requests must travel. Additionally, QUIC.cloud can cache dynamic content at the CDN level, unlike other CDNs which must retrieve all dynamic requests from the origin server. CDN-level caching not only improves QUIC.cloud’s overall bandwidth speed, but it also minimizes the number of requests to the origin server.

What web servers are compatible with QUIC.cloud?Link to question

All web servers, including LiteSpeed Web Server, Apache, Nginx, and OpenLiteSpeed, are compatible with QUIC.cloud. QUIC.cloud acts as a CDN only and will not take the place of any web server.

Does QUIC.cloud offer any Anti-DDoS features?Link to question

Yes. The QUIC.cloud dashboard allows you to enable and configure reCAPTCHA & WordPress Brute Force Defense, and you may also restrict XML-RPC requests if you wish. Configurable allow and block lists are provided for access control.

While there are many WordPress plugins available to provide security features, nothing beats the efficiency and effectiveness of stopping attackers at the CDN level.

How many websites can each QUIC.cloud account support?Link to question

There is currently no limit to how many domains can be connected to each QUIC.cloud account.

I ordered credits, but I don't see them on my account. What should I do?Link to question

When you purchased credits, you should have received an Order is Complete email. Inside that email is a link to view the status of your credits. Click the link. If your credits look incorrect on that page, please save a screenshot, open a ticket, and share the screenshot with us so that we can look into the issue.

How do I get started using QUIC.cloud?Link to question

Our Onboarding Documentation should help you get started. If you have any questions after reading through the steps, feel free to contact us on Slack or open a ticket.

What’s the difference between QUIC and HTTP/3?Link to question

QUIC was originally a Google effort to improve HTTP/2 by transporting it encrypted over UDP (as opposed to TCP). In 2016, the Internet Engineering Task Force (IETF) began working to standardize the protocol. Part of that process involved splitting QUIC into the transport and application protocols. For some time, the application protocol was referred to as HTTP-over-QUIC, but in November of 2018, the IETF announced that HTTP-over-QUIC would be called HTTP/3.

Where can I learn about other QUIC.cloud services?Link to question

QUIC.cloud is more than a CDN. To learn about the other QUIC.cloud services (Image Optimization, Critical CSS Generation, and more), visit the Features section of our website. To get help with configuration, and learn some usage tips, please see the QUIC.cloud Knowledgebase.

PoPs and Nodes

What is a PoP?Link to question

PoP stands for “Points of Presence.” A PoP is a location, referenced by IP address, where we have a CDN node. Our PoPs are located around the world. See the CDN Global Coverage Map for more information.

Is there a list of current PoP IP addresses?Link to question

Yes. We maintain an IP list. You can use this list to populate your firewall’s allowlist, as some firewalls may block CDN IPs. This list is subject to change at any time without notice.

What should I do if the QUIC.cloud IP list changes?Link to question

You will need to make sure the QUIC.cloud IPs in your firewall’s allowlist are up to date. If you are running LiteSpeed Web Server v5.4.12 or newer, this will be handled automatically. The same goes for Imunify360 and Bitninja. Automation through other means will be added in the future, but until then, if your security solution cannot automatically keep up to date with the IP changes, you will need to manually update the QUIC.cloud IPs in your allowlist. Learn more in our Knowledgebase.

Can I be notified in real time of QUIC.cloud IP list changes?Link to question

Yes. You can be notified via email if you join our Google Group. We also announce IP list changes on Twitter and Slack.

Do you plan to add more POPs in the future?Link to question

Absolutely. We are always looking to expand and improve our network. If you have specific requests for PoP locations, feel free to join our Slack Community and post your ideas in the #quic_cloud_cdn channel

Configuration

General

How does QUIC.cloud know my domain’s IP address?Link to question

QUIC.cloud can get this information from WordPress via your LSCache plugin settings, but you can also manually set the IP address in your QUIC.cloud Dashboard, if you wish.

Does QUIC.cloud support HTTP/3?Link to question

Yes. QUIC.cloud is capable of serving requests via HTTP/3 to browsers that also support the protocol. But unlike other CDNs, QUIC.cloud is also capable of making backend HTTP/3 connections! If your site’s origin server supports HTTP/3 (it does if you are running on LiteSpeed Web Server) and your visitor’s browser supports HTTP/3, then QUIC.cloud will serve your content end-to-end via HTTP/3. If either the origin server or the client cannot handle an HTTP/3 connection, QUIC.cloud will connect via HTTP/2 or HTTP/1 as appropriate.

How do I verify that my site is using QUIC or HTTP/3?Link to question

Any site using QUIC.cloud CDN is capable of HTTP/3 connections. You can verify this with the HTTP/3 Check tool. If your site does not appear to support QUIC or HTTP/3, check your QUIC.cloud Dashboard and make sure your domain is set up properly.

Domains and DNS

How do I use my root domain (such as site.com) for QUIC.cloud?Link to question

To use your root (or apex) domain with QUIC.cloud, your DNS must support CNAME flattening or ANAME/ALIAS records. If your DNS provider does not support CNAME flattening, then the only way to use your root domain with QUIC.cloud is to switch your DNS provider. QUIC.cloud offers a free DNS service if you need one. Our knowledgebase has more information about DNS and QUIC.cloud CDN.

Do I have to use my root domain with QUIC.cloud?Link to question

It is not required to use the root domain. Subdomains may be used, if you prefer.

Can I use a CDN subdomain (such as cdn.site.com) instead of pointing my entire domain to QUIC.cloud?Link to question

No. Other CDNs that allow you to use a subdomain are only using it for static content (images and other rarely-changing assets). QUIC.cloud functions as a reverse proxy in front of your entire site, and so the site itself must point to the CDN. This is what allows QUIC.cloud to reliably cache your site’s dynamic content on our global network, and to serve everything from cache in a locale-advantaged manner.

What happens if I have a non-WordPress site at the same domain?Link to question

The simplest answer is that “it’s complicated.” Having multiple web apps at the same domain may or may not be problematic. Because the whole domain must be pointed to QUIC.cloud, the WordPress site will be fine, but any others at that domain could potentially experience caching issues, especially if they are running other web apps that use LSCache, or there are special rules in the .htaccess file that must be followed.

If possible, we recommend putting each site in its own subdomain (for example, blog.site.com instead of site.com/blog, or forum.site.com instead of site.com/forum). This way, you can point the WordPress site’s subdomain to QUIC.cloud without impacting any of the other sites living at that domain.

Is DNS verification required, and if so, why?Link to question

Yes, it is required. DNS verification is our way of making sure that your DNS is configured correctly for use with QUIC.cloud. During the test, we toggle the DNS to point your site to QUIC.cloud PoPs and then check whether it is indeed pointing to the PoPs. If successful, your site is considered Verified. We will automatically generate an SSL certificate (if you’ve enabled that option), and QUIC.cloud CDN will begin handling your domain’s traffic. If there is a failure at any point in the verification process, the DNS will be reverted back to your origin server. You can then fix your configuration and try again.

How can I tell if my DNS is configured correctly?Link to question

If your domain passed DNS Verification, then your DNS is most likely configured correctly. To be sure, try pinging your site twice:

  1. First use your site’s domain (for example, site.com or www.site.com)
  2. Then use the URL that QUIC.cloud provided to you (for example c12345.tier1.quicns.com)

The IP addresses returned from both pings should match.

Alternatively, visit LSCache Check, enter your URL, and look for the x-qc-pop response header. If it’s there, it means your site was accessed via a QUIC.cloud PoP, and your DNS is configured correctly.

SSL Certificates

Can I generate an SSL certificate without setting up a CNAME record?Link to question

No, you cannot generate an SSL Certificate via QUIC.cloud if you do not set up a CNAME record properly.

Approximately how long will it take to generate an SSL Certificate?Link to question

It normally takes up to a minute to generate an SSL Certificate. If it does not generate for you, please contact us on Slack or open a ticket.

Can I use my own SSL certificate?Link to question

Yes. QUIC.cloud has the ability to generate an SSL certificate for your site, manage the expiration, and keep it automatically up to date, but you may manage your own SSL if you prefer. Visit your QUIC.cloud Dashboard, and add the Certificate and Private Key in the CDN Config section. If you decide to use QUIC.cloud’s automatic SSL feature, we still strongly recommend that you keep your own certificate up to date on your origin server. This is required if you are using QUIC.cloud’s WordPress optimization services, and it allows end-to-end secure connections for the CDN.

Cache

What content does QUIC.cloud cache?Link to question

By default, QUIC.cloud caches your site’s dynamically generated pages. This cache is controlled via the LiteSpeed Cache plugin for WordPress. QUIC.cloud can also cache your site’s static content. Be sure to set Static Cache to ON in your QUIC.cloud Dashboard‘s CDN Config area.

Can I bypass the CDN?Link to question

Yes, you can easily bypass the CDN if you need to. In your QUIC.cloud dashboard, navigate to the domain you want to bypass, click on the CDN tab, then select CDN Config in the left hand menu. Toggle Bypass CDN to ON.

Can I purge the CDN’s cache?Link to question

Yes, however this should not be necessary under normal circumstances. The CDN cache is managed by the LiteSpeed Cache plugin for WordPress, and is sophisticated enough to know when content has changed and requires purging. That said, if you wish to purge the CDN cache manually, visit your QUIC.cloud Dashboard, and press the Purge All CDN Cache button in the Domain Overview section.

Does the LiteSpeed Cache crawler also crawl QUIC.cloud?Link to question

Yes. The crawler included in the LiteSpeed Cache for WordPress plugin will populate the cache at the origin server (but only if it is a LiteSpeed server), and also the cache at the QUIC.cloud PoP closest to the origin server.

Under the current CDN cache policy, pages are stored at a PoP for 24 hours from the last access. So, pages that don’t see much traffic will be removed from the PoP’s cache after about a day, but frequently-accessed pages will remain in CDN cache for as long as needed.

Future plans include tiered regional caching, which will increase the CDN cache hit rate and allow us to cache pages in a nearby node longer term.

Please note: if the Crawler > Site IP option is set in the LSCache plugin, the crawler will directly populate the cache for the server at that IP, essentially bypassing QUIC.cloud. If you wish for the local QUIC.cloud PoP to be included in your site’s cache crawl, then you need to leave Site IP blank.

Troubleshooting

What do I do if I haven’t received the activation email?Link to question

The activation email, entitled Activate Your QUIC.cloud Account is sent immediately, from no-reply@quic.cloud. If you don’t see it in your inbox, please check your spam folder, and add no-reply@quic.cloud to your email client’s allow list. You may contact us on Slack or via a ticket if you need further assistance.

Why can't I generate an SSL Certificate?Link to question

QUIC.cloud uses Let’s Encrypt to generate SSL Certificates. Sometimes certificate generation fails if your domain’s new or updated DNS records have not fully propagated yet. Please wait a few minutes and try again. If it continues to fail, please contact us on Slack or via a ticket for further assistance.

I updated my DNS configuration, so why does QUIC.cloud show a CNAME setup error?Link to question

Your DNS configuration changes may not have fully propagated. Depending on your DNS provider this can take anywhere from a few minutes to 48 hours. If the error persists after 48 hours, please contact us on Slack or via a ticket for further assistance.

How can I tell if QUIC.cloud is caching my site?Link to question

The easiest way to check whether QUIC.cloud is caching your site is to use the LSCache Check tool. This tool will indicate whether your site supports LSCache, and then it will tell you whether the page is cached at the origin server via LSCache or whether it’s cached by QUIC.cloud. It will also show you the relevant request headers.

I don’t see an x-qc-cache response for my CSS, JS or Images. Why not?Link to question

Images, CSS, and JavaScript are static files. In order for them to be cached by QUIC.cloud at least one of two things must happen:

  1. You have set Static Cache to ON in the CDN Config section of your QUIC.cloud Dashboard.
  2. The backend server provides an Expires or Cache-Control response header.

Why hasn’t my page speed score improved along with my site loading speed? Or vice versa?Link to question

The scores provided by page speed tools have little relation to the actual loading time for a website. These scores are relative and are based on how well you have implemented best practices. Best practices, however, do not guarantee your site is the fastest.

My site doesn’t appear to support a QUIC or HTTP/3 connection. What should I do?Link to question

Sites running on QUIC.cloud should support HTTP/3 connections. Use the HTTP/3 Check tool to see whether it’s supported on your site. If it is not, the most likely explanation is that your DNS configuration changes may not have fully propagated, or your DNS has been configured incorrectly. Verify your DNS is correct, and that it has fully propagated. If your site still does not support QUIC or HTTP/3, please contact us on Slack or via a ticket for further assistance.

How do I handle an Invalid Certificate error?Link to question

If you are using a QUIC.cloud-provided certificate, you can regenerate it. In the CDN Config area of your QUIC.cloud Dashboard, press the Generate Certificate button. If you have supplied an SSL certificate of your own, please ensure that it is valid.

Why are pages on my site getting 404, 503, 520, 521, 524, or other errors?Link to question

For help with HTTP response code errors, please see the Troubleshooting section of our Knowledgebase.

For more detailed information about these and many other topics, please see our Knowledgebase and our Blog.