Conflict Between Hide My WP Ghost and LiteSpeed Cache Crawler/QUIC.cloud API

  • Resolved SQ SuperRadu

    (@rdusnr)


    2 weeks ago

    Hi Support Team !

    I’m experiencing an issue where the LiteSpeed Cache Crawler and QUIC.cloud functionalities stop working whenever the Hide My WP Ghost plugin is activated. I’ve tried several configurations to allow LiteSpeed API routes and REST API paths, but the problem persists, even under minimal security settings in Hide My WP Ghost.

    I noticed that if I set the Security Level to “Deactivated” instead of “Light Mode,” the LiteSpeed Crawler and QUIC.cloud start working again. My setup uses OpenLiteSpeed as the web server.

    Steps to Reproduce

    1.  Activate Hide My WP Ghost plugin on my WordPress site.
2.  Set Protection Mode to Light.
3.  Change wp-admin path to a custom path, such as /adm.
4.  In Hide My WP Ghost settings:
?   Whitelist common REST API paths and LiteSpeed Cache API routes:
?   /wp-json/
?   /wp-json/litespeed/
?   /wp-admin/admin-ajax.php
?   /sitemap.xml
?   /sitemap_index.xml
?   Add localhost, 127.0.0.1, and the server’s IP to the whitelist.
5.  Go to LiteSpeed Cache > Crawler and manually click Start under the cron settings.
6.  Observe that the crawler does not start unless the Hide My WP Ghost plugin is either disabled or Security Level is set to “Deactivated”.

    Expected Behavior

    LiteSpeed Cache Crawler and QUIC.cloud API functionalities should work normally with Hide My WP Ghost active, especially when REST API paths and LiteSpeed-specific routes are whitelisted.

    Actual Behavior

    When Hide My WP Ghost is activated with Security Level set to “Light” (or higher), the LiteSpeed Cache Crawler and QUIC.cloud services cannot function, resulting in failures to reach necessary API routes (e.g., /wp-json/litespeed/v1/cdn_status). This happens regardless of settings adjustments, such as lowering protection levels, setting default paths for wp-json, and fully whitelisting the necessary routes and server IPs.

    Additional Information

    ?   WordPress Version: 6.6.2
?   LiteSpeed Cache Version: 6.5.2
?   Hide My WP Ghost Version: 5.3.02
?   Web Server: OpenLiteSpeed
?   QUIC.cloud: Active

    Thank you for your assistance! I’d appreciate any guidance on compatibility settings or configuration adjustments to resolve this issue.

Viewing 7 replies - 1 through 7 (of 7 total)
  • Plugin Support Peter

    (@petersquirrly)

    ??Hi Radu,

    Thank you for bringing this to our attention.

    After looking over quic.cloud we found their IP list.
    https://www.quic.cloud/ips

    Please go to Change Paths > Level of Security > Whitelist IPs and add all their IPs to be whitelisted. This should ensure a smooth functionality.

    Thread Starter SQ SuperRadu

    (@rdusnr)

    Hi Peter,

    Thank you for your response and for pointing me to the QUIC.cloud IP list!

    I’ve added all the QUIC.cloud IPs to the whitelist as suggested. However, I’m still experiencing issues with the LiteSpeed Cache Crawler not starting when Hide My WP Ghost is activated. The crawler consistently fails to run unless I set the Security Level in Hide My WP Ghost to “Deactivated”.

    Could you provide guidance on any additional settings specific to the LiteSpeed Cache Crawler that might allow it to function with Hide My WP Ghost enabled in Light Mode? My main objective is to keep the crawler functional while maintaining Hide My WP’s security features.

    Thank you again for your assistance and any further recommendations you can provide!

    Best regards,

    Radu

    Plugin Support Peter

    (@petersquirrly)

    We tested with the latest version and it worked with both cloud and caching. If all IPs were added it should work properly.

    Would you mind sending us a screenshot of the IPs?

    Thread Starter SQ SuperRadu

    (@rdusnr)

    Hi,

    Thank you for your assistance earlier. I wanted to provide an update regarding the crawler issue.

    Everything is working correctly now with QUIC.cloud, so that part is resolved.

    As for the crawler error, it seems it was somehow related to the security level settings. The crawler only started working properly when the security level was disabled, or it may have been a coincidence. After addressing this, the crawler is now functioning as expected.

    Thank you for your support, and please let me know if you need any further details!

    Best regards,

    Radu

    Plugin Support Peter

    (@petersquirrly)

    I was just about to write to update the plugin as our developer added a fix over the weekend which takes care of this, but glad to see a confirmation that everything is alright now.

    In case anything else comes up, we are one reply away!

    I too am having this same issue between Hide My WP and Litespeed Cache. When Hide My WP is switched on I cannot cache my site or run the crawler with Litespeed. When the security level is disabled it works fine, however I’d like to continue using this feature of course.

    Could you help me resolve it? I’ve tried switching the feature back on as I think the OP suggested but that didn’t work. I also have the IPs whitelisted.

    Plugin Support Peter

    (@petersquirrly)

    We have tested both Litespeed Cache and quic.cloud after the last update and it works properly on our end.

    Also, other customers of ours who encountered this confirmed that the issue is no longer occurring. On top of this, a large part of our userbase uses Litespeed Cache and we didn’t receive any other reports of such issues, so it could be something isolated to your end.

    Would you mind checking if you have the latest version of the plugin?

Viewing 7 replies - 1 through 7 (of 7 total)
  • You must be logged in to reply to this topic.