Check out our Monthly Survey Page to see what our users are running.
[FIXED] Login/cookie issues not fixed
TheSHEEEP commented on 17 December 2019 at 12:08 pm UTC

I just saw the other topic that this is supposedly resolved.
But it really isn't.

I had to login (via Steam) multiple times just in the last few hours.
This has always affected me.

What is extremely weird is that this happens multiple times per day (sometimes I get the impression it happens per visit, but not quite).
But only on my laptop (Ubuntu 18.04).
On my main rig (Manjaro), this never happens. Or it only happens once per month or so when I guess the Steam auth lifetime ends.
Both are active at the same time and use the same browser (Chrome) - could this "at the same time" be part of the problem?

I also use Chrome to sync open websites/account/etc. across devices, but afaik that does not include cookies, so it probably wouldn't affect this.
This is also the only website with that behavior.

Last edited by Liam Dawe on 19 December 2019 at 7:30 pm UTC

Liam Dawe commented on 17 December 2019 at 12:55 pm UTC

This might be specific to the Steam login then, the issue with the normal login seems to be fixed. I can see from your session DB info you indeed have had to. Will look into it, I'm now using the Steam login myself to help narrow it down.

TheSHEEEP commented on 17 December 2019 at 12:56 pm UTC

What confuses me most is really how this happens all the time on my laptop, but never on my PC.
What could even be the difference, given the browser is the same.

Liam Dawe commented on 17 December 2019 at 1:13 pm UTC

TheSHEEEPWhat confuses me most is really how this happens all the time on my laptop, but never on my PC.
What could even be the difference, given the browser is the same.
A plugin blocking cookies somewhere? I've known a few plugins prone to doing that without people knowing.

Liam Dawe commented on 17 December 2019 at 1:16 pm UTC

Next time it happens, tell me if the "gol_session" cookie actually still exists and the contents of it please. If so, that would mean the details changed somewhere and it's a case of things not communicating properly. If the cookie is fully gone, that's something removing it - there's nothing in the GOL code to remove that cookie until a manual logout.

TheSHEEEP commented on 17 December 2019 at 1:22 pm UTC

Liam Dawe
TheSHEEEPWhat confuses me most is really how this happens all the time on my laptop, but never on my PC.
What could even be the difference, given the browser is the same.
A plugin blocking cookies somewhere? I've known a few plugins prone to doing that without people knowing.
Could be possible, but Chrome also syncs plugins, so if that was a plugin it should also do it on the other machine.
Which plugins do you know that do it? Maybe it is one of mine.

I'll likely come back to this tomorrow as I'll be back on the laptop then...

Salvatos commented on 17 December 2019 at 4:22 pm UTC

I was away a few days last week and noticed a similar situation. Sessions don’t persist on my laptop for more than several minutes. I can close the browser window and come back and still be logged in, but any "natural" length of time between visits and I’m logged out. I’m using Firefox sync so I have the same extensions and settings on both computers, but my laptop is badly out of date so it could be something on my end. I’m using a straight GoL account, though.

I have two gol_session cookies, which is not the case on desktop.

Before login:
 {
  "name": "gol_session",
  "value": "d0fc08de8218929e93086436a6a57ff9",
  "domain": ".gamingonlinux.com",
  "hostOnly": false,
  "path": "/",
  "secure": true,
  "httpOnly": false,
  "session": false,
  "expirationDate": 1578240874,
  "storeId": "firefox-default",
  "sameSite": "no_restriction",
  "firstPartyDomain": ""
 },  {
  "name": "gol_session",
  "value": "kOmA7s%2Fwr5EX.3QzHpcmes9CK4ci1BYV9Uefd",
  "domain": "www.gamingonlinux.com",
  "hostOnly": true,
  "path": "/",
  "secure": true,
  "httpOnly": true,
  "session": false,
  "expirationDate": 1581462021,
  "storeId": "firefox-default",
  "sameSite": "no_restriction",
  "firstPartyDomain": ""
 }


After login:
 {
  "name": "gol_session",
  "value": "d0fc08de8218929e93086436a6a57ff9",
  "domain": ".gamingonlinux.com",
  "hostOnly": false,
  "path": "/",
  "secure": true,
  "httpOnly": false,
  "session": false,
  "expirationDate": 1578240874,
  "storeId": "firefox-default",
  "sameSite": "no_restriction",
  "firstPartyDomain": ""
 },
 {
  "name": "gol_session",
  "value": "nkS3GaEz4Op0.cLBhgYWQKCuRnhWiUzJYd%2FKn",
  "domain": "www.gamingonlinux.com",
  "hostOnly": true,
  "path": "/",
  "secure": true,
  "httpOnly": true,
  "session": false,
  "expirationDate": 1581782867,
  "storeId": "firefox-default",
  "sameSite": "no_restriction",
  "firstPartyDomain": ""
 } 


One of the two is httpOnly; I don’t know if that helps. I saved the rest of my cookies from these two snapshots in case you need them, but I figured I shouldn’t post a PHPSESSID publicly.

On desktop, for comparison:
 {
  "name": "gol_session",
  "value": "2%2Bdt9vaubjQP.jHTarNvKGbjfO0hNNO5Uyuw%2F",
  "domain": "www.gamingonlinux.com",
  "hostOnly": true,
  "path": "/",
  "secure": true,
  "httpOnly": true,
  "session": false,
  "expirationDate": 1581782205,
  "storeId": "firefox-default",
  "sameSite": "no_restriction",
  "firstPartyDomain": ""
 }

Liam Dawe commented on 17 December 2019 at 5:43 pm UTC

If you have a gol_session cookie that does not split the value with a dot, it's old and likely causing issues. Remove it.

Salvatos commented on 17 December 2019 at 6:22 pm UTC

Can confirm that removing that one and refreshing logged me in automatically. Hopefully the same goes for TheSHEEEP.

TheSHEEEP commented on 18 December 2019 at 8:43 am UTC

Confirmed and working now.
This old double gol_session was the problem.

Hopefully you can find a way to do this on the server-side. Maybe checking for double cookies and delete the one that does not have the dot.

Liam Dawe commented on 18 December 2019 at 9:49 am UTC

TheSHEEEPConfirmed and working now.
This old double gol_session was the problem.

Hopefully you can find a way to do this on the server-side. Maybe checking for double cookies and delete the one that does not have the dot.
Afraid not, if there's two cookies the same, there's no easy way to tell the difference. This was a booboo on my part, not renaming the new one. Will have to live and learn there, thankfully after a month or two the old one will vanish on its own since I don't give them a long life.

Will consider this solved

You need to Register and Login to comment, submit articles and more.


Or login with...

Livestreams & Videos
Community Livestreams
  • Story Time: „Unavowed“ (Wine)
Popular this week
View by Category
Contact
Latest Comments
Latest Forum Posts