Lemmy

12524 readers

19 users here now

Everything about Lemmy; bugs, gripes, praises, and advocacy.

For discussion about the lemmy.ml instance, go to !meta@lemmy.ml.

founded 4 years ago

MODERATORS

nutomic@lemmy.ml

Being logged out on refresh, Firefox (lemmy.ml)

submitted 1 year ago* (last edited 1 year ago) by nik282000@lemmy.ml to c/lemmy@lemmy.ml

5 comments fedilink hide all child comments

I am experiencing weird behavior on both lemmy.ml and lemmy.ca where refreshing, or closing and reopening my browser, will cause me to be logged out. This seems to be an issue with my browser, Firefox 102.13 on Debian Bookworm, but it does not happen with any other sites with logins. I have tried clearing cookies and site data but nothing changed. I have also tried with Chromium and the problem does not occur so this is related to Firefox or some setting within.

If any one has experienced the same or has an idea what setting might be causing this I'd love to hear from you.

Regardless, thanks for the platform!

edit: ~~Just to fuck with me, after a week of consistent "refresh -> logout" the behaviour is no longer reproducible.~~ Still being logged out if I refresh or close/open the browser. The internet is cruel, laughs at you when you are naked, but you keep coming back for more, and more! Why? Because she is the only prostitute I can afford.

top 5 comments

sorted by: hot top controversial new old

[–] sabreW4K3@lemmy.tf 4 points 1 year ago (1 children)

What extensions are you running?

[–] nik282000@lemmy.ml 1 points 1 year ago

Good point, I'm running uBlock and NewTab. uBlock is blocking a single request/element from startrek.website but that's it.

[–] nachtigall@feddit.de 3 points 1 year ago

Same with Safari

[–] 0v0@sopuli.xyz 3 points 1 year ago (1 children)

I occasionally experience the same thing. When this happens, it appears the jwt token is not sent with the initial request (thus appearing to be logged out), but it is sent with api requests on the same page (unread_count, list, etc.), so the cookie is not lost (document.cookie also shows it). Sometimes refreshing again fixes it, but I haven't yet found a good workaround. I'll experiment a bit next time it happens.

[–] nik282000@lemmy.ml 1 points 1 year ago

Thanks, that gives me a direction for searching.