default gui session timeout

I

immo

Renowned Member
Nov 20, 2014
92
0
71
Hi folks,

Where do I find the default session timeout. I do have some clients which logout after less than 5 mins which is to short for them.

Immo
 
Hi, normally it's 2 hours, and as long as a client has the UI open we'll renew it every once and then, so that you could stay even longer.

We had once a problem where during updating pve-cluster any logged in client may received a 501 (HTTP UNAUTHORIZED), but that was fixed...
What's the nodes `pveversion -v` output?
 
root@prox03:~# pveversion -v
proxmox-ve: 5.1-38 (running kernel: 4.13.13-5-pve)
pve-manager: 5.1-43 (running version: 5.1-43/bdb08029)
pve-kernel-4.4.98-5-pve: 4.4.98-105
pve-kernel-4.2.3-2-pve: 4.2.3-22
pve-kernel-4.2.6-1-pve: 4.2.6-36
pve-kernel-4.4.13-1-pve: 4.4.13-56
pve-kernel-4.2.2-1-pve: 4.2.2-16
pve-kernel-4.2.8-1-pve: 4.2.8-41
pve-kernel-4.13.13-5-pve: 4.13.13-38
pve-kernel-4.4.59-1-pve: 4.4.59-87
libpve-http-server-perl: 2.0-8
lvm2: 2.02.168-pve6
corosync: 2.4.2-pve3
libqb0: 1.0.1-1
pve-cluster: 5.0-19
qemu-server: 5.0-20
pve-firmware: 2.0-3
libpve-common-perl: 5.0-25
libpve-guest-common-perl: 2.0-14
libpve-access-control: 5.0-7
libpve-storage-perl: 5.0-17
pve-libspice-server1: 0.12.8-3
vncterm: 1.5-3
pve-docs: 5.1-16
pve-qemu-kvm: 2.9.1-6
pve-container: 2.0-18
pve-firewall: 3.0-5
pve-ha-manager: 2.0-4
ksm-control-daemon: 1.2-2
glusterfs-client: 3.8.8-1
lxc-pve: 2.1.1-2
lxcfs: 2.0.8-1
criu: 2.11.1-1~bpo90
novnc-pve: 0.6-4
smartmontools: 6.5+svn4324-1
zfsutils-linux: 0.7.4-pve2~bpo9

could I check somehow the timesync for all hosts is ok ?
 
the timesync was not correct on one server. This seems to be an issue for the Windows hosted Webbrowsers Auth more than for Linux ones.
All are now in sync and everything is fine.
 
I'm new to Proxmox and I'm experiencing the same issue (really irritating, I admit).
I would be grateful for any help I could get to avoid getting logged out every 2 minutes or so.

This is my timedatectl -a output (it corresponds with the machin from which I log in from)
Local time: Sun 2020-05-31 12:40:40 CEST
Universal time: Sun 2020-05-31 10:40:40 UTC
RTC time: Sun 2020-05-31 10:40:40
Time zone: Europe/Paris (CEST, +0200)
System clock synchronized: yes
NTP service: inactive
RTC in local TZ: no
~#

and this is my pveversion -v output :
proxmox-ve: 6.1-2 (running kernel: 5.3.18-2-pve)
pve-manager: 6.1-7 (running version: 6.1-7/13e58d5e)
pve-kernel-helper: 6.1-9
pve-kernel-5.3: 6.1-5
pve-kernel-5.3.18-2-pve: 5.3.18-2
ceph-fuse: 12.2.11+dfsg1-2.1+b1
corosync: 3.0.3-pve1
criu: 3.11-3
glusterfs-client: 5.5-3
ifupdown: 0.8.35+pve1
ksm-control-daemon: 1.3-1
libjs-extjs: 6.0.1-10
libknet1: 1.15-pve1
libpve-access-control: 6.0-6
libpve-apiclient-perl: 3.0-3
libpve-common-perl: 6.0-13
libpve-guest-common-perl: 3.0-3
libpve-http-server-perl: 3.0-5
libpve-storage-perl: 6.1-5
libqb0: 1.0.5-1
libspice-server1: 0.14.2-4~pve6+1
lvm2: 2.03.02-pve4
lxc-pve: 3.2.1-1
lxcfs: 4.0.3-pve2
novnc-pve: 1.1.0-1
openvswitch-switch: 2.12.0-1
proxmox-mini-journalreader: 1.1-1
proxmox-widget-toolkit: 2.1-6
pve-cluster: 6.1-8
pve-container: 3.0-21
pve-docs: 6.1-6
pve-edk2-firmware: 2.20200229-1
pve-firewall: 4.1-2
pve-firmware: 3.0-7
pve-ha-manager: 3.0-9
pve-i18n: 2.1-1
pve-qemu-kvm: 4.1.1-4
pve-xtermjs: 4.3.0-1
qemu-server: 6.1-6
smartmontools: 7.1-pve2
spiceterm: 3.1-1
vncterm: 1.6-1
zfsutils-linux: 0.8.3-pve1



these are the latest entries in /var/log/pveproxy/access.log after getting logged out (sorry but I'm incapable of saying what is what, too many entries for me) :
192.168.1.72 - root@pam [31/05/2020:13:08:52 +0200] "GET /api2/json/nodes/prox/qemu/101/rrddata?timeframe=hour&cf=AVERAGE HTTP/1.1" 500 13
192.168.1.72 - root@pam [31/05/2020:13:08:52 +0200] "GET /api2/json/nodes/prox/status HTTP/1.1" 200 716
192.168.1.72 - - [31/05/2020:13:08:52 +0200] "GET /xtermjs/xterm.css?version=4.3.0-1 HTTP/1.1" 200 1768
192.168.1.72 - root@pam [31/05/2020:13:08:53 +0200] "POST /api2/json/nodes/prox/termproxy HTTP/1.1" 200 481
192.168.1.72 - root@pam [31/05/2020:13:08:53 +0200] "GET /api2/json/nodes/prox/vncwebsocket?port=5900&vncticket=PVEVNC%3A5ED39044%3A%3AZqVHEX8SKK8xwHION4Aa%2BQKzd8FgDbcI$
192.168.1.72 - root@pam [31/05/2020:13:08:54 +0200] "GET /api2/json/nodes/prox/status HTTP/1.1" 200 710
192.168.1.72 - root@pam [31/05/2020:13:08:55 +0200] "GET /api2/json/nodes/prox/status HTTP/1.1" 200 715
 
You must log in or register to reply here.
Top Bottom