Issues with LiteSpeed Cache plugin

  • Resolved frafor

    (@frafor)


    1 month, 2 weeks ago

    I am having some issue with Altcha in self-hosted config when paired with Litespeed powered servers and using the native Litespeed Cache plugin to handle cache.

    It seems that the nonce gets cached and from time to time I am not able to login or send a form because the altcha doesn’t allow me.

    I have tried to match the LS cache time with the Altcha update time, however this ended up just in time frames where the things work, and time frames where things do not.

    This has started to become more than annoying later so we are thinking to roll back to recaptcha.

    However, since I really like Altcha (and we wrote about it even in my company’s blog) I’d really like to know if there’s something we can do.

    Our last attempt was to turn off REST API calls caching in Litespeed Cache, we’ll see if that can help, but please let us know what you think!

    • This topic was modified 1 month, 2 weeks ago by frafor.
Viewing 4 replies - 1 through 4 (of 4 total)

  • Also interested. Have Litespeed running on all my sites and am very interested in this plugin.

    Plugin Author Daniel

    (@danielregeci)

    Hi,
    there was a bug in the plugin, where the REST API endpoint did not send cache-control header. It’s fixed in the version 1.9.3, please update the plugin, it should fix caching issues.

    If any caching plugin still caches the response, exclude ALTCHA’s challenge endpoint from cache. With Lightspeed, you can configure excluded URIs under “Excludes -> Do Not Cache URIs”, add “/wp-json/altcha/v1/challenge”.

    Ok thanks a lot for this explanation!

    Plugin Author Daniel

    (@danielregeci)

    resolved.

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