• Resolved psamathe

    (@psamathe)


    I don’t use CDN (none) and have never connected to QUIC and before and after update all CDN options are “Off” but suddenly I’m getting WordPress warnings about

    Warning:

    You must have Domain Key first before linking to QUIC.cloud.

    I don’t want a domain key, I don’t want CDNs (anybodies) so why all these warnings everywhere (even on non Litespeed plug-in pages).

    I’ve reverted to a pre version 3 plug-in which works (straight forward settings, no warnings everywhere (in WordPress).

    Is this a bug or daftness by LiteSpeed or do I need to find a different cache plug-in?

    These changes seem to have moved settings all over the place – rather a mess where before a “Settings” page with all the tabs on, now different pages with different tabs and big warnings about options disabled. As I say a mess to achieve what?

Viewing 15 replies - 1 through 15 (of 23 total)
  • Plugin Support LiteSpeed Lisa

    (@lclarke)

    Hi @psamathe

    You are correct, CDN usage is optional. Are you using Image Optimization, Critical CSS generation, or Low-Quality Image Placeholder generation? If so, those services are provided on QUIC.cloud servers and require a domain key.

    If you are not using those services, then you should not be seeing such warnings. Please let us know if you are not using the services, and we will look into it.

    We know the new interface may take a little bit of getting used to, but the re-organization by subject (instead of lumping all settings together in one place) should make things easier to find in the long run.

    Our Beginner’s Guide (even if you’re not a beginner) should help you get your bearings.

    Thread Starter psamathe

    (@psamathe)

    No CDN, no Image Optinisation. Can’t see “Low-Quality Image Placeholder” setting but all the lazy load/media stuff is off.

    Switched off CCSS ages ago as it broke my site. But I now see that whilst “Load CSS Asynchronously” is OFF, “Generate Critical CSS” and “Generate Critical CSS In Background” have reverted to “ON” – both these should have no effect as “Load CSS Asynchronously” is OFF?

    At some point something has been changing my settings but I can see no reason why I should be needing a QUIC.clod domain key.

    (LiteSpeed access to my servers is blocked anyway because at least some are running on Digital Ocean and they are a nightmare source of hack attempts (continual) so Digital Ocean AS number is completely blocked.

    Thread Starter psamathe

    (@psamathe)

    In fact whatever has messed with the settings has disabled all the optimisations I had previously set and had assumed would stay set!

    e.g. CSS minify, CSS combine, JS minify, JS combine, HTTP/s Push, etc! something has reset them all!

    Plugin Support LiteSpeed Lisa

    (@lclarke)

    > In fact whatever has messed with the settings has disabled all the optimisations I had previously set and had assumed would stay set!

    That shouldn’t happen. I’m sorry about that. It should have preserved your previous settings.

    Would you mind sharing your Report Number, found in WP Admin > LiteSpeed Cache > Toolbox > Report? We can see if any of the current settings would be triggering the domain key notifications.

    Thread Starter psamathe

    (@psamathe)

    Report number and date are both blank.
    I pressed “Automatically Install” and it went and install a new plug-in I have absolutely no knowledge about. and I hate new plug-ins as quite a few don’t clear out wp-options on remove and it just gets bigger and bigger and now I’ve got to go check what this unknown plug-in has done! (Whilst I’m now spending ages getting the site caching back properly set.

    Plugin Support LiteSpeed Lisa

    (@lclarke)

    If you press the Send to LiteSpeed button, it sends us your report, and generates a Report Number that you can share with us here.

    I’m sorry. I wasn’t clear enough. That Automatically Install is for something else, and is not needed. You can uninstall the plugin it added. Apologies for the inconvenience!

    Thread Starter psamathe

    (@psamathe)

    LKSFUEPV

    But I’m changing settings at the moment to try and get the CSS/JS combine/minify settings working again.

    Thread Starter psamathe

    (@psamathe)

    If I re-install V3 of the plug-in will it still be giving warnings about domain keys everywhere (not just on the LS Cache pages.

    Better if it didn’t give any warnings if the CDN is not enabled, but currently on latest pre V3 plug-in and I don’t like not keeping up to date but also I don’t want warnings about stuff I don’t want/need all over WordPress Admin areas (which is how I noticed it to begin will).

    Plugin Support LiteSpeed Lisa

    (@lclarke)

    I checked your report, and see you’re back to 2.9.9.2

    So, I can’t tell which service is triggering the domain key warning. Our developer tells me, though, that the domain key warning should indicate which service needs it. Does your warning say anything more than this?

    You must have Domain Key first before linking to QUIC.cloud.

    My guess is it’s the LQIP setting, but that doesn’t exist in v2. LQIP generates an image placeholder in the background, and it uses online services to do it. When you switch back to v3 in the future, check LiteSpeed Cache > Page Optimization > Media Settings, and make sure that LQIP Cloud Generator is OFF.

    Hope this helps!

    Plugin Support LiteSpeed Lisa

    (@lclarke)

    If I re-install V3 of the plug-in will it still be giving warnings about domain keys everywhere (not just on the LS Cache pages.

    It should not, if LQIP settings are off. If you are still seeing the warnings, you can send us a new report so we can see your v3 settings and let you know if any of them are triggering the notification.

    Thread Starter psamathe

    (@psamathe)

    Back with V3 <latest release> and it’s still asking for a domain key

    New Report: SJRXDJPC (created after updating to latest release plug-in)

    Thread Starter psamathe

    (@psamathe)

    It looks like the update to V3 messes-up the settings as I just got V2 settings working with my site (which requires CSS Combine to be “OFF”) and updated to V3 and the Page Optimisation settings have it set back ON

    Thread Starter psamathe

    (@psamathe)

    And now if I try and reset things and press “Save” Wordfence security

    403 Forbidden
    A potentially unsafe operation has been detected in your request to this site, and has been blocked by Wordfence

    So I can’t reset and save the correct settings. I’m getting frustrated by this plug-in (sorry but I have other stuff to do today).

    Plugin Support LiteSpeed Lisa

    (@lclarke)

    I understand.

    We’re having a little trouble here with the report service, hence the delay.

    For now, please just make sure that the following settings are OFF, and that should prevent any need for a domain key:

    Image Optimization > Image Optimization Settings > Auto Request Cron
    Page Optimization > CSS Settings > Generate Critical CSS
    Page Optimization > Media Settings > LQIP Cloud Generator
    CDN > CDN Settings > QUIC.cloud CDN

    If all of those settings are OFF there should be no more domain key notifications. Please let us know if this doesn’t solve the problem. And again, apologies for the inconvenience!

    Thread Starter psamathe

    (@psamathe)

    I can’t save settings – Wordfence is blocking it as an “unsafe transaction”.

    The update to V3 has trashed all the settings as now (apart from the “combine” settings having become re-enabled, “Generate Critical CSS” has also become r-enabled.

    I’ve got to revert back as I can’t switch-off the functions that V3 has re-enabled

Viewing 15 replies - 1 through 15 (of 23 total)
  • The topic ‘Just Updates and QUIC Warnings Everywhere’ is closed to new replies.