VNC via browser
Use the browser for VNC connections
Starting with RPort-Server 0.6.0 the NoVNC proxy and the NoVNC JavaScript client is included into the server. You directly connect to a remote VNC server from your browser. No VNC viewer is needed.
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.
The current version of VNC® Server from RealVNC® should not be used for RPort's browser-based VNC remote access.
NoVNC only supports old (open source) versions of the RFB protocol. RealVNC® has added a number of enhancements to the RFB protocol including encryption and additional authentication mechanisms not supported by NoVNC.
⛔ It is not recommended to make any configuration changes to VNC® Server from RealVNC® to achieve NoVNC compatibility, like disabling security, using “VNC Password” authentication and setting protocol version to 3.8.
👉 Using the RPort/VNC® Viewer from RealVNC® integration is recommended. Learn more.
Last modified 7mo ago