Hi @imjino,
Please refer to the following article for complete instructions – https://docs.litespeedtech.com/lscdn/onboarding/
Thread Starter
imjino
(@imjino)
Hi @shivam
I tried t follow exactly the guidance but not successful.
My website uses CloudFlare and https, none www domain.
– CNAME 1: I point www to mydomain.com
– CNAME 2: Point mydomain.com to cxx.tier1.quic.cloud
It shows CNAME can not be parsed ERROR when I click on “Verify”.
How could I do now?
Thank
Plugin Support
qtwrk
(@qtwrk)
Hi,
That verification is optional , it may also delayed for worldwide DNS broadcast , if your domain is working , you can safely ignore that error.
Best regards,
Thread Starter
imjino
(@imjino)
Thank you, @qtwrk
It works fine now.
But, please tell me is Quic Cloud better than CloudFlare CDN?
And how to check if Quic Cloud works or not?
Thanks
-
This reply was modified 3 years, 4 months ago by
imjino.
Plugin Support
qtwrk
(@qtwrk)
Hi,
Currently QUIC CLOUD is still at public test and not meant to be on production for now.
But QC does have certain unique features that no other CDN provider does.
To check if QC works or not, please open your browser dev tool (pressing F12) , go to network tab , click on main URL and go to header tab , you should see “x-qc-cache: hit/miss” that means it is working.
Best regards,
I am trying to do this in cloudflare, but I get the error “An A, AAAA or CNAME record already exists with that host. (Code: 81053)” when I try to add mydomain.com as an alias of c87.tier1.quic.cloud.
As per my understanding I can still use cloudflare DNS in conjunction with quic cloud?
Can you please make the instructions clearer?
-
This reply was modified 3 years, 4 months ago by
JohnS0N.
Plugin Support
qtwrk
(@qtwrk)
Hi,
You will need to remove your current A or AAAA record that has same name of your domain
and then to create the CNAME one.
Best regards,
Thank you, very obvious option actually.
I have changed the CNAME record now 8 hours ago and deleted the A record. It is the first time I am actually changing the CNAME records (I only changed DNS in the past). I read that the max time until the domain should be resolved in this case is 4 hours. Could there be any other issue? With SSL for example? I had that enabled in cloudflare and HSTS as well.
It’s still not resolving. I am now quite sure there is something wrong somewhere… could you please assist? The page has been offline since 12 hours and that’s quite bad. I will leave it through the night since the damage has been done and see if the domain starts resolving… but I think it won’t. In any case, if you would be so kind and are interested in solving this issue, this is the website address if that helps in any way.
This is the setup (both are set as DNS only in cloudflare aka. grey cloud is shown):
CNAME www is an alias of “mydomain.com”
CNAME “mydomain.com” is an alias of c87.tier1.quic.cloud
And on Quic.cloud the “mydomain.com” is pointed to the 107.6.156.58 where the server is located.
So what could be wrong? I’ve searched around for the past 10 hours and I don’t know what the mistake is. Please assist. Thanks a lot.
-
This reply was modified 3 years, 4 months ago by JohnS0N.
-
This reply was modified 3 years, 4 months ago by JohnS0N.
-
This reply was modified 3 years, 4 months ago by JohnS0N.
-
This reply was modified 3 years, 4 months ago by JohnS0N.
So after about 18 hours it still does not work, so I have no other option but to revert the changes back to my old.
I will set up another website just to test this further as I can not do tests on this one.
-
This reply was modified 3 years, 4 months ago by JohnS0N.
@qtwrk What should Recaptcha Concurrent connection Limit be set to?
Noticing random hanging (slow loading) with quic.cloud and intermittent 400 errors.
@imjino, @johns0n and @websitehelperberto
Apologies for the delay in reply. Most of these issues have more to do with setting up QUIC.cloud than they do with the LiteSpeed Cache plugin, so the best way to get support is in our Slack workspace.
First, join the golitespeed Slack team.
Then, visit the #quic-cloud-beta channel and post your question there.
Much appreciated!
Hi There
Hopefully I am in the right forum.
I have configured Quic.Cloud and was working fine until this morning, When I try to visit site its saying “Can’t connect securely to this page, similar warning from all (Chrome, Firefox, IE) browser. Site use Let’s Encrypt SSL certificate, pointing to QUIC.Cloud CDN by modifying CNAME in my share server. I have contacted to my hosting provider they check and found not issue at server site.
Any solution will be grateful.
Thsnks
Regards
Shaunpan
I have the same problem as @shaundas
