Site keeps logging me out all the sudden...

[nuke]

Last several says, I log in, read a message or two, and the site logs me back out. I click the "keep me logged in" checkbox to no avail. Logged out and back in, erased all cookies associated with this site, but it keeps happening.

No problem logging back in, but it is annoying.

Any idea what's going on?

[keithrick]

No answers other then I am experiencing the same issue. I'm following this thread.

[martin manning]

Same.

[pompeiisneaks]

best guess on that is there's some kind of cookie problem with your browser. For giggles try logging in with a different browser or in 'incognito' mode and see if it persists.

If you use chrome, try edge, or on mac safari, or maybe even firefox. often there are browser caching issues where things like that can happen. If it's more widespread I can see if there's something going on with the database.

~Phil

[pompeiisneaks]

or, better, report back with which browser you use and that may narrow down the culprit.

I'm not seeing it and I'm on chrome on windows.

~Phil

[xtian]

No issue experienced on Safari, desktop nor mobile.

[martin manning]

I am on Safari. Cleared history and it seems better, but still dropping me fairly regularly.

[pompeiisneaks]

Although I can find no smoking gun, almost all the posts I find about this seem to link back to a couple of reasons, and both seem to tie to the hosting provider doing things badly. This is not a shock, as we've had problems with the hosting provider for the site for years. Best guess either links it to problems with IPv6 being 'enabled' at the hosting provider but being somewhat inconsistent and falling back to IPv4 and then returning to IPv6. Which IS and IP address change, and therefore your session is from a 'new' address and needs to re-authenticate. another option is if they use poorly configured transparent proxies in the mix, which they may have decided to add recently and is causing this as well. Not sure if it's either, but so far that's about all i can find that 'might' be the cause.

~Phil

[nuke]

Safari, Mac, Tahoe 26.5.2 (latest).

I'll try from other systems/browsers.

[nuke]

Seems possibly better on Google Chrome than Safari on the same Mac. Also seems better on Safari on the iPhone.

[didit]

Hello --

I've had no troubles with this particular glitch.

Best guess either links it to problems with IPv6 being 'enabled' at the hosting provider but being somewhat inconsistent and falling back to IPv4 and then returning to IPv6. Which IS and IP address change, and therefore your session is from a 'new' address and needs to re-authenticate. another option is if they use poorly configured transparent proxies in the mix, which they may have decided to add recently and is causing this as well.

Both make sense to me. The v6 vs v4 twitching in particular fits with a pattern of some folk having persistent issues and others not seeing it all. Assuming it is the root cause, browsers aren't implicates -- just the IP connectivity providers.

..

[nuke]

Wouldn't IPv4 vs IPv6 affect all browsers from the same computer?

I'm not seeing it on Chrome, on the same computer as Safari, not seeing it on Chrome (hope I didn't jinx it).

[didit]

Wouldn't IPv4 vs IPv6 affect all browsers from the same computer?

I'm not seeing it on Chrome, on the same computer as Safari, not seeing it on Chrome (hope I didn't jinx it).

That would definitely confound. That is, unless either Chrome or Safari makes some form of assertive selection of one or the other vs leaving it to machinations under OS hood. It’s been too long since I coded in MacOS IP networking to remember what controls there were, and besides the system APIs have doubtless evolved. Sorry for a less than certain answer.

..

[didit]

Adding another half-baked thought --

Through their extensive backbone networking systems (largest single-owner slice of Internet capacity on the planet) Google has unique visibility into the state of the global forwarding systems. I'm skeptical that Chrome has any active access but I would not be surprised if the browser developers get helpful input from the netOps people on best methods for achieving "happy eyeballs".

..

[nuke]

That would definitely confound. That is, unless either Chrome or Safari makes some form of assertive selection of one or the other vs leaving it to machinations under OS hood. It’s been too long since I coded in MacOS IP networking to remember what controls there were, and besides the system APIs have doubtless evolved. Sorry for a less than certain answer.

..

Weirdly, both Chrome and Safari use Webkit.

I wonder if there's something with Apple's privacy scheme going on to subvert trackers in Safari.