Gambit Mutant
Forum Replies Created
-
Forum: Plugins
In reply to: [LiteSpeed Cache] Webp not served on Desktop version homepage onlyUnder virtual hosts in the OLS admin panel it shows a 404 error. The web host hasn’t been able to help with this. So I’m unable to change the cache-control header and it’s hurting my site’s SEO.
CURRENT VERSION: OpenLiteSpeed (DirectAdmin Edition) 1.7.16
Forum: Plugins
In reply to: [LiteSpeed Cache] Webp not served on Desktop version homepage onlyThanks. I’m currently working on updating the OLS TTL with DirectAdmin. The webhost said I need a premium version of the VPS to modify the .conf file.
What’s happening with the Webp images is they’re mostly not being served on the Desktop version of the homepage even though the webp images are available and are smaller sizes. Many images on the Desktop homepage aren’t being served with Webp. I even reoptimized all the images recently to try and solve it, and have Webp set to 75% the file size of the original images.
Here are a couple examples from Google Page Speed Insights:
Forum: Plugins
In reply to: [LiteSpeed Cache] Custom URL real cron jobs are cached when Guest Mode is onI’m sure the caching of the custom URL real cron job was an issue, but as it turns out, that wasn’t the only issue. Something else is preventing that cron job from running automatically that’s unrelated to your caching plugin. I just can’t seem to figure out what’s causing this to happen. My apologies for any inconvenience this may have caused.
I found that if I choose the “use built-in cron” settings option for the WP Automatic plugin, the automated cron tasks work again for this plugin! And I have a real alternate cron already set up for the default WordPress cron.
While it’s not the exact solution I was looking for, it’s still an excellent workaround in my case. Thanks for all of your help plugin support!
Forum: Plugins
In reply to: [LiteSpeed Cache] Custom URL real cron jobs are cached when Guest Mode is onI can confirm that there’s still an issue with QUIC.cloud CDN caching the cron page, preventing automated cron tasks. I’ve turned the CDN off again for the time being until there’s a permanent fix.
Forum: Plugins
In reply to: [LiteSpeed Cache] Custom URL real cron jobs are cached when Guest Mode is onI had run into another issue with real cron tasks after using that solution above for now, but found a solution!
LiteSpeed cache’s ObjectCache that uses memcache or redis was causing automated cron tasks to have their next run be decades ago in the past, so they never ran automatically.
The WP Crontrol plugin was showing this when running the tasks manually:
Hook wp_automatic_hook
Arguments none
Next Run (UTC-8) 1969-12-31 16:00:01 52 years 2 months ago
Action wp_automatic_function()
Recurrence Non-repeating`After disabling ObjectCache, that problem went away. But I still think there needs to be a way to exclude the cron pages from being cached by QUIC.cloud CDN. My apologies for any inconvenience this may have caused you, the plugin developers. I’m still new to using LiteSpeed cache and QUIC CDN. I will try re-enabling the CDN and see if there are still any issues.
Forum: Plugins
In reply to: [LiteSpeed Cache] Custom URL real cron jobs are cached when Guest Mode is onYes, that worked for the time being. It appears that the QUIC.cloud CDN is what’s caching the cron page. I had excluded the WP Automatic plugin path and the cron page URL in your plugin’s CDN settings, but the cron page was still being cached by QUIC CDN. Likely because the CDN exclude is for paths and not full URLs such as the cron page.
I’ve now turned off QUIC CDN in your plugin and bypassed the CDN on the Quic.Cloud website, and the cron page URL is no longer being cached.
Cron page HTTP header in a private browser after changing those settings:
x-litespeed-cache-control: no-cacheI think this means we’re getting closer to a solution.
Forum: Plugins
In reply to: [LiteSpeed Cache] Custom URL real cron jobs are cached when Guest Mode is onI’ve installed v4.6-a4, excluded the cron page URL, cleared the cache, but the cron page is still being cached in private browser mode.
It still shows: x-qc-cache: hit
