VNC client web application
Go to file
Kyle Russell 1a50f6809f rfb: Allow port to be optionally appended to URI
Supports server configurations that might prefer wss:// connections
on the default port, then proxies them through the web server to the
VNC server.

This proxy configuration is helpful on servers using self-signed
certificates.  Accessing the https://host/vnc_auto.html page and
adding an exception for that host is sufficient to also satisfy the
wss://host/ request, unlike requests to wss://host:port/ which
may require an extra certificate exception.
2016-11-24 06:14:31 -06:00
app Update Greek translation 2016-11-24 12:18:59 +02:00
core rfb: Allow port to be optionally appended to URI 2016-11-24 06:14:31 -06:00
docs Enable noVNC to become Browserifiable 2016-09-16 15:49:51 -04:00
po Update Greek translation 2016-11-24 12:18:59 +02:00
tests rfb: Allow port to be optionally appended to URI 2016-11-24 06:14:31 -06:00
utils Use Unicode keysym range as fallback 2016-10-15 14:58:55 +02:00
.gitignore Enable noVNC to become Browserifiable 2016-09-16 15:49:51 -04:00
.gitmodules Use Typed Arrays for the Websock receive queue 2015-08-06 14:47:03 -04:00
.npmignore Clean up page icon ("favicon") handling 2016-10-14 13:24:35 +02:00
.travis.yml Bump up node.js version for travis 2016-11-10 09:26:00 +01:00
CONTRIBUTING.md Added in guidelines for contributing to noVNC 2014-11-02 13:27:06 -05:00
LICENSE.txt Move input-related files into core/input 2016-09-16 15:49:52 -04:00
README.md Added more useful links to README 2016-11-22 00:59:11 +01:00
karma.conf.js Move input-related files into core/input 2016-09-16 15:49:52 -04:00
package.json Also translate HTML elements 2016-11-19 13:23:00 +01:00
vnc.html Also translate HTML elements 2016-11-19 13:23:00 +01:00
vnc_auto.html Use gettext .po files for translations 2016-11-17 20:42:08 +01:00

README.md

noVNC: HTML5 VNC Client

Build Status

Description

noVNC is a HTML5 VNC client that runs well in any modern browser including mobile browsers (iOS and Android).

Many companies, projects and products have integrated noVNC including Ganeti Web Manager, OpenStack, OpenNebula, LibVNCServer, and ThinLinc. See the Projects and Companies wiki page for a more complete list with additional info and links.

News/help/contact

Notable commits, announcements and news are posted to @noVNC.

If you are a noVNC developer/integrator/user (or want to be) please join the noVNC discussion group.

Bugs and feature requests can be submitted via github issues. If you are looking for a place to start contributing to noVNC, a good place to start would be the issues that are marked as "patchwelcome".

If you want to show appreciation for noVNC you could donate to a great non- profits such as: Compassion International, SIL, Habitat for Humanity, Electronic Frontier Foundation, Against Malaria Foundation, Nothing But Nets, etc. Please tweet @noVNC if you do.

Features

  • Supports all modern browsers including mobile (iOS, Android)
  • Supported VNC encodings: raw, copyrect, rre, hextile, tight, tightPNG
  • WebSocket SSL/TLS encryption (i.e. "wss://") support
  • 24-bit true color and 8 bit colour mapped
  • Supports desktop resize notification/pseudo-encoding
  • Local or remote cursor
  • Clipboard copy/paste
  • Clipping or scolling modes for large remote screens
  • Easy site integration and theming (3 example themes included)
  • Licensed under the MPL 2.0

Screenshots

Running in Chrome before and after connecting:

 

See more screenshots here.

Browser Requirements

  • Chrome 8, Firefox 4, Safari 6, Opera 12, IE 11, Edge 12, etc.

  • HTML5 Canvas, WebSockets and Typed Arrays

  • Fast Javascript Engine: this is not strictly a requirement, but without a fast Javascript engine, noVNC might be painfully slow.

  • See the more detailed browser compatibility wiki page.

Server Requirements

Unless you are using a VNC server with support for WebSockets connections (such as x11vnc/libvncserver, QEMU, or PocketVNC), you need to use a WebSockets to TCP socket proxy. There is a python proxy included ('websockify').

Quick Start

  • Use the launch script to start a mini-webserver and the WebSockets proxy (websockify). The --vnc option is used to specify the location of a running VNC server:

    ./utils/launch.sh --vnc localhost:5901

  • Point your browser to the cut-and-paste URL that is output by the launch script. Enter a password if the VNC server has one configured. Hit the Connect button and enjoy!

Other Pages

  • Modules/API - The library modules and their Javascript API.

  • Integration - Get noVNC to work in existing projects.

  • Troubleshooting - How to troubleshoot problems.

  • Encrypted Connections - Setup websockify so that you can use encrypted connections from noVNC.

  • Advanced Usage - Generating an SSL certificate, starting a VNC server, advanced websockify usage, etc.

  • Testing - Run and write tests.

  • Translations - Add and modify localization for JavaScript and HTML.

Authors/Contributors

  • Core team:

  • Notable contributions:

    • UI and Icons : Pierre Ossman, Chris Gordon
    • Original Logo : Michael Sersen
    • tight encoding : Michael Tinglof (Mercuri.ca)
  • Included libraries:

    • as3crypto : Henri Torgemane (code.google.com/p/as3crypto)
    • base64 : Martijn Pieters (Digital Creations 2), Samuel Sieb (sieb.net)
    • DES : Dave Zimmerman (Widget Workshop), Jef Poskanzer (ACME Labs)
    • Pako : Vitaly Puzrin (https://github.com/nodeca/pako)
  • Contribution guide