How do I set up noVNC with my VNC server?

Use the novnc_proxy script to start a WebSocket proxy pointing to your VNC server, then access the provided URL in a browser. For example, run './utils/novnc_proxy --vnc localhost:5901' and connect via the output URL, as detailed in the quick start section.

noVNC vs Apache Guacamole: which is better for web-based remote access?

noVNC is specifically for VNC and is lighter, ideal for integrating VNC into web apps. Apache Guacamole supports multiple protocols like VNC, RDP, and SSH, but is heavier and more complex. Choose noVNC for VNC-only needs, Guacamole for multi-protocol support.

Can noVNC work on mobile phones?

Yes, noVNC runs well on mobile browsers including iOS and Android, with touch gesture support for emulating mouse actions, making it suitable for remote management on the go, as stated in the features list.

How to embed noVNC into my own web application?

Refer to the LIBRARY.md documentation for integrating the noVNC JavaScript library. It provides APIs for connecting to VNC servers and handling desktop rendering within your app's interface, allowing custom UI integration.

Does noVNC support copy and paste between local and remote desktops?

Yes, noVNC supports clipboard copy/paste with full Unicode support, allowing seamless text transfer between the browser and remote VNC session, which is useful for productivity in remote access scenarios.

What are the minimum browser requirements for noVNC?

noVNC requires modern browsers like Chrome 89, Firefox 89, Safari 15, or later, as specified in the browser requirements. Older browsers may not be supported due to the use of advanced web technologies like WebSockets.

Open-Awesome

noVNC

NOASSERTIONJavaScriptv1.7.0

A HTML VNC client JavaScript library and application that runs in modern browsers, including mobile.

Visit Website GitHub

13.9k stars2.6k forks0 contributors

What is noVNC?

noVNC is an open-source HTML VNC client library and web application that allows users to access remote desktops directly from a web browser. It implements the VNC protocol over WebSockets, enabling no-plugin remote desktop access for cloud platforms, virtualization management, and remote support. The project solves the problem of providing cross-platform VNC access without requiring native client installations.

Target Audience

Developers and integrators building cloud infrastructure platforms (like OpenStack or OpenNebula), virtualization management tools, or remote support solutions that require browser-based remote desktop access.

Value Proposition

Developers choose noVNC because it's a mature, widely-adopted open-source solution that works in any modern browser, supports a wide range of VNC encodings and authentication methods, and can be easily integrated into existing systems or self-hosted.

Overview

VNC client web application

Use Cases

Best For

Adding remote desktop access to cloud management platforms
Building browser-based virtualization administration interfaces
Creating mobile-friendly remote support tools
Integrating VNC capabilities into web applications without plugins
Self-hosting remote desktop solutions for internal infrastructure
Developing cross-platform remote access solutions for iOS and Android

Not Ideal For

Projects requiring native application performance without browser latency overhead
Environments with VNC servers lacking WebSockets support and unwilling to deploy a proxy
Use cases needing remote desktop protocols other than VNC, such as RDP for Windows-centric infrastructures

Pros & Cons

Pros

Cross-Platform Accessibility

Works in any modern browser including iOS and Android, enabling remote access from virtually any device without plugins, as highlighted in the browser requirements section.

Comprehensive VNC Support

Implements a wide range of VNC encodings and authentication methods, such as tight, ZRLE, and RealVNC RSA-AES, ensuring compatibility with various servers and efficient data transmission.

Flexible Integration

Can be embedded as a JavaScript library or deployed as a standalone app with WebSocket proxy via websockify, making it adaptable to different project needs like cloud platforms and remote management tools.

Cons

WebSocket Dependency

Requires VNC servers to support WebSockets or the use of websockify proxy, adding an extra layer to setup and potential points of failure, as admitted in the server requirements section.

Browser Version Constraints

Minimum browser versions like Chrome 89 are required, which may exclude older systems or browsers, limiting accessibility in legacy environments despite broad modern support.

Setup Complexity

Initial deployment involves running scripts like novnc_proxy or configuring snap packages, which can be challenging for those unfamiliar with VNC or web server setups, as seen in the quick start guide.

Frequently Asked Questions

Related Projects

ansible

Ansible is a radically simple IT automation platform that makes your applications and systems easier to deploy and maintain. Automate everything from code deployment to network configuration to cloud management, in a language that approaches plain English, using SSH, with no agents to install on remote systems. https://docs.ansible.com.

Stars69,669

Forks24,186

Last commit11 hours ago

localstack

💻 A fully functional local AWS cloud stack. Develop and test your cloud & Serverless apps offline

Stars65,152

Forks4,771

Last commit4 months ago

traefik

The Cloud Native Application Proxy

Stars64,084

Forks6,087

Last commit16 hours ago

Portainer

Making Docker and Kubernetes management easy.

Stars38,033

Forks2,870

Last commit19 hours ago

Community-curated · Updated weekly · 100% open source

Found a gem we're missing?

Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.

Submit a project Star on GitHub