Using GUI Applications with VNC¶
NOTE:Please also see our page on using X2Go as this is a little bit simpler to set up than VNC.
Here we cover how to use a VNC server on the CRNCH Rogues Gallery machines to access and manipulate GUI-based applications. We typically have TightVNC servers set up in conjunction with the xfce4 desktop as this allows for a low-latency but somewhat standardized and open-source setup.
Table of Contents¶
TLDR - How do I quickly get started using VNC on CRNCH resources?¶
This guide goes into great details on the how and why of using VNC. If you have questions, please refer to the following sections for more information. As a baseline just to get started you need to do the following:
- Select and install a VNC viewing client on your local workstation. We recommend TightVNC for Windows or RealVNC Viewer for Mac OSX.
- Connect to your destination server using SSH jumphosts and port forwarding. Here we use a jumphost to ssh to our destination server.
ssh -L 5901:localhost:5901 -C -J <yourGTusername>@rg-login.crnch.gatech.edu <yourGTusername>@flubber1.crnch.gatech .edu
- Start the remote VNC server. On the first time you start this, you will need to enter a new password.
//On newer flubber installs you may need to add the newest VNC to your path. This will be updated shortly! export PATH=$PATH:/opt/TurboVNC/bin //Launch a vnc server vncserver #Enter your 6 character password on first use.
- Using your local VNC viewer client connect to “localhost::5901” using your password. You then should be able to launch the web browser and apps.
- Once you are done, please kill your VNC session in the terminal before logging out.
#Usually you will kill instance #1 vncserver -kill :1 #Check with ps aux to see if you have any VNC sessions open and kill these ps aux | grep <yourGTusername> kill <any pids for xtightvnc>
There is a script, crnch_client_vnc_login.sh in the rogues-docs repository that you can use for the initial port forwarding setup from your local machine.
What about running GUI applications on Windows Subsystem for Linux?¶
This uses X forwarding and is described more in this page.
What is VNC?¶
While there is a lot of good information about “virtual network computing (VNC)” online, the main keys to remember are that VNC consists of a server running on the remote machine, a client running on your local host, and graphical updates and keystrokes are exchanged via a protocol called Remote Frame Buffer (RFB). There are many different optimizations for serving and updating a graphical environment using RFB with optimizations to only transfer data when a particular “square” of the served application changes.
How does VNC differ from X11 forwarding?¶
ssh -X or
ssh -Y will allow you to use “X forwarding” to
forward one application to your desktop. The main difference between X
forwarding and VNC is that X forwarding typically only forwards one
application at a time while VNC will forward a session, including the
application and a desktop environment.
VNC sessions also typically survive a disconnection because they are running remotely on the VNC server rather than being forwarded to your local X server. This also means that VNC requires more resources on the server while X forwarding typically requires a faster client. VNC is also optimized to have lower latency which may make your session seem more responsive.
X11 sessions may handle multi-layered windows (think Matlab with an output figure) better than VNC because it will spawn multiple windows rather than just showing the graphical region that has been changed, as with VNC. This is a trade-off in terms of performance and usability.
For more differences please check out these links:
How does VNC differ from NX?¶
NX is a similar protocol to RFB that is further optimized for low-bandwidth connections and that supports more options for secure connections (i.e. Kerberos, SSH keys). The NX protocol is proprietary and is created by the Belgian company NoMachine. However, free implementations of NX like FreeNX are available.
How does VNC differ from Remote Desktop?¶
The main difference is that Remote Desktop is typically an OS-dependent tool that has slightly better integration with the video driver stack. Microsoft’s remote desktop has been around since the early 2000s, and Apple’s Remote Desktop is a more recent innovation. Both of these tools are typically used in an IT setting for “remote assistance”.
A master list of remote desktop client comparisons can be found on Wikipedia.
- TigerVNC - Supports Mac
- NoMachine (NX)
- TurboVNC - Recommended by PACE
Setting up a VNC server¶
We suggest using xfce4 as the desktop environment because it is a bit more full-featured than standard X11 but still lightweight.
Install the following:
sudo apt install tightvncserver xfce4 xfce4-terminal firefox autocutsel -y
sudo dnf install tigervnc-server xfdesktop xfce4-terminal xfce4-session
Setting up and using your VNC client (GT Network or VPN)¶
This guide has a great introduction to setting up both a VNC server and your local client.
- Set up your local VNC viewer client from the list above.
- Connect to the remote server using the appropriate SSH port forwarding command. If you are connecting to a node other than rg-login or hawksbill, you will either need to be on the GT network (LAWN) or connected to the campus network with VPN.
# -L specifies which port to forward from the remote machine to the local machine # -C specifies to use compression. This is usually useful for X sessions or VNC! # Here we want to forward the GUI from rg-login to our local machine. We assume that the user is on GT network or connected to the VPN. ssh -L 5901:localhost:5901 -C firstname.lastname@example.org email@example.com's password: Welcome to Ubuntu 18.04.4 LTS (GNU/Linux 4.15.0-91-generic x86_64) ... #Start the TightVNC server on the remote machine [rg-login]$vncserver #If it is the first time you've started this server, you will need to create a unique password for the server.
Using SSH jump hosts (VNC without the GT VPN)¶
Note that applications might be a little bit more responsive when you are connected to the GT VPN, but you can also use SSH jumphosts to connect directly to an application on a server behind the firewall.
# -L specifies which port to forward from the remote machine to the local machine # -C specifies to use compression. This is usually useful for X sessions or VNC! # -J <host1> <host2> specifies a jump host, where you log into host1 and then "jump" to host2 # Here we want to forward the GUI from flubber to our local machine. ssh -L 5901:localhost:5901 -C -J firstname.lastname@example.org email@example.com firstname.lastname@example.org's password: email@example.com's password: Welcome to Ubuntu 16.04.6 LTS (GNU/Linux 4.4.0-142-generic x86_64)... ... #Start the TightVNC server on the remote machine [flubber]$vncserver New 'X' desktop is flubber:1 Starting applications specified in /nethome/gtburdell/.vnc/xstartup Log file is /nethome/gtburdell/.vnc/flubber:1.log #Now you can proceed to connect with your local VNC viewer using the address "localhost::5901
Securing VNC Server¶
When you first set up a new VNC server instance, it should ask you for an 8 character password. Please note that this password is stored locally in your ~/.vnc/passwd file, and it is “encrypted” but not necessarily hard to reverse engineering. These limitations (password size, etc.) mainly ensure compatibility with the RFB protocol, so for this reason we strongly encourage that you kill vncserver sessions when you are done with them!
If you need to change your password, you can use the “vncpasswd” function to do so. Note that we advise not entering a “view-only” password.
$ vncpasswd Using password file /nethome/jyoung9/.vnc/passwd Password: Verify: Would you like to enter a view-only password (y/n)? n
Killing a VNC server instance¶
To kill the remote server you want to kill the particular “session” that
is being served; usually this is the first session. However if you run
multiple instances of vncserver you may have to use
You can check to see which vncservers are running with
ps aux | grep vnc.
#Checking to see how many VNC sessions are running ps aux | grep vnc gtburdell 2452 0.0 0.1 57752 15864 pts/0 S 13:04 0:00 Xtightvnc :1 -desktop X -auth /nethome/gtburdell/.Xauthority -geometry 1024x768 -depth 24 -rfbwait 120000 -rfbauth /nethome/jyoung9/.vnc/passwd -rfbport 5901 -fp /usr/share/fonts/X11/misc/,/usr/share/fonts/X11/Type1/,/usr/share/fonts/X11/75dpi/,/usr/share/fonts/X11/100dpi/ -co /etc/X11/rgb #Kill the first VNC session vncserver -kill :1 Killing Xtightvnc process ID 1922
Using GUI jobs with the other GT Resources (PACE tips)¶
PACE has other resources for running graphical jobs including tips on X
forwarding and submission scripts like
pace-jupyter-notebook which allow users to use VNC and SSH port
forwarding to view graphical applications and Jupyter notebooks hosted
on PACE cluster interactive jobs, respectively.
- Using copy-paste between your local client and the remote VNC
session: With TightVNC, this requires the install of the package
autocutselas detailed in this post.
- A sample
~/.vnc/xstartupfile that includes support for autocutsel is as follows:
- A sample
#!/bin/bash xrdb $HOME/.Xresources #Use the xfce desktop instead of a basic X session, /etc/X11/Xsession startxfce4 & xrdb $HOME/.Xresources # -solid grey gaves us a real mouse pointer instead of the default X xsetroot -solid grey -cursor_name left_ptr # Allow copy & paste when ClientCutText is set to true on the client side autocutsel -fork
startxfce4 /usr/bin/startxfce4: Starting X server /usr/lib/xorg/Xorg.wrap: Only console users are allowed to run the X server No protocol specified xinit: giving up xinit: unable to connect to X server: Resource temporarily unavailable xinit: server error
/etc/X11/Xwrapper.config needs to be edited to allow “anybody” to
run X11 instead of just console users.
TBD - not totally clear why this might be happening..
startxfce4 Cannot open /dev/tty0 (Permission denied)