Page MenuHomePhabricator

Wikiapiary Session problems: can't edit due to loss of session data. If trying to login from a new browser, says cookies are disabled
Closed, ResolvedPublic

Assigned To
Authored By
Ciencia_Al_Poder
Mar 29 2018, 9:44 AM
Referenced Files
None
Tokens
"Like" token, awarded by Kghbln."Like" token, awarded by Liuxinyu970226."Burninate" token, awarded by Ciencia_Al_Poder."Like" token, awarded by Samwilson.

Description

When trying to save an edit I get an error: Lo sentimos, no hemos podido procesar tu edición debido a una pérdida de los datos de sesión. Por favor, inténtalo de nuevo. Si el problema persiste, prueba a cerrar sesión y volver a acceder. (the standard error about loss of session data).

Trying to login on a private window, I get an error saying I must enable cookies (they are enabled)

Event Timeline

@MarkAHershberger It will be really great if you had a peep at this. Thanks and cheers.

I am unable to log in as well. The login form is has a link to log in via HTTPS (as though it doesn't know that it already is).

Don't know if it's related, but https://www.wikiapiary.com is giving a certificate error (it's only valid for the non-www domain).

The login form is has a link to log in via HTTPS (as though it doesn't know that it already is).

MediaWiki displays that link when it detects the user is coming from HTTP. But that could happen if your wiki endpoint is published through HTTPS but it's a proxy to an internal HTTP backend (varnish doesn't support HTTPS for example). I have also this "problem" in my wiki. I'll probably find time some day to report this.

Don't know if it's related, but https://www.wikiapiary.com is giving a certificate error (it's only valid for the non-www domain).

It's not related. It may be worth a new bug report for that. The certificate should include 2 domains: wikiapiary.com and *.wikiapiary.com or www.wikiapiary.com.

Also reported at https://www.mediawiki.org/wiki/Topic:Ubb4rq1ajetfbxc2

Could this be something to do with session storage (out of space etc.)?

(I've created T192226 for the certificate error. Thanks. Sorry to conflate things here. :) )

Could this be something to do with session storage (out of space etc.)?

Yes, most likely session storage is read-only or can't allocate more space.

MarkAHershberger claimed this task.

Sorry for taking so long on this. I switched from Jamie's use of Redis for an objectcache to memcache.

It seems to be working now.