open vnc error: Unsupported security types: 19

[RobFantini]

On some systems I get this when trying to run console:

Unsupported security types: 19

that happens only on some systems .


using VNC works . so it is not a big deal.

still any clues on how to fix?

 

[1nerdyguy]

On some systems I get this when trying to run console:

Unsupported security types: 19

that happens only on some systems .


using VNC works . so it is not a big deal.

still any clues on how to fix?

I'm getting this now to, but only for one host. If I migrate the VM to a different host, NoVNC works great.

 

[RobFantini]

the 4 systems have this issue on have a support contract license attached to. those 4 are the ceph cluster we use .

in addition we have our own tls cert for our domain .

do you have either of those two ?

 

[dgp]

From my small setup and testing this appears to be a cross server issue. If I use NoVNC console on a VM that's hosted on the same server as the web interface in use it works fine. If I try to access a VM hosted on a different server in the cluster I get the Unsupported security types error.

Although talking about slightly different backend tools (I think, no idea what Proxmox uses) it led me in the right direction:
http://stackoverflow.com/questions/6391005/novnc-to-x11vnc-ssl-connection

So the issue is between noVNC trying to connect to "qm vncproxy" on a different host

 

[RobFantini]

" If I use NoVNC console on a VM that's hosted on the same server as the web interface in use it works fine. If I try to access a VM hosted on a different server in the cluster I get the Unsupported security types error."

The same thing occurs here.

 

[ScottR]

Has anyone ever resolved this issue? It's still present in 4.3 except with a fresh error:

Unsupported security types: [object Uint8Array]

Note, I can produce this consistently if I connect to a pve cluster via node1, while trying to open console on node3. It's quite awkward to have to keep connecting to the node where the QEMU VM resides.

 

[tom]

Has anyone ever resolved this issue? It's still present in 4.3 except with a fresh error:

Unsupported security types: [object Uint8Array]

Note, I can produce this consistently if I connect to a pve cluster via node1, while trying to open console on node3. It's quite awkward to have to keep connecting to the node where the QEMU VM resides.

this works here, so I assume you have a cluster communication problem somewhere. please open a new thread as this one is old and seems unrelated.

 

[ScottR]

New thread here as requested.

https://forum.proxmox.com/threads/pve-4-3-console-access-on-different-cluster-member.29733/