Just starting this week, when I first visit lemm.ee, I used to be logged in auytomatically, every time, but now I have to manually choose to login. My browser (Firefox on Ubuntu) definitely knows my username and password still.
Then, I can click around, go from page to page as I want, but if I hit F5 to refresh the page, or right click and choose the reload icon, I do get the page reloaded, but now I am not logged in.
I’ve tried disabling my (5) extensions but still saw this issue.
I tried completely erasing my cache in Firefox. Same issue still.
ETA: I tried explicitly logging out and logging back in (again). Same issue still.
This is only happening on lemm.ee.
Any ideas why Lemme doesn’t want to keep me logged in?
Thanks!
ETA – Thursday night: I made sure I am clearing cookies along with the cache. The problem remains. And, as @yogurt@lemm.ee said, the expiration date on the “jwt” cookie lemmee sets does expire in 3023. I installed an extension so I could edit that, set it to 2Dec 13 2025, saved the cookie. But still refreshing the page causes me to be logged out. This is just an annoyance at this point, not a big deal, but some sort of resolution eventually would be great. Thanks for any other ideas.
Can you try clearing all your cookies & then logging in again? I’m not sure if clearing the cache also clears cookies in Firefox.
In desktop Firefox new cookies are being set to expire in 3023, and going into inspect and setting the cookie to a shorter expiration fixes it. In Chrome long cookies are auto shortened to 400 days.
Strangely enough, this has been happening to me when visiting hexbear.net through Firefox. (I haven’t tried other instances or browsers.) It hasn’t annoyed me enough (yet!) to look into it, but since you mentioned it, I wanted to chime in and say it’s not just you.
Edit: I saw this last night as I was falling asleep and didn’t reply then, and when I went looking for the post this morning to respond, I found one by another user on another instance with the same problem.
Hey thanks. I guess it’s good it’s not just me. I’ll keep poking around here to see what I can figure out. Defintely has to do with the “jwt” cookie set on logging in, and maybe with its 3023 expiration date (though I don’t know why that’s an issue specifically still). Gotta be an answer here somewhere.