error on console

informant

Renowned Member
Jan 31, 2012
762
10
83
Hi, i have a new node add to my cluster and i can not connect with console to vms on this new node, i have the error:
Code:
TASK ERROR: command '/bin/nc6 -l -p 5900 -w 10 -e '/usr/bin/ssh -T -o BatchMode=yes 10.0.0.12 /usr/sbin/qm vncproxy 100 2>/dev/null'' failed: exit code 1
only "starting vnc handshake" comes in window.

command pvecm updatecerts --force:
Code:
 pvecm updatecerts --force
Signature ok
subject=/OU=PVE Cluster Node/O=Proxmox Virtual Environment/CN=prometheus.speedloc.de
Getting CA Private Key
CA certificate and CA private key do not match
140489327224464:error:0B080074:x509 certificate routines:X509_check_private_key:key values mismatch:x509_cmp.c:330:
unable to generate pve ssl certificate:
command 'openssl x509 -req -in /tmp/pvecertreq-5815.tmp -days 3650 -out /etc/pve/nodes/prometheus/pve-ssl.pem -CAkey /etc/pve/priv/pve-root-ca.key -CA /etc/pve/pve-root-ca.pem -CAserial /etc/pve/priv/pve-root-ca.srl -extfile /tmp/pvesslconf-5815.tmp' failed: exit code 1

What can i do here? all other nodes are working fine with console. i need help please.

best regards
 
Last edited:
More Info about ssl cert -> https://www.digicert.com/help/ said all are ok on node and cluster, but why console does not work on this new node? any ideas - please?

if i use command in console, its comes:
Code:
/bin/nc6 -l -p 5900 -w 10 -e '/usr/bin/ssh -T -o BatchMode=yes 10.0.0.12 /usr/sbin/qm vncproxy 100'
nc6: connection timed out

and

/bin/nc -l -p 5900 -w 10 -e '/usr/bin/ssh -T -o BatchMode=yes 10.0.0.12 /usr/sbin/qm vncproxy 100'
nc: connection timed out

Proxmox was installed with ISO DVD and updatet to last version. it is a problem with ipv6 in lat proxmox version? i connect with ipv4-client.

Code:
pveversion -v
proxmox-ve: 4.1-28 (running kernel: 4.2.6-1-pve)
pve-manager: 4.1-2 (running version: 4.1-2/78c5f4a2)
pve-kernel-4.2.6-1-pve: 4.2.6-28
pve-kernel-4.2.2-1-pve: 4.2.2-16
lvm2: 2.02.116-pve2
corosync-pve: 2.3.5-2
libqb0: 0.17.2-1
pve-cluster: 4.0-29
qemu-server: 4.0-42
pve-firmware: 1.1-7
libpve-common-perl: 4.0-42
libpve-access-control: 4.0-10
libpve-storage-perl: 4.0-38
pve-libspice-server1: 0.12.5-2
vncterm: 1.2-1
pve-qemu-kvm: 2.4-18
pve-container: 1.0-35
pve-firewall: 2.0-14
pve-ha-manager: 1.0-16
ksm-control-daemon: 1.2-1
glusterfs-client: 3.5.2-2+deb8u1
lxc-pve: 1.1.5-5
lxcfs: 0.13-pve2
cgmanager: 0.39-pve1
criu: 1.6.0-1
zfsutils: 0.6.5-pve6~jessie

a very old artical was here http://blog.stalkr.net/2010/02/proxmox-kvm-reach-vnc-in-ipv6.html but i hope, you have a solution or a idea for my problem.

regards
 
Last edited:
Hi, a new information. if the node was clean installed, console works fine, if new node was add to existing cluster, console does not work.

if i connect to console over cluster url (https://cluster-url:8006), console does not work, if i connect to console over node host (https://node-url:8006), console works fine, if i connect over node url to a console of a other node, it does doent work, too. only console on local host works - why this? whats wrong here?

what can i do here? please help. thanks and regards
 
Last edited:
i have test a ssh connect on console and found the error, a old ssh_key was on cluster, i have remove it and set it new, it works fine after this. for all other, they have the same error, clean ssh_keys on cluster in root dir and set it new, after it works fine.

regards
 

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!