• Resolved knapit

    (@knapit)


    Hi there!

    We’re using LSCache on a website running on OpenLiteSpeed. Previously it worked fine and had absolutely no problems whatsoever.
    This changed recently (give or take 3 weeks), with certain pages not loading or erroring out with the following: “”The operation couldn’t be completed. Protocol error” (NSPOSIXErrorDomain:100)”. This would only occur on Safari browsers, both mobile and desktops.

    Disabling and wiping the cache would resolve the issue for a short while (between 30 minutes and 2 hours) before the problem would come back. Now, its gotten so bad that not even that works, and we had to disable the entire plugin.

    When trying to load the page, OpenLiteSpees access log simply gives a 200 status (OK) for the page and the LSCache debug log also contains no helpful entries.

    Site and server info:
    – OpenLiteSpeed 1.7.3 installed and configured by DirectAdmin
    – WordPress 5.4.2
    – LSCache 3.3 (currently disabled completely)
    – WooCommerce (With an assortment of addons)
    – Wordfence
    – Divi Theme

    Hopefully there’s a solution for this ??

Viewing 4 replies - 1 through 4 (of 4 total)
  • Plugin Support qtwrk

    (@qtwrk)

    Hi,

    Could you please provide the report number ?

    you can get it from toolbox –> report —> click “send to LiteSpeed”

    Best regards,

    Thread Starter knapit

    (@knapit)

    Hi there,

    Thanks for your response. Sadly the problems were getting so severe that we have decided it was faster and easier to move to nginx for the time being. So a report won’t be of much help at this moment in time. We’ll have see when we have the time and ability to move back to OpenLiteSpeed.

    Thanks again!

    Plugin Support qtwrk

    (@qtwrk)

    Hi,

    OK , thanks for the information, wish you all the best ??

    Best regards,

    I’m also experiencing the exact same problem.

    Is there a fix?

    Thanks, Stephen

Viewing 4 replies - 1 through 4 (of 4 total)
  • The topic ‘LSCache causes protocol error on Safari browsers’ is closed to new replies.