Page MenuHomeMiraheze

Login error message
Closed, InvalidPublic

Description

For a while I'm getting this error before logging in, works the second time.
"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."

Event Timeline

Can confirm the same issue happens for me from time to time - is something caching?

NDKilla claimed this task.

Redis-server was dead for some reason. Will try to investigate the cause later.

For now just reopen and assign to me if logins fail.

Reception123 removed NDKilla as the assignee of this task.
Reception123 moved this task from Backlog to Bugs on the MediaWiki board.

As the last task that sort of included this issue was resolved (the one with session data) I am opening a new one. "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."
I get this error very frequently when trying to log in. As @John said I cleared my cookies, and that helped with the other errors but this one is still persistent.
As this "error" can be bypassed by just clicking "sign in" again I propose that we add "Please click Sign in again" below, as a few users were confused with what to do when this error happens.
Also get 504s (not sure if to create a separate task or not for that).

Amanda subscribed.

Can confirm that this is definitely happening frequently. Anyone have a link to the upstream task readily available?

Upon a discussion I got

<bawolff> It might be whereever your session is stored doesn't have enough space
If you're storing in memcached try giving it more memory
<Vulpix> redis
<bawolff> I don't know much about redis, but if you're redis as your session store I assume there's something similar about how much memory and cache eviction policy that can be adjusted

Maybe we should review our Redis settings?

Reception123 mentioned this in Unknown Object (Diffusion Commit).May 21 2017, 14:54
Reception123 claimed this task.

Along with all the annoying login issues that we're having, this is really one that I haven't seen in a while, and it hasn't been reported either so I'm going to resolve this task.

I see this problem frequently on nenawiki. Second attempt seems to always succeed.

Errors are reported again, best to keep open

John changed the task status from Open to Stalled.Aug 14 2017, 13:49
John lowered the priority of this task from Normal to Low.

This falls into the category of "upstream issue (by way of issue or support) which is getting no progress and even so, having a ticket in our tracker is literally pointless. This isn't causing major issues therefore, if we get rid of this ticket no one will really notice or care".