Frequently Asked Questions

About QUIC.cloud

General

What is QUIC.cloud?Link to question

QUIC.cloud is a high performance, LSCache enabled CDN service created by LiteSpeed Technologies. It is currently in beta and is available worldwide free of charge (up to a limit).

How many GB can I use on QUIC.cloud?Link to question

You can use up to 20GB per month on QUIC.cloud free of charge. If you require more than that we encourage you to contact us on Slack so we can discuss your needs.

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

If you use over 20GB in a month the DNS will change automatically so visitors will be directed to your origin servers again.

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

QUIC.cloud reduces the physical distance requests must go to deliver your site to its visitors by setting servers up across the world. Unlike other CDN services though, QUIC.cloud has the capability to cache dynamic content, meaning more content can be cached for more of your users. With less physical distance and more caching opportunities available, QUIC.cloud can deliver sites faster than any other service ever has.

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

All web servers, including Apache, Nginx, OpenLiteSpeed, etc, 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

If you enable our RECAPTCHA protection inside of the QUIC.cloud panel for the domain, we will detect if there is a high influx of connections going to your domain. If there is, we will have them verify via RECAPTCHA, which should help protect against Layer 7 attacks. We also have many security related features working behind the scenes to protect against DDoS attacks, such as blocking known bad IPs and preventing WordPress brute force attacks.

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

There is currently no limit to how many verified domains you can connect to each QUIC.cloud account. You are limited to 5 unverified domains.

Are there substantial performance improvements planned in addition to increasing the POP locations?Link to question

We consistently update with new features and performance improvements. Make sure to stay alert for all the cutting edge changes!

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

To get started, just follow our onboarding document, and if you have any questions you can reach us on Slack and/or Twitter.

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.

About Beta

Is QUIC.cloud considered production ready?Link to question

Currently, QUIC.cloud is still in beta. There is currently no ETA on when it will be out of beta.

How much will QUIC.cloud cost after it’s no longer in a beta state?Link to question

No decisions have been finalized in regards to the future cost of QUIC.cloud. We have decided we will continue offering a free tier, so everyone gets a chance to try it, and those who use LiteSpeed Web Server will get a larger quota for the free tier.

POP/Nodes

What does POP stands for in the context of a CDN?Link to question

POP stands for ‘points of presence’, which refers to the location in which our CDN nodes are placed and operate.

What are the locations of the current POPs?Link to question

We currently have POPs in the following locations:

  • Missouri, USA
  • New York, USA
  • Oregon, USA
  • Virginia, USA
  • Copenhagen, Denmark
  • Paris, France
  • Frankfurt, Germany
  • Madrid, Spain
  • London, United Kingdom
  • Mumbai, India
  • Tokyo, Japan
  • Singapore, Singapore
  • Sydney, Australia

What are the IP addresses of the current POPs?Link to question

The following IP addresses are subject to change at anytime without notice. The list can be found at: our IPs page.

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

Yes, so stay tuned for more future plans! Contact us in our Slack Community in the #quic_cloud_beta channel to make requests.

Configuration

General

How does QUIC.cloud know the correct IP address of the server where my site is located?Link to question

The LSCache plugin will auto update to recognize the correct IP address based on the WordPress installation, but it can also be manually updated through the domain overview on the panel inside QUIC.cloud.

Will a site using QUIC.cloud test yes for QUIC on HTTP3Check.net?Link to question

Yes. When testing, please make sure your website is set up properly and points to QUIC.cloud.

What is quic proxy?Link to question

QUIC proxy is a new feature that enables QUIC.cloud to use QUIC to connect to backend servers. The backend server must have QUIC enabled and available for access (some hosts block the port). Make sure that QUIC is available on the backend because if it is not available this option may slow the performance of your site rather than improve it. This feature is very new and may have bugs, so please let us know if you are experiencing issues when accessing your site.

Domain/CNAME

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

If you want to use your root domain you have to use a DNS provider which supports CNAME flattening or "ANAME".

Do I have to use a root domain for the CNAME record?Link to question

It is not required to use the root domain, subdomains can be used as well.

With other CDN providers, I can usually use a subdomain, such as cdn.site.com, so why do I need to point the entire domain to QUIC.cloud?Link to question

Because it isn't just using a subdomain for static content, QUIC.cloud functions as a reverse proxy in front of the entire site, it isn't just using a subdomain for static content. So the site itself has to point to the CDN. With other CDNs, the most they can reliably cache are your assets (even that is somewhat untrue - static files just change very infrequently). In other words, when using another CDN, browsers will always visit your server first. The secondary requests are handled by the CDN. With QUIC.cloud, we can cache your whole site on our CDN network, enabling you to serve everything from cache in a locale advantaged manner.

What does verification of the CNAME do?Link to question

CNAME verification tests to make sure your DNS configurations are set up correctly. It will toggle the DNS to point your site to QUIC.cloud POPs and run a test to see if your site is pointing to the POPs. If that succeeds it will generate a certificate if auto SSL is enabled. Once that is complete your site is verified and running on QUIC.cloud. At any point if there is a failure, the DNS will revert back to your origin server.

Is CNAME verified required?Link to question

Without CNAME verification, your site will not function properly. Verification is STRONGLY recommended.

How can I tell if the CNAME is properly set up?Link to question

If CNAME verification is completed successfully, your CNAME is most likely set up properly. To better verify you can visit your site in a private browser.

Another way to verify that your CNAME records are set up correctly is to ping your domain (ensure it’s the default one you use to access your website www/non-www) and the CNAME record QUIC.cloud has provided you. The IPs should match. You can also check to see if there is a x-Qc-pop response header; this will only show if the CNAME setup is working properly.

SSL Certificate

Can I generate the SSL Certificate if I skip the CNAME?Link to question

No, you cannot generate an SSL Certificate via QUIC.cloud if you do not set up the CNAME 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.

If I already have an SSL certificate on my site, do I need to do anything in the QUIC.cloud panel for SSL to work?Link to question

If you have your own certificate that you want to manage yourself, you can do so by adding the cert, key, and certificate chain on the QUIC.cloud dashboard. Do note that you will need to re-upload the certificate every time you update the certificate in order to keep it up to date.

Alternatively, you can use the Generate and Auto SSL settings on the QUIC.cloud dashboard. We will manage the expiration update automatically.

We highly recommend that you keep your certificate up to date on your origin server in order to properly maintain the connection with QUIC.cloud.

Cache

What does QUIC.cloud cache?Link to question

QUIC.cloud caches both static and dynamic content. To cache static content though, the “Enable Static Cache” option must be set to “YES”.

Can I bypass the CDN?Link to question

Yes, you can easily bypass the CDN. In your my.quic.cloud dashboard, navigate to the domain you want to bypass and click on the 'Cache' tab. There, you can toggle the 'Enable CDN' option. 'OFF' will bypass QUIC.cloud and send users directly to your origin server.

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

Yes, you can purge the cache by clicking the “Purge All CDN Cache” button in the Domain Overview section of the QUIC.cloud dashboard. The normal LSCWP purges will purge the QC cache as well.

Crawler

Can I use the crawler function inside of the LSCache for WordPress plugin with QUIC.cloud?Link to question

Yes, the crawler function does work with QUIC.cloud. The crawler function will crawl the POP closest to the origin server. If you have a LiteSpeed backend server it will also be populated by the crawler.

Does the crawler automagically detect QUIC.cloud and warm up the cache on the CDN POPs?Link to question

If the LSCache for WordPress plugin has the `Crawler -> Site IP` setting filled, the crawler will bypass the CDN and go directly to the server tied to `Site IP` when it runs, meaning if it is not pointed to QUIC.cloud it will bypass caching on it. If that setting is empty, the crawler function will crawl the POP closest to the origin server. If you have a LiteSpeed backend server, it will also be populated by the crawler. In the future, we will have a crawler function available to crawl more POPs.

Troubleshooting

I believe I should have received the activation email already, but I haven’t; why not?Link to question

Please check your spam folder to make sure it was not sent there. If it is not there either, please contact us for further assistance.

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

QUIC.cloud uses Let’s Encrypt to generate SSL Certificates. If it fails to generate the certificate, it may be due to the DNS. Please wait a few minutes and try again. If it still does not work, let us know and we'll assist you.

I set the CNAME up, so why is QUIC.cloud showing an error for the CNAME setup?Link to question

Different DNS providers can take different lengths of time to propagate the records, taking anywhere up to 48 hours.

Why is my site not showing that it is pointed to QUIC.cloud? Or why is my site throwing 404 errors?Link to question

You may have your CNAME pointing to the wrong domain, meaning your site is not set up correctly. For example, if your site is configured to use www.site.com, you should be updating the CNAME record for www. If instead your site is configured to use site.com, you should be updating the CNAME record for the root domain. Updating the incorrect CNAME record could result in redirecting to the correct domain which is not behind QUIC.cloud or finding a domain that doesn’t exist on your server.

Why is my website indicating that it is not using QUIC even though it should be?Link to question

The two most likely possibilities are you do not have an SSL Certificate, or your DNS is not pointing to QUIC.cloud.

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

You can check the x-Qc hit/miss response header. If it shows ’hit’, it is caching.

Why isn’t there a x-qc hit/miss response header for static files like CSS, JavaScript, image, etc?Link to question

Make sure that the “Enable Static Cache” option is set to “YES”. Also, the static file cache depends on the 'Expires' or 'Cache-Control' response header from the backend server. Please make sure that at least one of these are present.

Why hasn’t my PageSpeed score increased, but my site loading speed has? Or vice versa?Link to question

The pagespeed score has no relation to the actual loading time. Pagespeed is a relative score based on how good you are at doing best practices (which doesn’t always mean fastest.)

Why am I getting a 503 error with QUIC.cloud?Link to question

If you are receiving a 503 error when visiting a site that is pointed to QUIC.cloud, there is an issue with QUIC.cloud serving the website. Please contact us so we can diagnose the issue.

Why am I getting a 520 error with QUIC.cloud?Link to question

520 Origin Server Unavailable: The connection to the origin server could not be completed.

The 520 error indicates that the QUIC.cloud POP was unable to connect to the origin server. Most likely, the issue is a firewall at the origin server blocking connections. Try adding the QUIC.cloud IPs to the firewall or request that your hosting provider do so. Note that the IP list provided is not necessarily nodes that browsers will visit. This is the list of nodes that will contact your server.

The QUIC.cloud IPs are automatically updated for hosts that use the Imunify360 and BitNinja security systems. If you or your host use a different security system that can pull from an IP list, please let us know and we'll contact them!

Why am I getting a 521 error with QUIC.cloud?Link to question

521 Origin Server Timeout: The connection to the origin server timed out.

The 521 error indicates that the connection between the QUIC.cloud POP and your origin server timed out. 'Timing Out' means that there was no activity for a lengthly period of time, so the connection is assumed to be dead.