Cookies on this website

We use cookies to ensure that we give you the best experience on our website. If you click 'Accept all cookies' we'll assume that you are happy to receive all cookies and you won't see this message again. If you click 'Reject all non-essential cookies' only necessary cookies providing core functionality such as security, network management, and accessibility will be enabled. Click 'Find out more' for information on how to change your cookie settings.


These instructions are for running and connecting to a graphical display on Linux workstations, jalapeno and jalapeno00/18 (XX) nodes.​

Whilst it is possible to run graphical programs on Linux desktops, jalapeno and jalapenoXX nodes via remote-X11 connections, we recommend that you use Virtual Network Computing (VNC) sessions. These are persistent (please shut these down when you aren't actively running anything) so your running programs will survive a loss of WiFi connection or you moving from one physical location to another (e.g. going home to continue your work). The system also works well on low-bandwidth connections, unlike remote-X11, and typically behaves better with modern visualisation software.

To use VNC you first need to start a VNC server on the computer you will be using - if you don't have a dedicated Linux desktop computer then this will normally be

For FMRIB hosted services, you can run VNC on ( internally), or (the latter only available directly with a VPN connection).

Starting A server

On jalapeno

Use a SSH client (either 'ssh' or puTTY) into your chosen jalapeno server and enter the command vncserverThis will either start a VNC server and report back the display number for that server, or advise you of the number of an existing server - you need this number to connect to the server so make a note of it. This number will be yours for the lifetime of your VNC server, i.e. until you shutdown the VNC server or the computer is rebooted.

Example output:

 New ' (auser)' desktop is Starting applications specified in /homes/auser/.vnc/xstartup Log file is /homes/auser/.vnc/

In this example the display number is 1. 

Linux Desktops

There are two options for VNC on Linux desktops, a standalone, multi-user VNC desktop as per or a mirror of the local display. The later is appropriate if the machine is dedicated to your use, but be aware that people in the building will be able to see what you are doing, if your display is switched on, and interact using the local keyboard an mouse. ALWAYS ​lock your remote screen if you are going to leave it unattended for more than a few seconds, and do not view sensitive information.

The multi-user VNC server will not be able to utilise any GPU resources for improved graphics performance but content will not be shown on the local display so this mode is suitable for sensitive information and there is no need to lock the remote screen when leaving unattended.

To start a local display mirror use the command:


​​​The display to connect to in this instance is :0, e.g. port 5900.

To start a separate, multi-user VNC session use:


Example output:

New ' (auser)' desktop is Starting applications specified in /homes/auser/.vnc/xstartup Log file is /homes/auser/.vnc/

In this example the display number is 1.

Connecting to a VNC Server

To connect to your VNC server session you need a VNC viewer application of which we support TigerVNC Viewer. Windows, macOS clients are available from the link on and Linux clients should be available via your distributions software store. We recommend version 1.13.0+, especially on macOS where 1.12.0 is known to have issues with it's settings control panel.

Connections to are only possible from a University of Oxford network so when connection from home/another institution, you will need to connect to the FMRIB,  Oxford University or MSD-IT VPN services first. To access devices on the FMRIB network other than jalapeno, you should either use the FMRIB VPN or use as a jump server (see below). Oxford University and MSD-IT VPN services only allow a direction connection to jalapeno server; you will need to hop using ssh to access other servers so, where possible, FMRIB's VPN is recommended.

In all cases, VNC connections are only supported over an encrypted SSH tunnel (direct VNC connections are unencrypted).

SSH Tunnels

The SSH service can protect arbitrary network traffic using a tunnel, this can be used to secure an otherwise insecure connection.

Mac, Linux and the latest builds of Windows 10 and Windows 11 include a built-in ssh client.  Alternatively the graphical Putty application can be obtained from

puTTY has a section under Connection > SSH > Tunnels which allows you to configure these SSH port forwards.

When connecting to an unencrypted VNC server you need to setup a tunnel that will carry the VNC communications; this is achieved as follows:

Use the SSH command line to build the tunnel

ssh -J SSHSERVER -C -L 59XX:localhost:59XX username@REMOTESERVER

XX should be the zero-padded, two digit display number of your VNC desktop, e.g. 01 or 10. If the VNC desktop is running on a different server that isn't visible on your network then REMOTESERVER should be the DNS name of the server as it is known to SSHSERVER.

Example 1, VNC is running on - no need to jump via another host

ss​​​h -C -L 5910:localhost:5910

Example 2, VNC is running on the server which cannot be contacted outside of the FMRIB network (or is an external resource that requires you to connect from, the command:

ssh -J -C -L 5910:localhost:5910

would allow you to connect to the VNC server using jalapeno as a proxy.

Now you can use the Tiger VNC client to open the display.

Connecting to a tunnelled VNC display

With the software installed/downloaded run the viewer application (double click the application on macOS and Windows or run the vncviewer program from a terminal or Linux desktop panel menu. 

When the viewer starts you are presented with the connection details window, enter localhost:<displaynumber>, e.g. localhost:1 if you have display number 1.

Screen Shot 2018-11-26 at 10.33.27.png

You will then be presented with a login dialogue box:


Note the red-banner, the connection has been secured by your SSH tunnel, but the VNC viewer doesn't know this and so presents this warning message - you can ignore this.

Log in with your WIN computer account name and password.​ You will now be presented with a view of your desktop, the LXQT environment. 

Connection errors

​If your connection fails with an error message saying "No valid vencrypt" or "No valid security types", please restart TigerVNC, click on the Options button, then select the Security Tab. At this point, you should untick the Authentication Types None and Standard VNC. Your settings should now be as shown at the bottom of the image below:

Security Tab - untick authentication types None and Standard VNC

Then continue connecting as per the above instructions.

Stoppin​​g a server

When you have finished your work please remember to shut down your server as there are a limited number of slots available for these sessions. To shutdown your server, either use the Leave > Logout panel menu option or in a terminal issue the command

vncserver -kill :<display number>

e.g. if you have display number 1

vncserver -kill :1

On this page