Proxmox VNC "Failed to connect to server"
- Thread starter marciglesias17
- Start date
hi,
Please post output of command:
Also check if there any firewall or antivirus that not allow TLS traffic
Please post output of command:
pveversion -vAlso check if there any firewall or antivirus that not allow TLS traffic
pveversion -v
proxmox-ve: 6.2-1 (running kernel: 5.4.34-1-pve)
pve-manager: 6.2-4 (running version: 6.2-4/9824574a)
pve-kernel-5.4: 6.2-1
pve-kernel-helper: 6.2-1
pve-kernel-5.4.34-1-pve: 5.4.34-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
libproxmox-acme-perl: 1.0.3
libpve-access-control: 6.1-1
libpve-apiclient-perl: 3.0-3
libpve-common-perl: 6.1-2
libpve-guest-common-perl: 3.0-10
libpve-http-server-perl: 3.0-5
libpve-storage-perl: 6.1-7
libqb0: 1.0.5-1
libspice-server1: 0.14.2-4~pve6+1
lvm2: 2.03.02-pve4
lxc-pve: 4.0.2-1
lxcfs: 4.0.3-pve2
novnc-pve: 1.1.0-1
proxmox-mini-journalreader: 1.1-1
proxmox-widget-toolkit: 2.2-1
pve-cluster: 6.1-8
pve-container: 3.1-5
pve-docs: 6.2-4
pve-edk2-firmware: 2.20200229-1
pve-firewall: 4.1-2
pve-firmware: 3.1-1
pve-ha-manager: 3.0-9
pve-i18n: 2.1-2
pve-qemu-kvm: 5.0.0-2
pve-xtermjs: 4.3.0-1
qemu-server: 6.2-2
smartmontools: 7.1-pve2
spiceterm: 3.1-1
vncterm: 1.6-1
zfsutils-linux: 0.8.3-pve1
Hi,
Thank you
the packages look good.
Other things is there any error on your browser console javascript?
You can see that by open Ctrl + Shift + k on Firefox and Ctrl + Shift + j on Chrome
Thank you
the packages look good.I asked if there any firewall or something that not allow TLS traffic, but you didn't answer.
Other things is there any error on your browser console javascript?
You can see that by open Ctrl + Shift + k on Firefox and Ctrl + Shift + j on Chrome
hi,
like i said before check if there is any virus scanner or firewall on your network even plugins on the browser that take kind of traffic.
Try to open novnc on different browser/system.
I hope that helps
like i said before check if there is any virus scanner or firewall on your network even plugins on the browser that take kind of traffic.
Try to open novnc on different browser/system.
I hope that helps
@marc.iglesias17
follow the link explaining this solved for me
https://mindnotes.sh/proxmox-migration-aborted/
I believe that the same error when trying to migrate this is due to the ssh key as I understand it ..
Hello,
I think, its a problem from keys, when connect in to VNC with Proxmox GUI of another server of cluster dont works, but when connect directly from this servers VNC works.
I think, its a problem from keys, when connect in to VNC with Proxmox GUI of another server of cluster dont works, but when connect directly from this servers VNC works.
this command generates new public keys, from one node to another via ssh, you have an access key, the specified command, resolve in my senario. Every time you remove and add a new cluster it does this. because I do not change ip only the hostname of the new one in
Hello @Psydown
Thanks, but i prefer verify with Staff, i have more servers in production.
Appears this message:
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
@ WARNING: REMOTE HOST IDENTIFICATION HAS CHANGED! @
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
IT IS POSSIBLE THAT SOMEONE IS DOING SOMETHING NASTY!
Someone could be eavesdropping on you right now (man-in-the-middle attack)!
...
Thanks, but i prefer verify with Staff, i have more servers in production.
Appears this message:
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
@ WARNING: REMOTE HOST IDENTIFICATION HAS CHANGED! @
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
IT IS POSSIBLE THAT SOMEONE IS DOING SOMETHING NASTY!
Someone could be eavesdropping on you right now (man-in-the-middle attack)!
...
very good this command in .. thanks for the help i will test it when I have the problem again. I generated the ssh certificates on the defective node
as I understand it this command does it all automatically ..
Using this command fixed this problem for one of the nodes of my "homelab" cluster. Thank you very much.