Quic + cloudflare

Hi,

Technically yes, you can enable both.

But it might not make much of sense to enable 2 CDNs at same times.

And please note that more CDN does not always mean faster , it could slow things down due to too many layers in play.

Best regards,

@qtwrk

I have already Cloudflare in one of our sites and I don’t want to use another CDN because of what you said “more CDN does not always mean faster , it could slow things down due to too many layers in play”, but the thing is that your plugin becomes worthless because it would not let me cache anything unless I use QUIC.cloud CDN “To use the caching functions you must have a LiteSpeed web server or be using QUIC.cloud CDN”.

Plus I can’t get the “Domain Key to use the online services”.

This new version is a total train wreck!

Hi,

My apologize for the inconvenience.

When you say Quic Cloud in CDN part , I assumed that you want to use both QC and CF as CDN.

Please note that , the link to quic cloud is totally optional.

if you don’t want to link it , everything still works same way as before , the image opt , CCSS …etc

It’s just some naming things , before we didn’t give it name , now we just name it as Quic Cloud Online service.

For domain key , do you see any message it comes back ? usually when you failed to get the domain key ,it will state something.

Best regards,

@qtwrk

This is incredibly confusing.

The name of the pluging is called “LiteSpeed Cache”, so this is a CACHE plugin, yet you can not cache anything unless you use quic cloud: “To use the caching functions you must have a LiteSpeed web server or be using QUIC.cloud CDN”

For this particular site I just want to use Cloudflare as my CDN, (not both QUIC.cloud and Cloudflare, but the pluging says that NOTHING is being cached because “To use the caching functions you must have a LiteSpeed web server or be using QUIC.cloud CDN”

“For domain key , do you see any message it comes back ? usually when you failed to get the domain key ,it will state something.”

It says waiting for approval ( for hours now), if you click the green button “Waiting for Approval” the following message comes up; “Failed to communicate with QUIC.cloud server: The callback validation to your domain failed. Please make sure there is no firewall blocking our servers. Response code: 401”

Notice:
There is a problem receiving your domain key. Please click the Waiting for Approval button to retry.

There are two reasons why we might not be able to communicate with your domain::

1) The POST callback to https://www.samplesite.com/wp-json/litespeed/v1/token failed.

2) Our Current Online Server IPs was not whitelisted.

Please verify that your other plugins are not blocking REST API calls, whitelist our server IPs, or contact your server admin for assistance.:

I think you misunderstood

Caching works fine without quic cloud, its a local server thing

For example mysite I use Cloudflare and Bunny CDN, I did enable Quic Cloud for image and CSS optimzation, but not CDN

Hi,

Could you please access manually on your browser to https://www.samplesite.com/wp-json/litespeed/v1/token

and see what it returns ?

Best regards,

Hi @lechon

To clarify:

This is incredibly confusing.

The name of the pluging is called “LiteSpeed Cache”, so this is a CACHE plugin, yet you can not cache anything unless you use quic cloud: “To use the caching functions you must have a LiteSpeed web server or be using QUIC.cloud CDN”

It says LiteSpeed web server OR QUIC.cloud CDN. If you are using OpenLiteSpeed, LiteSpeed Enterprise, or LiteSpeed Web ADC on your site, you can definitely use the caching functions without enabling QUIC.cloud.

I hope this clears up the confusion.

I’m going to close this topic due to lack of activity. If you still need help, please answer @qtwrk ‘s previous question and we’ll be happy to re-open the topic.

Thanks!