LiteSpeed Lisa
Forum Replies Created
-
Forum: Plugins
In reply to: [LiteSpeed Cache] Missing information on AVIF optimization creditsImage Optimization has two processing queues: Standard and Advanced.
Standard Queue includes image optimization and WebP generation, and is always 100% free.
Advanced Queue includes faster image optimization and either WebP or AVIF generation. You get free Advanced Queue credit at the beginning of every month, and if you need more, you can buy it (either a $5/month subscription for 20000 additional requests that amounts to $0.00025 per image, or a pay-as-you-go $3 for 10000 requests that amounts to $0.0003 per image).
So, the costs associated with selecting AVIF as your next-generation image format are the same as using the Advanced Queue power-up. Hope this helps!
I will take a look at our pricing page and documentation and see if I can make these costs more clear. Thanks for the feedback.
- This reply was modified 6 months ago by LiteSpeed Lisa. Reason: Added a clarifying sentence
Forum: Reviews
In reply to: [LiteSpeed Cache] Quota exceeded because of litespeedHi, @rkramer I’m sorry you’ve had this experience. It’s possible the issue you are having is due to a random string in one of your JavaScript files. The randomized string causes a new combined JS file to be created for every cache variant of every page on your site. It can be a lot. We have a blog post about that, if you want to try to find the randomized string and solve the problem.
Forum: Reviews
In reply to: [LiteSpeed Cache] Waste of Time@lisaleftfoot sorry to hear you’re disappointed :-/
It sounds to me like you were on the Standard Plan for the CDN. There is a Free Plan with unlimited bandwidth, and maybe that will work better for you. You can learn more about that here.
The support team should be able to help you out with the image optimization issue, if you want to pursue it further. You can open a ticket at QUIC.cloud, or post a support topic here, and be sure to grab your report number so the team has information about your configuration that can help them get to the bottom of the issue.
Forum: Reviews
In reply to: [LiteSpeed Cache] LiteSpeed Plugin now is a QUIC ADI am sorry to hear that. But we appreciate the feedback, and will take it into account!
Forum: Reviews
In reply to: [LiteSpeed Cache] LiteSpeed Plugin now is a QUIC ADHi. I just wanted to clarify that QUIC.cloud is 100% optional. You can cache your site and use most of the optimization features without enabling QUIC.cloud.
There has been some feedback that the QUIC.cloud banner introduced in v7.0 gives the impression that enabling QC is required. It is not. We are redesigning that area to make it more clear. The only functions you need QUIC.cloud for are:
– Image optimization
– Critical CSS
– Unique CSS
– Low-quality image placeholders
– Viewport imagesFor everything else, the LiteSpeed Cache plugin works the same as it always has. You can safely ignore QUIC.cloud if you want to.
Hope this clears everything up!
Hi, Rob
We’ve already come up with a plan for improving that QUIC.cloud banner and making it dismissible. That will come in a future update. Thanks for your feedback.
As for your other suggestion, we don’t have any single resource that would cover all of those bases, but we do have a few blog posts that you might find interesting:
https://www.quic.cloud/blog in general, and https://www.quic.cloud/why-switch-to-quic-cloud/ and https://www.quic.cloud/a-handy-guide-to-online-services/ in particular. I’ll keep your suggestion in mind for a future post!
Lisa
(Director of Content)Forum: Reviews
In reply to: [LiteSpeed Cache] Annoying and irritatingTo be clear, though, QUIC.cloud is not required. You can fully cache the dynamic pages on your site without a QUIC.cloud connection. And you can use many of the optimization features as well. The only features you need QC for are:
- Content Delivery Network (CDN)
- Image Optimization
- Critical CSS Generation (CCSS)
- Unique CSS (UCSS)
- Low Quality Image Placeholder Generation (LQIP)
- Viewport Images (VPI)
Everything else is handled locally and can be done without QC. Hope this helps!
Forum: Plugins
In reply to: [LiteSpeed Cache] Is LiteSpeed Cache vulnerable?It’s not a matter of extraordinary settings. Cloudflare’s dynamic cache is not cleared when LiteSpeed’s cache is cleared (@litetim just verified that this was still true). There is always the risk of the CF cache becoming outdated, whether you use the plugin or not.
Our compatibility doc already states that LSCWP is compatible with CF, only if you’re not using CF APO. I will look into whether there are other places that we should add this warning.
Forum: Plugins
In reply to: [LiteSpeed Cache] Is LiteSpeed Cache vulnerable?@krashlab Thank you for the details you were able to share about this.
We don’t believe this is a hack. We think the answer to this issue is found somewhere in your Cloudflare and LSCWP settings. Working with multiple caches can easily open you up for conflicts that are not easy to see right away, especially if you are using CF to cache dynamic pages.
And if the issue is indeed due to CF dynamic cache settings, then you haven’t actually solved the problem by uninstalling the plugin. You’re still probably serving from an outdated cache. You just aren’t seeing the symptom anymore because you are no longer generating optimized CSS and JS files (an outdated HTML page that was still referencing the old CSS/JS file names caused the errors, as @qtwrk mentioned in reply to the original thread).
We realize you have decided to stop using the plugin. If you change your mind in the future, we’d be happy to work with you to diagnose the issue.
Forum: Reviews
In reply to: [LiteSpeed Cache] Just a nuisanceYou can open a ticket (email
[email protected]) and our team will be happy to help you correct your email address so that you can proceed.
Also, just FYI, we will be releasing an update soon to provide a better experience with verification and site linking, but if you don’t want to wait for that, the support team can help you now.Thank you for your effort!
Forum: Reviews
In reply to: [LiteSpeed Cache] hacked, be carefulSecurity is very important to us. We are aware of these vulnerabilities affecting versions older than 5.7. We are not aware of any more recent vulnerabilities affecting the LSCache plugin. If you were hacked with a more recent version, and can show that it was the LSCache plugin that allowed the hackers access, please contact us at [email protected] and provide as many details as you can so that we may address this ASAP.
I’m sorry to hear you’re having difficulty. It definitely sounds like something is wrong. Have you contacted the support team via email ([email protected]) or posted a support thread here? We can help.
Forum: Plugins
In reply to: [LiteSpeed Cache] Broken sitesIt would be helpful if you let us know what issue you are referring to. We are unaware of any problem that is impacting “millions of sites,” as you say. Obviously an issue of that magnitude would be a high priority for us.
Forum: Reviews
In reply to: [LiteSpeed Cache] goodI’m sorry to hear you’re having trouble keeping the LSCache plugin permanently deleted.
To clarify, LiteSpeed is not responsible for auto-installing the plugin on your website. This is a hosting-provider-level issue.
If your hosting provider is using the LiteSpeed cPanel tool, you can opt out of future updates this way:
In cPanel, choose the LiteSpeed Web Cache Manager, select LiteSpeed Cache Management > WordPress Cache and “flag” your site. This will make sure your site is skipped next time the mass installation tool is run.
Otherwise, please contact your hosting provider for help.