VNC via browser
Use the browser for VNC connections
Using the NoVNC integration makes your VNC connection fully encrypted, even if the remote VNC server does not support encryption. The VNC "signal" is sent to the encrypted tunnel of rport from your remote machine to the rport server. The server transforms the signal into HTTPS.
VNC connection from the browser
Accessing a server via the NoVNC requires a VNC server running on the remote host. On Windows, the free TightVNC server is a good choice, but any VNC server is suitable. After installing the VNC server, activate the following settings:
- Turn off encryption. On TightVNC, encryption is not included, but others might have it. Encryption will be added via the RPort tunnel, the VNC server must accept unencrypted connections.
- Allow connection from localhost. All VNC server by default do not allow connection from localhost. Some call it loop back connection.
The VNC server must allow loop back connections.