Issue staying logged into XO (source)

tsettle

Just updated XO for the first time in a year and have been getting 'kicked out' of XO on the regular. Cleared cache and cookies. Tried private/incognito. No change.

Developer console not giving me much of anything, but here's a screenshot.

.

Sometimes it'll keep me logged in for hours, other times not very long at all. The latest, I logged in last night and it stayed logged in. Checked my backups and puttered around a bit this morning, but when I went back to it, I was logged out.

Tried finding anything useful in the server logs (journalctl & /var/log/messages) but nothing is jumping out at me. Here's the last few log entries (all entries after the backup job, before having to log back in):

Nov  9 07:30:20 xo.mydomain.com xo-server[949]: 2023-11-09T12:30:20.263Z xo:main INFO + Console proxy (troy - ::ffff:192.168.12.34)
Nov  9 07:30:20 xo.mydomain.com xo-server[949]: 2023-11-09T12:30:20.497Z xo:main INFO - Console proxy (troy - ::ffff:192.168.12.34)
Nov  9 07:30:21 xo.mydomain.com xo-server[949]: 2023-11-09T12:30:21.616Z xo:main INFO + Console proxy (troy - ::ffff:192.168.12.34)
Nov  9 07:40:26 xo.mydomain.com xo-server[949]: 2023-11-09T12:40:26.186Z xo:main INFO - Console proxy (troy - ::ffff:192.168.12.34)
Nov  9 07:40:31 xo.mydomain.com xo-server[949]: 2023-11-09T12:40:31.625Z xo:main INFO + Console proxy (troy - ::ffff:192.168.12.34)
Nov  9 08:15:55 xo.mydomain.com xo-server[949]: 2023-11-09T13:15:55.723Z xo:main INFO - Console proxy (troy - ::ffff:192.168.12.34)
Nov  9 12:08:24 xo.mydomain.com xo-server[949]: 2023-11-09T17:08:24.465Z xo:xo-server-auth-ldap INFO successfully bound as CN=Troy Settle,OU=Users,OU=MCD,DC=mydomain,DC=com => troy authenticated

If this is a potential bug, I'm more than happy to spend some time chasing it, but either way, I kind of need an idea of what to start looking at.

OS: Alma Linux 8.8
Node: 16.20.2 (updated with the XO installer script)
Previous XO: 7e4f4c from Nov 8, 2022
Current XO: db99a from Nov 3, 2023

Not sure what other info to provide or what other questions to ask.

Thanks!

Danp

@tsettle use Node 18

olivierlambert

Yes, and also prefer to use XO web in HTTPS

tsettle

@Danp

Well that's a kick in the pants. When I ran the script last week, it said it was updating node, but I didn't pay attention. Apparently, the update failed silently. Today it was noisy and ended up having to update node manually. We'll see how it goes. Looks like Roni is already aware of issues with his script where node is concerned.

@olivierlambert

I thought it was until I started poking at it this morning (was going to clear the cert along with the cookies and cache). Doesn't look like Roni's script takes care of that though, so maybe someday...

Thanks guys!

olivierlambert

I think using a script for an initial test is OK, but if you want to really use it, it's better to follow our documentation and following the per-requisites by the book.