This document describes how to embed and deploy the noVNC application, which includes settings and a full user interface. If you are looking for documentation on how to use the core noVNC library in your own application, then please see our library documentation.
The noVNC application consists of the following files and directories:
vnc.html - The main page for the application and where users should go. It
is possible to rename this file.
app/ - Support files for the application. Contains code, images, styles and
core/ - The core noVNC library.
vendor/ - Third party support libraries used by the application and the
The most basic deployment consists of simply serving these files from a web server and setting up a WebSocket proxy to the VNC server.
The noVNC application can be controlled by including certain settings in the query string. Currently the following options are available:
autoconnect - Automatically connect as soon as the page has finished
reconnect - If noVNC should automatically reconnect if the connection is
reconnect_delay - How long to wait in milliseconds before attempting to
host - The WebSocket host to connect to.
port - The WebSocket port to connect to.
encrypt - If TLS should be used for the WebSocket connection.
path - The WebSocket path to use.
password - The password sent to the server, if required.
repeaterID - The repeater ID to use if a VNC repeater is detected.
shared - If other VNC clients should be disconnected when noVNC connects.
bell - If the keyboard bell should be enabled or not.
view_only - If the remote session should be in non-interactive mode.
view_clip - If the remote session should be clipped or use scrollbars if
it cannot fit in the browser.
resize - How to resize the remote session if it is not the same size as
the browser window. Can be one of
quality - The session JPEG quality level. Can be
compression - The session compression level. Can be
show_dot - If a dot cursor should be shown when the remote server provides
no local cursor, or provides a fully-transparent (invisible) cursor.
logging - The console log level. Can be one of
noVNC is written using ECMAScript 6 modules. Many of the major browsers support these modules natively, but not all. By default the noVNC application includes a script that can convert these modules to an older format as they are being loaded. However this process can be slow and severely increases the load time for the application.
It is possible to perform this conversion ahead of time, avoiding the extra load times. To do this please follow these steps:
npm installin the noVNC directory
./utils/use_require.js --with-app --as commonjs
This will produce a
build/ directory that includes everything needed to run
the noVNC application.
If you serve noVNC files using a web server that provides an ETag header, and
include any options in the query string, a nasty browser cache issue can bite
you on upgrade, resulting in a red error box. The issue is caused by a mismatch
between the new vnc.html (which is reloaded because the user has used it with
browser reuses from its cache). To avoid this issue, the browser must be told
to always revalidate cached files using conditional requests. The correct
semantics are achieved via the (confusingly named)
header that needs to be provided in the web server responses.
# In the main configuration file # (Debian/Ubuntu users: use "a2enmod headers" instead) LoadModule headers_module modules/mod_headers.so # In the <Directory> or <Location> block related to noVNC Header set Cache-Control "no-cache"
# In the location block related to noVNC add_header Cache-Control no-cache;