
X2Go
Remote desktop sessions for Linux using the NX protocol
X2Go is an open source remote desktop server for Linux that uses the NX technology protocol. In QuickBox Pro, X2Go is installed as a system service (x2goserver) and is accessed through the X2Go client over a dedicated SSH port.
It is not a browser-based dashboard or web app. Access is provided via the X2Go client using the server host and the assigned QuickBox username.
Overview
X2Go provides remote desktop sessions for Linux servers and is designed for users who need a full GUI environment over an efficient NX-based connection. QuickBox Pro installs the X2Go server packages, enables the x2goserver service, and prepares per-user session directories.
If you need a web UI or browser-based control panel, X2Go is not the right tool. It requires the X2Go client and connects over SSH port 4747. If you do prefer browser-based remote access, check out noVNC for browser-based remote access options.
Key features
QuickBox Pro wires X2Go as a system-managed service with a predictable connection workflow. The install process pulls packages from the X2Go apt repository and keeps the service managed by systemd.
🖥️ NX-based Remote Desktop
Open source Linux remote desktop using the NX technology protocol.
🔐 Dedicated SSH Port
Client connections use SSH port 4747 for X2Go sessions.
⚙️ System Service
Managed by systemd as x2goserver during install and updates.
📁 Per-User Session Files
Creates /home/username/.x2go with an ssh/ directory for user sessions.
📦 X2Go Server Packages
Installs x2goserver, x2goserver-xsession, and pulseaudio via apt.
🔑 Official Repository
Adds the X2Go apt repository in /etc/apt/sources.list.d/x2go.list with keyring support.
When to use it
Use X2Go when you need a full Linux desktop session on a server instead of a web UI. It is ideal for administrators who want a dedicated client-based workflow rather than a browser route.
Good fit when
- You need a remote Linux desktop session instead of a browser UI.
- You can install and use the X2Go client on your personal computer.
- You want a system-managed service that runs as
x2goserver. - You are an administrator and can install admin-only software from the dashboard.
What QuickBox sets up
- QuickBox installs X2Go server packages and enables the
x2goserverservice. - Client connections use SSH port
4747with your QuickBox username. - Session directories are created under
/home/username/.x2go. - X2Go appears in the Package Management catalog for installs and reinstalls.
Installation
X2Go is available in the QuickBox CLI catalog and appears in the dashboard Package Management catalog. The CLI help for X2Go documents install, reinstall, remove, and update actions.
Install from the QuickBox CLI
qb install x2goInstall from the Dashboard
In the dashboard, the Package Management tab lists X2Go and provides Install and Reinstall actions. The catalog is filtered by your group membership — you will see X2Go if your group includes the Remote Access category.
Access and authentication
X2Go access details are provided by the QuickBox access output after install. Use those values in the X2Go client to establish a session over SSH.
URL / route
The QuickBox access output for X2Go provides connection details and does not list a web URL. Access is handled through the X2Go client over SSH.
Login / credentials / tokens
Use the X2Go client and connect with the values provided after install:
4747XFCEMATESecurity notes
X2Go connections use SSH port 4747 as documented by the QuickBox access output.
Configuration and files
QuickBox creates a per-user X2Go directory and SSH subfolder for session data. It also manages repository and service files that are removed during an uninstall.
System-level files and directories created or managed during install/remove include:
-
/etc/apt/sources.list.d/x2go.list -
/usr/share/keyrings/x2go.gpg -
/etc/x2go -
/var/lib/x2go -
/var/spool/x2goprint
Common tasks
Use systemd to control the X2Go server service. Use QuickBox CLI commands for lifecycle operations like update, reinstall, and removal.
Start/stop the service
systemctl start x2goserver
systemctl stop x2goserver
systemctl restart x2goserverUpdate, reinstall, or remove
qb update x2go
qb reinstall x2go
qb remove x2goTypical workflows
- Install X2Go from the CLI or the dashboard Package Management tab.
- Install the X2Go client on your personal computer and connect using host, username, and port
4747. - Choose
XFCEorMATEas the session type when creating a profile. - Use
systemctlto start or stopx2goserverif needed.
FAQ
These answers summarize the connection details and requirements printed by QuickBox during install. If your environment differs, use the access output as the source of truth.
4747 in the access output after install.Best practices
Follow the QuickBox workflow and the supported session types for consistent connections. This keeps your client profile aligned with the settings QuickBox expects.
Do
- Use
qb install x2goandqb update x2gofor lifecycle management. - Install the X2Go client on your personal computer before attempting to connect.
- Select
XFCEorMATEwhen configuring the session type.
Don't
- Do not attempt to connect without the X2Go client installed.
- Do not choose a session type other than
XFCEorMATE.
Troubleshooting
Most issues come down to connection details or session selection. Confirm the values from the QuickBox access output before troubleshooting deeper.
Connection fails on port 4747
Symptom: The client cannot connect to the X2Go server.
Checks: Confirm you are using SSH port 4747 and the server IP shown in the QuickBox access output.
Login fails
Symptom: Authentication fails after connecting.
Checks: Ensure the login username matches the QuickBox username shown in the access output after install.
Session type not available
Symptom: The session does not start or shows errors about the desktop environment.
Checks: Choose XFCE or MATE as the session type in the X2Go client.
Resources
Use these upstream references for client installation and repository details. They match the sources QuickBox uses during install.
Resources
Join the Community
Media server operators sharing configs, getting support, and shaping the future of QuickBox Pro.