New Proxmox build "failed to connect to server" novnc every time

[jamesisin]

I just built a new Proxmox host from the latest (yesterday) downloadable stable version. I uploaded the latest (LTS) Ubuntu ISO and created a VM for it.

I cannot install Ubuntu on that VM because every time (on three machines and two browsers) noVNC gives me the "Failed to connect to server" error.

I feel like this is something that should work out of the box. What's going on here?

 

[Moayad]

Hi,

Have you tried with Incognito/private browser or without plugins browser?

Did you configure Nginx Proxy on Proxmox VE?

Have you checked the firewall?

Do you have antivirus? - if yes may you disable it and try to open noVNC again.

 

[jamesisin]

Thanks, Moayad. No antivirus. No firewall (unless you mean a firewall within Proxmox itself?). Private browsing is the same and I use no plugins. I don't know anything about Nginx Proxy on Proxmox.

 

[Moayad]

Yes, I meant the firewall in Proxmox.

moe more question is the shell on the Datacenter => NodeName => Shell working or give you the same error?

Could you please renew the certificate of your Proxmox host by using the following command:

pvecm updatecerts -f

 

[jamesisin]

I haven't done anything with the Proxmox firewall so unless it does something out of the box that should be fine.

The node shell is working as expected (I used it specifically to issue the next command).

Running the pvecm update you provided made no difference to noVNC.

I'm wonder if this is a limitation of this old hardware. Is there a way to ask the hardware if it's virtualization compatible? I saw nothing to enable in the BIOS.

 

[glauco.lins]

did you set the display for the virtual machine?
Try default or VirtIO-GPU

If you are doing GPU Passthrough, use VirtIO-GPU to get the ">_ Console" (noVNC) to work.

I'm wonder if this is a limitation of this old hardware. Is there a way to ask the hardware if it's virtualization compatible? I saw nothing to enable in the BIOS.

Ultimatelly you can try set the processor to KVM64 or QEMU64.
As far as I understand, these options emulate hardware virtualization.
In other words, you will have a slower guest.

For Intel processor, look for VT-x
For AMD, look for AMD-v

 

[jamesisin]

Thanks, glauco.lins,

I didn't set up any GPU passthrough but I tried a variety of the Display options to no avail. Similarly for Processors (KVM64 is apparently the default and I tried several of the others, including QEMU64, to no avail). I saw no mention of VT-x.

 

[glauco.lins]

I said qemu64 and kvm64 assuming you have a 64bit processor.
Do you know your processor model?
With that information you can look at Intel Ark to see if it offers virtualization.

After you click "start" the virtual machine status says "running"?
Or the line in the bottom of the web interface gets red and the machine stops?

Please post your virtual machine config