Frequently Asked Questions
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.
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.
How many websites can each QUIC.cloud account support? Link to question
There is currently no limit to how many websites you can connect to each QUIC.cloud account.
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!
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.
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”.
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:
- Paris, France
- Frankfurt, Germany
- Tokyo, Japan
- Singapore, Singapore
- Oregon, USA
- Virginia, USA
- Sydney, Australia
- London, United Kingdom
What are the IP addresses of the current POPs? Link to question
The following IP addresses are subject to change at anytime without notice, please check back to see if the list has changed:
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, 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.
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 main domain for the CNAME record? Link to question
It is not required to use the main 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, 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.
Without CNAME verification, how will QUIC.cloud work? After clicking “Verify” there is a parsing error. Link to question
Verification is just for your own information. You don't have to press the `Verify` button in order for everything to work. In this case, the parsing error you are getting with the verification is more a problem with the verification process itself than a problem with your CNAME record.
How can I tell if the CNAME is properly set up? Link to question
Our verification process is one of many ways to detect if the CNAME is properly set up. It does not work for all cases though, such as when using the CloudFlare DNS. 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. If they match, you'll get the benefits even if it’s not verified on the dashboard. You can also check to see if there is a x-Qc hit/miss response header; this will only show if the CNAME setup is working properly.
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 a few seconds 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
Yes! If you use a free provider like Let’s Encrypt you can use the Generate and Auto SSL settings inside of the QUIC.cloud panel. If you use a purchased certificate from DigiCert, Geotrust, etc, then you will need to install the certificate inside of the QUIC.cloud panel.
Can I bypass the CDN? Link to question
Yes, you can easily bypass the CDN by clicking the “Bypass QUIC.cloud CDN” button in the Domain Overview section of the QUIC.cloud dashboard.
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.
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.
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, than as long as the domain is pointing to QUIC.cloud it will warm the cache on the CDN POPs when the crawler runs.
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. Using Cloudflare CNAME flattening to verify will not work, but QUIC.cloud may still work fine.
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 site set up incorrectly by having your CNAME point to the wrong domain. 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.
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.
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 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, QUIC.cloud may not be able to talk to your origin server. To resolve this please make sure QUIC.cloud's IP addresses are whitelisted in any firewall you have on your backend server. Click here for a list of our current IP addresses.