Installing AnyDesk on Ubuntu Server 24.04 for Session-Based RDP Connections

AnyDesk does not support native RDP or session-based multi-user connections on Ubuntu Server. To achieve simultaneous remote desktop access for multiple users, you must use xrdp, an open-source RDP server that integrates with the existing display manager. This approach provides standard Remote Desktop Protocol compatibility and true concurrent sessions.

Why AnyDesk Is Not Suitable for Multi-User RDP

The core misunderstanding in many initial requests is conflating proprietary remote access tools with open-standard protocols. AnyDesk is designed primarily for individual technician-to-machine support or single-user remote work. It lacks a command-line interface flag for passwordless authentication, meaning manual interaction is always required for the first connection. Furthermore, it does not implement the Remote Desktop Protocol (RDP) natively. Instead, it uses its own proprietary protocol over port 6568. Attempting to force AnyDesk into a multi-user RDP scenario will fail because it does not manage Linux display sessions in the way an RDP server does. When you connect via AnyDesk, you are typically sharing or taking control of the current physical console session or a specific virtual session managed by the host software. It does not spawn independent X11 or Wayland sessions for each incoming client. Consequently, if two users attempt to connect simultaneously, they will either fight for control of the same screen or one will be rejected entirely. There is no max_sessions configuration file for AnyDesk because the architecture simply does not support parallel user isolation. For organizations requiring multiple users to log in and work simultaneously on a headless Ubuntu Server, the industry standard solution is xrdp. This software acts as a bridge between the Windows RDP client and the Linux graphical environment. It allows each user to establish their own distinct session, complete with their own desktop environment, processes, and login state. This directly addresses the requirement for session-based connectivity that AnyDesk cannot provide.

Installing and Configuring xrdp

To set up a robust multi-user remote desktop environment, you need to install the xrdp package along with a compatible window manager. Ubuntu Server installations often lack a default graphical interface, so you may also need to install a lightweight desktop environment like XFCE or GNOME, depending on your resource constraints. For this guide, we assume you have already installed a desktop environment such as xubuntu-desktop or xfce4. First, update your package lists to ensure you are installing the latest stable versions. Run the following commands in your terminal:

sudo apt update
sudo apt install xrdp xfce4 xfce4-goodies

The xfce4-goodies package includes additional plugins and enhancements that improve the remote desktop experience, such as better clipboard handling and session management. Once the installation completes, you must enable and start the xrdp service. Unlike some services that start automatically upon installation, xrdp often requires explicit activation.

sudo systemctl enable xrdp
sudo systemctl start xrdp

You should verify that the service is running correctly by checking its status:

sudo systemctl status xrdp

If the service is active and running, you can proceed to configure the firewall. By default, Ubuntu Server blocks incoming connections unless explicitly allowed. You need to open port 3389, which is the standard port for RDP traffic. Use UFW (Uncomplicated Firewall) to permit this traffic:

sudo ufw allow from any to any port 3389 proto tcp

This step is critical. Without opening port 3389, your RDP clients will time out when trying to connect. If you are using a different firewall solution, ensure that inbound TCP traffic on port 3389 is permitted. For more information on troubleshooting network connectivity issues on Ubuntu Server, see our guide on Ubuntu Server 22.04 Unreachable via SSH After Time, which covers common firewall and networking pitfalls.

Configuring Security and Permissions

Security is paramount when exposing a remote desktop service to the internet. By default, xrdp stores SSL certificates in a directory that may not have the correct permissions, leading to connection errors. You need to fix these permissions to ensure smooth operation.

sudo chmod 600 /etc/xrdp/rsakeys.ini
sudo chmod 755 /var/run/xrdp/sockdir

Additionally, you should restrict access to trusted IP addresses if possible. While UFW allows broad rules, you can tighten security by allowing only specific subnets. However, for most small to medium deployments, relying on strong passwords and potentially implementing fail2ban is sufficient. Fail2ban can monitor xrdp logs and ban IPs that attempt repeated failed logins. Install fail2ban using:

sudo apt install fail2ban

Create a jail configuration for xrdp at /etc/fail2ban/jail.local to protect against brute-force attacks. This adds a layer of defense that proprietary tools like AnyDesk do not offer out-of-the-box for server environments.

Connecting Multiple Users Simultaneously

Once configured, any user with valid system credentials can connect using a standard RDP client. On Windows, use "Remote Desktop Connection." On macOS, you can use Microsoft Remote Desktop or FreeRDP. On Linux, various clients like Remmina are available. When a user connects, xrdp creates a new Xsession. This means User A sees their own desktop, and User B sees theirs. They do not interfere with each other. This is the fundamental difference between AnyDesk's session sharing model and xrdp's session spawning model. If you encounter issues where users cannot log in, check the /var/log/xrdp-sesman.log file for errors related to session creation. It is also important to note that headless servers may require a dummy graphics driver if no physical monitor is attached, as some desktop environments refuse to start without detecting a display. Installing a dummy HDMI dongle or configuring xorg.conf.d to emulate a display can resolve black screen issues during remote login. For monitoring headless setups, refer to Monitoring Headless Ubuntu 24.04 Server with Installed Xubuntu-core for best practices on maintaining visibility without physical hardware.

Frequently Asked Questions

Can I use AnyDesk for multiple users?

No, AnyDesk is designed for single-user remote control or support scenarios. It does not support concurrent sessions for different users working independently. Attempting to use it for multi-user access will result in conflicts over the shared desktop session.

Does xrdp support Wayland?

xrdp has limited support for Wayland. It works best with X11-based desktop environments like XFCE, MATE, or LXDE. If you are using GNOME or KDE Plasma, which default to Wayland on newer Ubuntu versions, you may need to switch to X11 mode in the login screen or adjust xrdp configurations to handle Wayland sockets, which can be unstable.

Is port 3389 secure enough for production?

Port 3389 is the standard for RDP, but it is a frequent target for brute-force attacks. It is essential to pair xrdp with fail2ban, use strong passwords, and ideally restrict access via VPN or firewall rules to known IP ranges. Never expose port 3389 directly to the public internet without additional security layers.

How do I troubleshoot black screens on login?

Black screens usually indicate that the display manager failed to start a session. Check /var/log/xrdp-sesman.log for errors. Common fixes include ensuring the correct desktop environment is installed, fixing permissions on /tmp/.X11-unix, or adding a dummy graphics driver configuration to satisfy the display requirements of the session.

Can I transfer files between my local machine and the server?

Yes, xrdp supports drive redirection. In your RDP client settings, enable "Drives" or "Local Resources" to map your local hard drives to the remote session. This allows you to drag and drop files between your local computer and the Ubuntu Server desktop environment seamlessly.