[SOLVED] Web interface requires re-login at regular intervals even with activity

[Chicken76]

I've installed the latest Proxmox VE on a new machine and the web interface keeps kicking me out. It's not the inactivity timeout, because it kicks me out even when I click something different every 3 seconds.
I've looked at this problem reported in the past and most times it's been clock/time problems. I've checked mine (including hwclock) and everything seems fine. This machine is standalone and has local storage.


Inspecting the webpage in my browser I found this:

Cookie “PVEAuthCookie” will be soon rejected because it has the “SameSite” attribute set to “None” or an invalid value, without the “secure” attribute. To know more about the “SameSite“ attribute, read https://developer.mozilla.org/docs/Web/HTTP/Headers/Set-Cookie/SameSite

Could this be the issue?

 

[Moayad]

Hi,

Have you tried to use a different browser or private/incognito? what is a version of your FIreFox?

 

[dcsapak]

hi, whats your 'pveversion -v' ? we already set the 'secure' attribute of the cookie.... do you have any proxy or something like that in between?

 

[Chicken76]

Hi,

Have you tried to use a different browser or private/incognito? what is a version of your FIreFox?

I have tried the current Firefox version of 97.0.2 and Chrome on Windows and also Firefox on Linux. All showing the same behavior.
In a Private Window, the console doesn't show that error, but it still locks me out while I'm using the interface.

 

[Chicken76]

hi, whats your 'pveversion -v' ? we already set the 'secure' attribute of the cookie.... do you have any proxy or something like that in between?

proxmox-ve: 7.1-1 (running kernel: 5.13.19-4-pve)
pve-manager: 7.1-10 (running version: 7.1-10/6ddebafe)
pve-kernel-helper: 7.1-12
pve-kernel-5.13: 7.1-7
pve-kernel-5.13.19-4-pve: 5.13.19-9
pve-kernel-5.13.19-2-pve: 5.13.19-4
ceph-fuse: 15.2.15-pve1
corosync: 3.1.5-pve2
criu: 3.15-1+pve-1
glusterfs-client: 9.2-1
ifupdown2: 3.1.0-1+pmx3
ksm-control-daemon: 1.4-1
libjs-extjs: 7.0.0-1
libknet1: 1.22-pve2
libproxmox-acme-perl: 1.4.1
libproxmox-backup-qemu0: 1.2.0-1
libpve-access-control: 7.1-6
libpve-apiclient-perl: 3.2-1
libpve-common-perl: 7.1-3
libpve-guest-common-perl: 4.1-1
libpve-http-server-perl: 4.1-1
libpve-storage-perl: 7.1-1
libspice-server1: 0.14.3-2.1
lvm2: 2.03.11-2.1
lxc-pve: 4.0.11-1
lxcfs: 4.0.11-pve1
novnc-pve: 1.3.0-2
proxmox-backup-client: 2.1.5-1
proxmox-backup-file-restore: 2.1.5-1
proxmox-mini-journalreader: 1.3-1
proxmox-widget-toolkit: 3.4-6
pve-cluster: 7.1-3
pve-container: 4.1-4
pve-docs: 7.1-2
pve-edk2-firmware: 3.20210831-2
pve-firewall: 4.2-5
pve-firmware: 3.3-5
pve-ha-manager: 3.3-3
pve-i18n: 2.6-2
pve-qemu-kvm: 6.1.1-2
pve-xtermjs: 4.16.0-1
qemu-server: 7.1-4
smartmontools: 7.2-1
spiceterm: 3.2-2
swtpm: 0.7.0~rc1+2
vncterm: 1.7-1
zfsutils-linux: 2.1.2-pve1

I do have a proxy. I'll access the web interface directly and report back. Does accessing via dns name or ip address make a difference?

 

[dcsapak]

I do have a proxy. I'll access the web interface directly and report back.

yes, please do that

Does accessing via dns name or ip address make a difference?

no that should not make a difference

 

[Chicken76]

I can confirm accessing the web interface without going through a proxy does solve the automatic logout problem. Thank you for all the support, I would not have guessed that the proxy was the culprit.
Will mark thread as solved.