Page MenuHomePhabricator

Rollback on ru.wp often fails with "problem with your login session"; reloading and trying again doesn't help
Closed, InvalidPublic

Description

In last two weeks attempt to rollback some edit often fails with message "There seems to be a problem with your login session; this action has been canceled as a precaution against session hijacking. Go back to the previous page, reload that page and then try again." Reloading and trying again doesn't help. It's just happened on this page https://ru.wikipedia.org/wiki/%D0%9F%D1%80%D0%B5%D0%B4%D0%BC%D0%B5%D0%BD%D1%81%D1%82%D1%80%D1%83%D0%B0%D0%BB%D1%8C%D0%BD%D1%8B%D0%B9_%D1%81%D0%B8%D0%BD%D0%B4%D1%80%D0%BE%D0%BC?action=history (attempt to rollback last anonymous edit). Complaints about this problem received from other ruwiki users.

Specs:
OS: Win 8.1
Browser Chrome, Firefox

Event Timeline

Aklapper renamed this task from Problems with rollbacking to Rollback on ru.wp often fails with "problem with your login session"; reloading and trying again doesn't help.Oct 9 2016, 5:33 PM

Have you tried clearing your cache and cookies? Also before we move on what browser and Operating System are you currently using when this error appears?

I don't tried. Win 8.1, Chrome.

Try clearing cache and cookies. Then tell me if it still gives you the error message! Thanks!

I have cleared my cache, the problem persisted. Will now clean the cookies and post an update later.

Nope, the error is still there. Win 8.1, Firefox 47.0

Even when I open a private/incognito window, log in and then try to roll something back, I see the error message.

I'll look into this I'm not assiging myself because this may be a mw/config issue

Zppix added a project: MediaWiki-libs-Rdbms.

Not a config issue I will be looking into this further, I'm assuming it may be a bad cookie, a sql error, or something to do with the auth manager/session manager

Zppix removed Zppix as the assignee of this task.Oct 19 2016, 10:12 PM

Sorry, for the delay but I cannot find a reason on why it won't work. So im unassigning myself

I'm sorry, this bug was caused by buggy userscript too.