For efficiency, security, and the ability to do everything from the command line, many servers don’t use a graphical user interface (GUI). However, there are times when you’ll want to run GUI applications on your remote servers, like when you’re testing web sites in browsers or you’re looking to set up a remotely accessible workstation with a full desktop environment (DE).
The typical solution to interacting with a graphical interface on a remote computer running Linux or other *nix variants is Virtual Network Computing (VNC). Unfortunately, VNC is notoriously sluggish, insecure by default, and requires a lot of manual configuration to get up and running.
In contrast, X2Go provides several advantages:
Such a setup is useful when:
In this tutorial, we’re recommending Debian over Ubuntu, because some versions of Ubuntu’s default DE, Unity, aren’t compatible with X2Go. And, alternative desktop environments can sometimes be problematic on Ubuntu.
Likewise, we’re recommending XFCE, because it doesn’t require a dedicated video card to run, making it more compatible with X2Go. But, LXDE, Mate (with compositing disabled), and even older KDEs, Unity and Cinnamon (with some tweaks) can work, too.
Lastly, Firefox—if xrender is active (which it is by default in Debian 8)—usually provides a smoother experience with X2Go.
After working through this tutorial, you’ll have a Linux desktop that you can connect to remotely and that includes exactly the same utilities you would get by installing Debian XFCE locally. Plus, by installing and configuring a firewall, you’ll secure your remote desktop, making it more difficult to exploit.
Before getting started with this tutorial, you will need:
Remember that if you run out of RAM, the application will be terminated by the Linux kernel, and you might lose your work. If you know or notice that the programs you use require a lot of RAM, you can power off your droplet and resize as needed.
Installing an entire desktop environment pulls in a lot of additional software dependencies and recommendations, some of which may try to open up network ports. For example, the Common UNIX Printing System (CUPS) included in many DEs might try to open up port 631. While a service like CUPS may be useful at home, we don’t want our server to be that exposed to the entire Internet, so blocking every incoming connection is a good idea. The only exception will be port 22, which will be left open so that we’re able to connect with SSH and X2Go.
To secure our server, we’ll be using Uncomplicated Firewall (UFW), because it’s less error-prone to beginner mistakes, easier to understand and manage, and fits better with our goal of only allowing connections to one port. iptables and other more sophisticated firewalls are better suited for advanced and complex rules that require more fine-grained detail. (See UFW Essentials: Common Firewall Rules and Commands for a quick reference guide to common commands.)
First, install UFW:
- sudo apt-get install ufw
By default, the firewall should be inactive at this point. You can check with:
- sudo ufw status verbose
The result should be:
Verifying the status at this point is important to avoid locking ourselves out if
ufw is active when we block all incoming connections later.
If UFW is already active, disable it with:
- sudo ufw disable
Now, set the default firewall rules to deny all incoming connections and allow all outgoing ones:
- sudo ufw default deny incoming
- sudo ufw default allow outgoing
And, allow SSH connections to the server (port 22):
- sudo ufw allow 22
With the rules in place, let’s activate
- sudo ufw enable
This will output:
OutputCommand may disrupt existing ssh connections. Proceed with operation (y|n)?
y and press
ENTER to activate the firewall.
If you run into a problem and discover that SSH access is blocked, you can follow How To Use the DigitalOcean Console to Access your Droplet to recover access.
With our firewall in place, there’s only one point of entry to our server, and we’re ready to install the graphical environment for the X2Go server.
In this tutorial, you’ll install the XFCE desktop environment. There are two ways to achieve this, but you only need to choose one—either the Minimal Desktop Environment or the Full Desktop Environment.
Minimal Desktop Environment: If you want to install a small, core set of packages and then build on top of them by manually adding whatever you need afterward, you can use the
A metapackage doesn’t contain software of its own, it just depends on other packages to be installed, allowing for an entire collection of packages to be installed at once without having to type each package name individually at the command line.
xfce4 and all of the additional dependencies needed to support it:
- sudo apt-get install xfce4
Full Desktop Environment: If you don’t want to handpick every component you need and would rather have a default set of packages, like a word processor, web browser, email client, and other accessories pre-installed, then you can choose
Install and configure a complete desktop environment that’s similar to what you would get with Debian XFCE from a bootable DVD on your local PC:
- sudo apt-get install task-xfce-desktop
Now that our graphical environment is installed and configured, we need to set up a way to view it from another computer.
X2Go comes with two main components: the server, which starts and manages the graphical session on the remote machine, and the client, which we install on our local computer to view and control the remote desktop or application.
Since Debian does not include the X2Go server in its default repositories, we have to add an extra repository to the package manager’s configuration.
First, import the X2Go’s developers’ public key. This is a security measure to ensure that we can only download and install packages which are properly signed with their private keys.
- sudo apt-key adv --recv-keys --keyserver keys.gnupg.net E1F958385BFE2B6E
Now, add the repository to the package manager’s config files:
- echo 'deb http://packages.x2go.org/debian jessie main' | sudo tee /etc/apt/sources.list.d/x2go.list
This creates the file
/etc/apt/sources.list.d/x2go.list and adds the line
deb http://packages.x2go.org/debian jessie main to it, telling the package manager where to find the supplementary packages.
To refresh the database of available software packages, enter the following command:
- sudo apt-get update
And, finally, install X2Go on the server:
- sudo apt-get install x2goserver x2goserver-xsession
At this point, no further setup is required on your server. However, keep in mind that since SSH password authentication is disabled for increased security, you’ll need to have your SSH private key available on any machine that you want to log in from.
We are now done setting up the server and can type
exit or close the terminal window. The rest of the steps will focus on the client for your local machine.
If you’re using Windows on your local machine, you can download the client software from http://code.x2go.org/releases/X2GoClient_latest_mswin32-setup.exe.
After you select your preferred language and agree to the license, a wizard will guide you through each step of the installation process. Normally, there shouldn’t be any reason to change any of the default values pre-filled or pre-selected in these steps.
If you’re running macOS locally, you can find the client software at http://code.x2go.org/releases/X2GoClient_latest_macosx_10_9.dmg.
Double-click the .dmg file to open a folder containing the copyright, license, and X2Go client executable, then double-click the executable to start the client.
And, if you’re using Debian or Ubuntu you can install the X2Go client with:
- sudo apt-get install x2goclient
If you’d like additional information about the clients or you’d like to build from the source, you can visit X2Go’s official documentation.
Now that the desktop client is installed, we can configure its settings and connect to the X2Go server to use our remote XFCE desktop.
When you first open the X2Go client, the following window should appear. If it doesn’t, click Session in the top-left menu and then select New session ….
In the Session name field, enter something to help differentiate between servers. This can be particularly useful if you plan on connecting to multiple machines, since all of the names will be listed in the program’s main window once you save your settings.
Enter your server’s IP address or hostname in the Host field under Server.
Enter the username you used for your SSH connection in the Login field.
And, since it’s what we installed in Step Two, choose
XFCE as your Session type.
Finally, because we log into the server with SSH keys, click the folder icon next to Use RSA/DSA key for ssh connection and browse to your private key.
The rest of the default settings should suffice for now, but as you get more familiar with the software, you can fine tune the client based on your individual preferences.
After pressing the OK button, you can start your graphical session by clicking the white box that includes your session name on the top-right side of the screen.
In a few seconds, your remote desktop will be displayed, and you can start interacting with it. At first login, XFCE will ask if you want to Use default config or One empty panel. The first option will create a rectangular panel docked at the bottom of the screen, containing a few useful application shortcuts (e.g. a file manager, a terminal emulator, a browser, etc.). This option will also add a top panel to the desktop that includes utilities like an application launcher, a clock, a shutdown menu, and more.
Unless you’re already familiar with XFCE, opting for an empty panel can be more complicated since you’ll be starting from scratch. There will be no taskbar, no clock, no pre-configured start menu; it will be up to you to add everything to an empty panel on your own.
Additionally, on Windows and Linux-based operating systems, there are a few useful keyboard shortcuts you can use for a better experience:
CTRL+ALT+F will toggle full-screen mode on and off. Working in full-screen mode can feel more like a local desktop experience. Plus, other keyboard shortcuts will be grabbed by the remote OS instead of the local one.
CTRL+ALT+M will minimize the remote view, even if you are in full-screen mode
CTRL+ALT+T will disconnect from the session but leave the GUI running on the server. It’s just a quick way of disconnecting without logging off or closing applications on the server. The same will happen if you click the window’s close button.
Lastly, there are two ways you can end the remote session, closing all of the graphical programs running in it. You can log off remotely from XFCE’s start menu, or you can click the button marked with a circle and a small line (like a power/standby icon) in the bottom right corner of the main portion of the screen.
The first method is cleaner but may leave programs like session managing software running. The second method will close everything but may do so forcefully if a process can’t cleanly exit. In either case, be sure to save your work before proceeding.
On a final note, although it’s not required, let’s go into XFCE’s control panel, navigate to power settings and disable all standby features. If you don’t use the desktop for a while, XFCE will try to trigger a standby. Although the server normally won’t do anything when it receives this request, it’s better to avoid any unforeseen behaviors altogether.
You now have a working “cloud desktop,” complete with all the advantages of an always-online, remotely-accessible, computing system.
To go a step further, you could centralize your development work by creating a git repository, installing a remote code editor like Eclipse, or configuring a web server for testing web applications. You could also couple your remote desktop with a good backup scheme to make sure that your work environment is available from anywhere and that it’s safe from data loss.
If you’d like to learn more, visit X2Go’s official documentation website.
Thanks for learning with the DigitalOcean Community. Check out our offerings for compute, storage, networking, and managed databases.