Chatbot broken since 2.8.9 – ‘session expired’ error, 2.8.8 works fine

  • Resolved simontec

    (@simontec)


    5 months, 1 week ago

    Hello,

    Since version 2.8.9, the chatbot stopped working completely. It shows this error in the browser console:

    “Your session has expired. Please refresh the page to continue using AI Engine.”

    Request fails with:

    POST /wp-json/mwai-ui/v1/chats/submit → 401 (Unauthorized)

    ✅ What I’ve Tried:

    Cleared all browser, plugin, and server caches

    Disabled LiteSpeed Cache

    I do not use NotificationX

    Tried logged-in and guest users

    🔁 Version Behavior:

    ✅ 2.8.8 (Free) → works fine

❌ 2.8.9 and 2.9.0 (Free + Pro) → broken

    I recently subscribed to Pro but had to downgrade to Free 2.8.8 to keep the chatbot working while waiting for a fix.

    Here’s a screenshot of the error:

    Can you help investigate this? Thanks!

    Simon

    • This topic was modified 5 months, 1 week ago by simontec.
    • This topic was modified 5 months, 1 week ago by simontec.
    • This topic was modified 5 months, 1 week ago by simontec.
Viewing 5 replies - 1 through 5 (of 5 total)
  • loudcow

    (@loudcow)

    5 months, 1 week ago

    I am experiencing similar although only for guest users. I get the ‘session expired’ error plus also “Sorry, you’re not allowed do do that”.

    I’ve followed all troubleshooting, checked API connection is OK, added my Neko Pass licence again

    Noticing 401 errors in the console.

    • This reply was modified 5 months, 1 week ago by loudcow.
    Thread Starter simontec

    (@simontec)

    5 months, 1 week ago

    Quick correction to my original post:

    🔹 The issue actually happens only for guest (not logged-in) users.
    🔹 When logged in (admin or regular user), the chatbot works as expected.
    🔹 But for guest visitors, it consistently fails with:
    "Your session has expired. Please refresh the page to continue using AI Engine."

    Plugin Author Jordy Meow

    (@tigroumeow)

    5 months, 1 week ago

    Have you tried 2.9.1 @simontec ? 🙂

    Thread Starter simontec

    (@simontec)

    5 months, 1 week ago

    Not yet, let me test.

    Thread Starter simontec

    (@simontec)

    5 months, 1 week ago

    Issue fixed in 2.9.1 — really appreciate the support!

    • This reply was modified 5 months, 1 week ago by simontec.
Viewing 5 replies - 1 through 5 (of 5 total)

You must be logged in to reply to this topic.