• Resolved nisto2016

    (@nisto2016)


    Hi,

    Beside your Plugin I am running also the Plugin WP Fastest Cache. Like you advise after each change in the settings I am clearing the WordPress Cache with it and everything works fine.
    But each morning the Chat Bot is down somehow and when I enter a question into the chatbox the standard “error message” appears.
    When I then clear the cache again the Chat Bot is working fine again.

    Is it a problem with this special Caching Plugin? Have you a recommendation for a Caching Plugin which works fine with your Plugin? Or do you have any other reommendation how to solve this problem?

    Thank you very much and best regards
    Nicola

    The page I need help with: [log in to see the link]

Viewing 3 replies - 1 through 3 (of 3 total)
  • Plugin Author intelahelp

    (@intelahelp)

    Hello @nisto2016.

    It seems that in the WP Fastest Cache plugin you are using a large cache lifetime. It is the most likely reason for malfunctioning chat widget.

    WordPress has mechanism for authorizing requests to its API. WordPress issues tokens (“nonces”, numbers used once) that should be supplied with every request to WordPress API. Nonces have limited lifetime. By default it is set to 12 hours. If you have long cache lifetime, user may get the page with invalid overdue nonce that can’t pass nonce validation and causes “403 forbidden” error.

    Therefore, to solve this issue you may shorten your cache lifetime. It should help users to avoid getting nonces older than 12 hours.

    Thread Starter nisto2016

    (@nisto2016)

    Thank you very much for this helpful support. Yesterday I reduced the cache lifetime to 1 hour and so far no new shutdown of our chat bot. So the problem seems to be solved ??

    Plugin Author intelahelp

    (@intelahelp)

    @nisto2016.
    We are glad that everything works for you now.
    Thank you for letting us know.

Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘Caching Problem with WP Fastest Cache-Plugin?’ is closed to new replies.