Console disconnecting

[NEFF]

Interupts NoVNC and xterm.js
spice not tested. Tested only on WIN machines and node Debeian.
Sometimes it possible to see win setup screen for a few secs )
ProxMox deployed from standard OVH template on OVH server.
I understand, that something wrong with certificates, many times was running all from begin, followed lot of rtfms and spent 40+ hrs on this, I cant more )

P.S. no, changing browsers, private mode and cache cleaning changes nothing.


----------------------------------------
Virtual Environment 5.2-5
Node 'proxmox02'
CPU usage

1.09% of 8 CPU(s)

IO delay

0.21%
Load average

0.04,0.09,0.05
RAM usage

28.58% (8.88 GiB of 31.07 GiB)

KSM sharing

0 B
HD space(root)

14.59% (2.79 GiB of 19.10 GiB)

SWAP usage

0.00% (0 B of 2.00 GiB)
CPU(s)

8 x Intel(R) Xeon(R) CPU E3-1270 v6 @ 3.80GHz (1 Socket)
Kernel Version

Linux 4.15.18-1-pve #1 SMP PVE 4.15.18-15 (Wed, 04 Jul 2018 15:42:56 +0200)
PVE Manager Version

pve-manager/5.2-5/eb24855a
Logs
()

proxmox-ve: 5.2-2 (running kernel: 4.15.18-1-pve)
pve-manager: 5.2-5 (running version: 5.2-5/eb24855a)
pve-kernel-4.15: 5.2-4
pve-kernel-4.15.18-1-pve: 4.15.18-15
corosync: 2.4.2-pve5
criu: 2.11.1-1~bpo90
glusterfs-client: 3.8.8-1
ksm-control-daemon: 1.2-2
libjs-extjs: 6.0.1-2
libpve-access-control: 5.0-8
libpve-apiclient-perl: 2.0-5
libpve-common-perl: 5.0-35
libpve-guest-common-perl: 2.0-17
libpve-http-server-perl: 2.0-9
libpve-storage-perl: 5.0-24
libqb0: 1.0.1-1
lvm2: 2.02.168-pve6
lxc-pve: 3.0.0-3
lxcfs: 3.0.0-1
novnc-pve: 1.0.0-1
proxmox-widget-toolkit: 1.0-19
pve-cluster: 5.0-28
pve-container: 2.0-24
pve-docs: 5.2-4
pve-firewall: 3.0-13
pve-firmware: 2.0-5
pve-ha-manager: 2.0-5
pve-i18n: 1.0-6
pve-libspice-server1: 0.12.8-3
pve-qemu-kvm: 2.11.2-1
pve-xtermjs: 1.0-5
qemu-server: 5.0-29
smartmontools: 6.5+svn4324-1
spiceterm: 3.0-5
vncterm: 1.5-3


Jul 14 18:03:38 proxmox02 pvedaemon[4047]: starting vnc proxy UPIDroxmox02:00000FCF:0001D8A2:5B4A3AFA:vncproxy:100:root@pam:
Jul 14 18:03:39 proxmox02 pveproxy[2183]: worker exit
Jul 14 18:03:39 proxmox02 pveproxy[2182]: worker 2183 finished
Jul 14 18:03:39 proxmox02 pveproxy[2182]: starting 1 worker(s)
Jul 14 18:03:39 proxmox02 pveproxy[2182]: worker 4073 started
Jul 14 18:03:40 proxmox02 pveproxy[2184]: problem with client 210.24x.xx.xx; ssl3_read_bytes: sslv3 alert bad certificate
Jul 14 18:03:40 proxmox02 pvedaemon[2131]: <root@pam> end task UPIDroxmox02:00000FCF:0001D8A2:5B4A3AFA:vncproxy:100:root@pam: OK
Jul 14 18:04:00 proxmox02 systemd[1]: Starting Proxmox VE replication runner...
Jul 14 18:04:00 proxmox02 systemd[1]: Started Proxmox VE replication runner.
Jul 14 18:04:13 proxmox02 sshd[4144]: Did not receive identification string from 87.25x.xx.xx port 51106
Jul 14 18:04:16 proxmox02 sshd[4146]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=87.25x.xx.xx user=root
Jul 14 18:04:18 proxmox02 sshd[4146]: Failed password for root from 87.25x.xx.xx port 51152 ssh2
Jul 14 18:04:18 proxmox02 sshd[4146]: Received disconnect from 87.25x.xx.xx port 51152:11: Bye Bye [preauth]
Jul 14 18:04:18 proxmox02 sshd[4146]: Disconnected from 87.25x.xx.xx port 51152 [preauth]
Jul 14 18:04:26 proxmox02 pveproxy[2184]: problem with client 210.24x.xx.xx; ssl3_read_bytes: sslv3 alert bad certificate
Jul 14 18:05:00 proxmox02 systemd[1]: Starting Proxmox VE replication runner...
Jul 14 18:05:00 proxmox02 systemd[1]: Started Proxmox VE replication runner.
Jul 14 18:06:00 proxmox02 systemd[1]: Starting Proxmox VE replication runner...
Jul 14 18:06:00 proxmox02 systemd[1]: Started Proxmox VE replication runner.