AnyDesk — Remote Display Server is Not Supported on Linux (Ubuntu) and How to Fix It

thowfick official
4 min readMar 5, 2025
AnyDesk — Remote Display Server is Not Supported on Linux (Ubuntu) and How to Fix It

AnyDesk — Remote Display Server is Not Supported on Linux (Ubuntu) and How to Fix It

Are you experiencing an issue with AnyDesk where the remote server display is not supported, particularly when using Wayland on Linux distributions like Ubuntu? This is a common problem due to the stricter security policies of Wayland compared to Xorg. Fortunately, there’s a way to resolve it. In this detailed guide, we will walk you through the steps to enable AnyDesk to function smoothly within a Wayland session. We’ll also address enabling automatic login for a more seamless experience.

Why Does This Issue Occur?

AnyDesk relies on screen capture and input control to provide remote access. Wayland, the default display server in modern Linux distributions like Ubuntu, has security mechanisms that prevent applications from capturing the screen directly. This results in the “Remote Display Server is Not Supported” error. To bypass this limitation, adjustments must be made to the system configuration.

Step 1: Open the Terminal

Press Ctrl + Alt + T simultaneously to open a terminal window. This will allow you to execute the necessary commands.

Step 2: Access Configuration Files

To start, you will need to access and edit the configuration files for the GDM (GNOME Display Manager). These files control how the login session and display server operate. Open your terminal and list the GDM configuration directory to ensure you’re in the right place:

ls /etc/gdm3

If the gdm3 directory exists, you are using GNOME Display Manager, which controls Wayland settings.

Step 3: Edit the Custom Configuration File

Using a text editor such as nano, open the custom.conf file within the GDM configuration folder:

sudo nano /etc/gdm3/custom.conf

You will now see the configuration file, which contains settings related to Wayland and user sessions.

Step 4: Enable Wayland Support

In the custom.conf file, locate the line that controls Wayland settings. If the line is commented out (preceded by #), remove the # to leave the default setting unchanged:

WaylandEnable=false

Why This Step is Necessary

By removing the #, you unlock access to the Wayland security settings. This adjustment allows AnyDesk to function properly within a Wayland session by permitting screen sharing and remote input. Without this change, AnyDesk cannot initiate a remote session.

Step 5: Set Up Automatic Login

For convenience and to streamline the login process, you can enable automatic login. This ensures that your system logs into your account automatically, preventing any additional authentication steps that might interfere with remote access.

Modify the following lines in custom.conf, replacing $USERNAME with your actual username:

# Enabling automatic login
AutomaticLoginEnable=true
AutomaticLogin=$USERNAME

Benefits of Automatic Login

  • Ensures that the system is always ready for remote access without manual intervention.
  • Prevents AnyDesk from failing due to authentication restrictions.
  • Useful for headless systems or remote servers where physical access is limited.

Step 6: Save and Reboot

After making the necessary modifications, save the custom.conf file by pressing Ctrl + X, then Y, and Enter to confirm the changes. Restart your system for the changes to take effect:

sudo reboot

Step 7: Unlock Security Settings in AnyDesk

After rebooting your system, open AnyDesk and adjust the security settings to ensure smooth operation:

  1. Open AnyDesk.
  2. Navigate to Settings.
  3. Click on Security.
  4. Click Unlock Security Settings (you may be prompted for a password).
  5. Enter your system password and confirm the changes.

This step ensures that AnyDesk has the necessary permissions to function correctly in a Wayland session.

Reverting Changes if Issues Arise

Sometimes, modifying these settings may cause certain system options to stop working properly. If you experience unexpected behavior or issues after making these changes, you can revert them by following these steps:

Step 1: Open the terminal

Ctrl + Alt + T

Step 2: Edit the custom.conf file again

sudo nano /etc/gdm3/custom.conf

Step 3: Revert any modifications by restoring the original commented-out settings. For example, add # back before the WaylandEnable=false line and disable automatic login if necessary.

Save the file (Ctrl + X, then Y, then Enter).

Step 4: Reboot the system

sudo reboot

After AnyDesk usage is complete, restoring the original configuration ensures your system functions as expected.

Conclusion

By following these steps, you should be able to resolve the “Remote Display Server is Not Supported” issue when using AnyDesk on Linux distributions like Ubuntu. Modifying Wayland settings and enabling automatic login can significantly improve your remote desktop experience.

If you found this guide helpful, feel free to share it with others facing the same issue.

Happy remote working!

Free

Distraction-free reading. No ads.

Organize your knowledge with lists and highlights.

Tell your story. Find your audience.

Membership

Read member-only stories

Support writers you read most

Earn money for your writing

Listen to audio narrations

Read offline with the Medium app

No responses yet

Write a response