I noticed this yesterday. It appears that for some short period of inactivity (a half hour or less) my login is being timed out so that I have to log back in. That is a bit annoying but was tolerable if I was truly inactive.

Today however, I was posting a detailed reply to a thread and on clicking submit it instead took me to the login page. Presumably this is because I hit whatever timeout limit is now in place. Of course the detail I was writing was lost.

Our internal security person says no such timeout has been implemented on our end.

To stay logged in your must check the "Remember Me" box and ensure your browser is accepting cookies (and that no proxy is deleting or altering them en route).

--jeremy

I haven't changed anything in browser settings recently (in fact I've been ignoring nag alerts telling me to update Firefox) and do always leave "remember me" checked because that is the default.

Did something change in the way LQ is "remembering me" recently?

I can confirm that nothing has changed on our end (and that I have not experienced the issue). Are any other members seeing this behavior?

--jeremy

Yes, it's been happening to me a lot today. I was using Debian with Firefox 48, if that's relevant.

1 members found this post helpful.

Can you try completely removing all LQ-related cookies and then logging in with the "Remember Me" box checked? Have either of you installed any addons or upgraded browsers recently?

--jeremy

Nope! But it happened again, this time on LFS, so it's unlikely to be the specific browser that's doing it. I've just deleted LQ cookies. We shall see!

1 members found this post helpful.

I have my browser setup so it deletes all history including cookies on close and I'm seeing this timeout even between reboots.

I'm using Firefox 49 on Windows 7 at the moment. As noted previously I've done no updates to the browser recently.

I did update Flash player within the last week or so. Usually when I do that I delete all history it contains but I expect it to start adding information on new access. On checking today it shows I'm using the latest version for my system.

I have encountered this issue today on both Vivaldi 1.4.586 and Firefox 50.1.0. In fact, when I tried to submit the first version of this post, I got a message telling me that I was "not authorized" and had to log in to post. Vivaldi had not remembered my login from yesterday so I logged back in, but, when I clicked the title to read this thread, I was directed to a login dialog.

This was on Slackware --Current.

1 members found this post helpful.

Yes, I've been noticing it too. I've been auto logged out several times despite logging on with "Remember me" checked as I always do (I haven't changed anything that I can see may have precipitated this change).

I use Firefox 50.1 in Private Browsing mode.

1 members found this post helpful.

Same here for both firefox-50.1.0 and seamonkey-2.46.
Maybe it's related to the fact, that the logout page is garbled

1 members found this post helpful.

Today I tested using MS Edge from a separate Windows 10 system from my home network and saw the same timeout issue. This eliminates my work network, Firefox and Windows 7 which were what I was using when I first reported the issue.

Given this test and the fact that others are experiencing the issue on a variety of platforms it appears the issue is with LQ itself.

It's almost certainly not related to the logout page css issue. Can any member having the issue remove all LQ cookies again and log in? We've made a change on our end. I apologize for the inconvenience.

--jeremy

1 members found this post helpful.

Happy New Year!

It seems to be fixed now. Thanks

1 members found this post helpful.

Yup! I'm logged in and I last posted 3 hours ago.

1 members found this post helpful.