After deleting lightstart 403 still there

  • Resolved anov

    (@anov)


    6 days, 23 hours ago

    hello

    after some issues with the lightstart plugin i set it to inactive, deactivated it and finally deleted it. but still, very often the 403 maintanance page is still there. i deleted also the maintanence page (not sure if it was from lightstart) the last screenshot the Console error leads me to this URL https://developer.mozilla.org/de/docs/Web/HTTP/Headers/Set-Cookie#samesitesamesite-value

    there is something wrong since i deleted the plugin. can you please help me out what i have to do to make it work properly again? thanks

    edit: i checked other posts but they didn’t had full answers to it so i created a new one

    • This topic was modified 6 days, 23 hours ago by anov.

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

Viewing 3 replies - 1 through 3 (of 3 total)
  • Thread Starter anov

    (@anov)

    edit2: i also cleared cache several times in WP on many different sites. after a cache clear it works for some time, but the 403 still is coming back on different sites.

    the text on the last screenshot says

    The cookie “WP_SESSION_COOKIE” does not have a valid value for the “SameSite” attribute. Soon, cookies without the “SameSite” attribute or with an invalid value for it will be treated as “Lax”. This means that the cookie will no longer be sent to contexts that belong to a third-party provider. If your application requires the cookie in these contexts, please add the “SameSite-None” attribute to it.
    You can find more information on the “SameSite” attribute at https://developer-mozilla.org/docs/Web/HTTP/Headers/Set-Cookie/SameSite.

    • This reply was modified 6 days, 21 hours ago by anov.
    Thread Starter anov

    (@anov)

    my friend who is a server specialist found out, that the WP Plugin chatty and the lightstart plugin somehow interfered which each other. after some serverchanges and deactivating and activating chatty it worked. if i get more information out of it, i will post it here.

    Plugin Support Kush

    (@kushnamdev)

    @anov Thank you for updating this thread with the information about the issue. We are glad to hear that you were able to track the issue down.

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