tlsv1 alert unknown ca

[jeller]

thousands of lines with

Nov 16 07:30:17 10.160.5.11 pveproxy[88404]: problem with client 10.160.5.12; ssl3_read_bytes: tlsv1 alert unknown ca
Nov 16 07:30:17 10.160.5.11 pveproxy[88404]: Can't call method "timeout_reset" on an undefined value at /usr/share/perl5/PVE/HTTPServer.pm line 225.

inside syslog

this message "tlsv1 alert unknown ca" everytime shown as a pop up alert on the web-gui

 

[manu]

Hi
Are you using official SSL certs or the default self-signed from the standard installation ?

 

[jeller]

Hi
Are you using official SSL certs or the default self-signed from the standard installation ?

Proxmox Cluster is use the default self-signed from the standard installation

 

[silverado]

I'm having the same problem with a fresh installed Proxmox 4.1 using the default self signed certificates. As a result the console window of virtual machines "flickers" in my browser, that means after a few seconds it starts to connect and disconnect quickly several times and then gets finally disconnected with error 1006. When I replace the certificates with certificates of my own private ca (that work perfectly in all the other servers that I use) the log says that these certificates are not okay; the behavior of the console stays the same.

I have no idea what is going on and how to fix it. Any help would be appreciated.

 

[tom]

virtual machines "flickers" in my browser

What browser do you use? Which OS do you run on your desktop?

 

[silverado]

What browser do you use? Which OS do you run on your desktop?

Tested with Win7 and 8, Firefox, PaleMoon, Chrome.

As I already said: "Flickering" means that after a few seconds the console disconnects and reconnects very quickly before it finally disconnects.

The syslog repeats lots of lines like these::

Dec 21 00:49:10 server2 pveproxy[2221]: problem with client 192.168.2.113; ssl3_read_bytes: tlsv1 alert unknown ca
Dec 21 00:49:10 server2 pveproxy[2221]: proxy detected vanished client connection

 

[silverado]

Now I reinstalled on the same hardware using the same procedure I used last time (installed a fully encrypted Debian 8.2 64 bit first, then installed Proxmox on top of it). The only difference is that I used ext3 instead of ext4. Now the problem seems to be gone. Fingers crossed...