You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have an vm running on ESXi. Using RealVNC, I can directly connect to the VNC server provided by ESX to that vm so I know the ESX firewall is correct. If I try the same using websockify with vnc.html. I get one of two errrors.
In the first case , using Chrome developer tools, I can see it connect and it will actually register mouse clicks. The instant you type any character in the vnc screeen though it fails with
I have an vm running on ESXi. Using RealVNC, I can directly connect to the VNC server provided by ESX to that vm so I know the ESX firewall is correct. If I try the same using websockify with vnc.html. I get one of two errrors.
In the first case , using Chrome developer tools, I can see it connect and it will actually register mouse clicks. The instant you type any character in the vnc screeen though it fails with
Sending keysym (down): 100
keyboard.js:42 onkeyevent up, keysym: 100 , code: KeyD
rfb.js:376 Sending keysym (up): 100
rfb.js:685 Failed while connected: Unsupported encoding (encoding: -260)
_fail @ rfb.js:685
_framebufferUpdate @ rfb.js:1517
_normal_msg @ rfb.js:1422
_handle_message @ rfb.js:725
_recv_message @ websock.js:304
rfb.js:635 New state 'disconnecting', was 'connected'.
rfb.js:427 >> RFB.disconnect
keyboard.js:276 >> Keyboard.allKeysUp
keyboard.js:281 << Keyboard.allKeysUp
websock.js:239 Closing WebSocket connection
Also sometimes it just fails with this error
Starting VNC handshake
websock.js:221 << WebSock.onopen
websock.js:224 >> WebSock.onclose
rfb.js:211 WebSocket on-close event
rfb.js:688 Failed when connecting: Connection closed (code: 1006)
_fail @ rfb.js:688
(anonymous) @ rfb.js:222
(anonymous) @ websock.js:225
rfb.js:635 New state 'disconnecting', was 'connecting'.
Should this work with recent versions of ESXi/vSphere hypervisors?
The text was updated successfully, but these errors were encountered: