How to Install AnyDesk on Fedora 44

Remote support on Fedora works best when the desktop client, background service, and update source stay aligned after package upgrades. On Fedora 44 and Fedora 43, use the vendor RPM repository on x86_64 systems for DNF-managed updates, or use the Flathub package when you prefer Flatpak packaging and accept its community-maintained status.

AnyDesk publishes a Fedora RPM repository and direct Linux downloads from its official Linux download page, but its Linux support notes currently list Ubuntu 18.04 and newer, Debian 9 and newer, RHEL 8, OpenSUSE 42/15, and Linux Mint 20 and newer as officially supported distributions. Check AnyDesk’s Linux support page before relying on Fedora for business-critical unattended access.

AnyDesk’s Linux support notes state that incoming remote-control sessions require an Xorg graphical session. Wayland sessions can initiate outgoing connections, but they are not supported for incoming sessions. This matters on Fedora 43 and newer GNOME desktops because the former Xorg-based GNOME login session is removed from the default GNOME desktop.

Install AnyDesk on Fedora Linux

Choose an AnyDesk Package Source

The RPM repository is the cleanest default on traditional Fedora Workstation and other mutable Fedora installs because DNF owns the package, service, and updates. Flatpak is useful when you want the Flathub package, when you are on an Atomic desktop, or when you need the Flathub aarch64 build instead of the x86_64-only Fedora RPM repository.

Method	Package Source	Update Owner	Best Fit
RPM repository	AnyDesk RPM repository	dnf	Fedora x86_64 desktops that need the vendor RPM and background service
Flatpak	Flathub com.anydesk.Anydesk	flatpak update	Fedora Atomic desktops, aarch64 systems, or users who prefer Flathub packaging

The official download page also lists direct RPM and tar.gz files. Those are useful for special deployment cases, but they require manual update checks unless you add a managed package source, so the repository method stays first for managed Fedora installs.

Check Architecture and Update Fedora

Confirm the system architecture before adding the repository. The Fedora RPM repository currently resolves for x86_64.

uname -m

Expected output on most Fedora desktop systems:

x86_64

If the command returns aarch64, use the Flatpak method for package-managed updates or review AnyDesk’s direct ARM64 RPM download instead of the RPM repository commands.

Refresh Fedora and apply pending package updates before installing a third-party desktop package:

sudo dnf upgrade --refresh

Review the transaction before confirming. If the update includes a new kernel, graphics stack, or desktop session package, reboot first so AnyDesk starts against the same session and libraries you will use later.

Import the AnyDesk RPM Signing Key

Import the AnyDesk RPM signing key before creating the repository file. DNF uses this key to validate the package signature during installation.

sudo rpm --import https://keys.anydesk.com/repos/RPM-GPG-KEY

Confirm that Fedora stored the current AnyDesk key fingerprint in the RPM key database:

rpm -q gpg-pubkey --qf '%{VERSION}-%{RELEASE}\n' | grep -Ei '^06b5ea2fae208e7cda9761dca2fb21d5a8772835-'

Expected output:

06b5ea2fae208e7cda9761dca2fb21d5a8772835-67a474af

Add the AnyDesk RPM Repository

Create the repository file under /etc/yum.repos.d/. The repository keeps RPM package signature checks enabled with gpgcheck=1. Metadata signature checking stays disabled with repo_gpgcheck=0 because current Fedora DNF5 can report repomd.xml GPG signature verification error against the AnyDesk repository metadata even after the package signing key is imported.

printf '%s\n' \
'[anydesk]' \
'name=AnyDesk Fedora - stable' \
'baseurl=https://rpm.anydesk.com/fedora/$basearch/' \
'enabled=1' \
'gpgcheck=1' \
'repo_gpgcheck=0' \
'gpgkey=https://keys.anydesk.com/repos/RPM-GPG-KEY' | sudo tee /etc/yum.repos.d/anydesk.repo > /dev/null

Confirm the AnyDesk Package Source

Refresh only the AnyDesk repository first. This catches URL, key, and metadata problems before the package transaction starts.

sudo dnf makecache --refresh --disablerepo='*' --enablerepo=anydesk

Expected output ends with:

Metadata cache created.

Confirm that the enabled repository exposes the anydesk RPM for Fedora:

dnf repoquery --disablerepo='*' --enablerepo=anydesk --available --qf '%{name} %{evr} %{arch} %{repoid}' anydesk

Expected output on x86_64:

anydesk 8.0.2-1 x86_64 anydesk

The version can be newer when AnyDesk updates its repository.

Install AnyDesk with DNF

Install the AnyDesk RPM after the repository and source checks pass:

sudo dnf install anydesk

Relevant output includes:

Installing:
 anydesk x86_64 0:8.0.2-1 anydesk 40.9 MiB

Complete!

A first install can also print a package scriptlet line about a missing /etc/systemd/system/anydesk.service. Treat that line as harmless only when the DNF transaction ends with Complete! and the service checks in the next step return active and enabled.

Verify the AnyDesk Package and Service

Confirm the installed package version with RPM:

rpm -q anydesk

Expected output:

anydesk-8.0.2-1.x86_64

The version number may change through normal repository updates. The RPM also installs and enables anydesk.service, which supports connection readiness and unattended-access features configured inside the application.

systemctl is-active anydesk
systemctl is-enabled anydesk

A healthy RPM installation returns:

active
enabled

Install AnyDesk with Flatpak on Fedora

Fedora Workstation and Fedora Atomic desktops include Flatpak, but Flathub is opt-in. The AnyDesk Flathub page marks the app as unverified and states that it is a community package, not officially supported by AnyDesk Software GmbH. Use this method when the Flathub package fits your update or architecture needs better than the RPM repository.

Enable Flathub on Fedora

Add the Flathub remote at system scope if it is not already configured:

sudo flatpak remote-add --if-not-exists flathub https://dl.flathub.org/repo/flathub.flatpakrepo

Confirm the remote is available:

flatpak remotes --columns=name,options | grep -E '^flathub[[:space:]]'

Expected system-scope output:

flathub system

Check the AnyDesk Flatpak Details

Review the current Flathub record before installing:

flatpak remote-info flathub com.anydesk.Anydesk

Relevant output includes:

            ID: com.anydesk.Anydesk
           Ref: app/com.anydesk.Anydesk/x86_64/stable
        Branch: stable
       Version: 8.0.2
       Runtime: org.freedesktop.Platform/x86_64/25.08

The Flatpak version and runtime branch can change. To inspect the current permission context, query the remote metadata:

flatpak remote-info --show-metadata flathub com.anydesk.Anydesk | sed -n '/^\[Context\]/,/^$/p'

Relevant output includes:

[Context]
shared=network;ipc;
sockets=x11;pulseaudio;
devices=dri;
filesystems=home;

Because the Flatpak exposes home-directory access and X11-related permissions, treat it as a Flathub packaging choice rather than a strict isolation upgrade over the RPM method.

Install AnyDesk from Flathub

Install the AnyDesk Flatpak at the same system scope used for the Flathub remote:

sudo flatpak install flathub com.anydesk.Anydesk

The install prompt lists the app permissions before you confirm:

com.anydesk.Anydesk permissions:
    ipc    network    pulseaudio    x11
    dri    file access [1]    system dbus access [2]    tags [3]

    [1] home
    [2] org.freedesktop.login1
    [3] proprietary

Verify the installed Flatpak record:

flatpak list --system --app --columns=application,version,branch | grep -F com.anydesk.Anydesk

Expected output:

com.anydesk.Anydesk    8.0.2    stable

Launch AnyDesk on Fedora Linux

AnyDesk needs an active graphical desktop session for normal use. Open Activities, search for AnyDesk, and select the launcher. Do not start the graphical client with sudo; AnyDesk’s Linux notes state that the client cannot run as root. The first window shows the local AnyDesk address for attended support and the connection field for reaching another device.

Launch AnyDesk from the Terminal

For the RPM installation, start the graphical client from a terminal inside your desktop session:

anydesk

For the Flatpak installation, use the app ID:

flatpak run com.anydesk.Anydesk

Use AnyDesk Command Line Options

AnyDesk’s Linux command line documentation lists options for tasks such as reading the local AnyDesk ID or starting a session by address. Run client-dependent options from the graphical session after AnyDesk has registered the local client.

anydesk --get-id

To start a connection by ID or alias, pass the remote address to the client:

anydesk 123456789

Replace 123456789 with the actual remote AnyDesk address.

Back Up AnyDesk ID and Settings on Fedora

AnyDesk’s backup notes list /etc/anydesk/ for installed Linux clients and ~/.anydesk/ for uninstalled or user-local clients. Back up these folders before reinstalling Fedora, cloning a system, or deleting configuration if you need to keep the same AnyDesk ID, alias, unattended-access settings, or session history.

if sudo test -d /etc/anydesk; then
    sudo tar -czf "$HOME/anydesk-system-config-backup.tar.gz" -C /etc anydesk
    sudo chown "$USER:$(id -gn)" "$HOME/anydesk-system-config-backup.tar.gz"
    chmod 600 "$HOME/anydesk-system-config-backup.tar.gz"
fi

if test -d "$HOME/.anydesk"; then
    tar -czf "$HOME/anydesk-user-config-backup.tar.gz" -C "$HOME" .anydesk
    chmod 600 "$HOME/anydesk-user-config-backup.tar.gz"
fi

The commands are quiet when they succeed and restrict each archive to the current user account. If neither directory exists yet, AnyDesk has not created a local identity or user configuration for that account.

Update AnyDesk on Fedora Linux

For RPM installations, DNF owns the AnyDesk package after the repository setup. Check and apply an AnyDesk update with:

sudo dnf upgrade --refresh anydesk

Normal workstation maintenance with sudo dnf upgrade --refresh also includes AnyDesk when a newer repository package is available.

For Flatpak installations, update only the AnyDesk app with:

sudo flatpak update com.anydesk.Anydesk

Use sudo flatpak update when you want to refresh all system-scope Flatpak apps and runtimes.

Remove AnyDesk from Fedora Linux

Remove the RPM Package and Repository

Remove the AnyDesk RPM first. DNF stops the service and removes the package-owned desktop launcher and binaries during the transaction.

sudo dnf remove anydesk

The manually created repository file remains after package removal. Remove it and refresh DNF metadata:

sudo rm -f /etc/yum.repos.d/anydesk.repo
sudo dnf clean metadata

Verify the package and repository are gone:

rpm -q anydesk
dnf repo list --enabled | grep -i anydesk || echo "AnyDesk repository is not enabled"

Expected output after removal:

package anydesk is not installed
AnyDesk repository is not enabled

Remove the imported signing key only after no AnyDesk package or repository remains on the system:

if rpm -q gpg-pubkey --qf '%{VERSION}-%{RELEASE}\n' | grep -Eqi '^06b5ea2fae208e7cda9761dca2fb21d5a8772835-'; then
    sudo rpmkeys --delete 06B5EA2FAE208E7CDA9761DCA2FB21D5A8772835
else
    echo "AnyDesk signing key is not installed"
fi

Remove the Flatpak Package

Remove the system-scope Flatpak package with:

sudo flatpak uninstall com.anydesk.Anydesk

Verify that the Flatpak app is no longer installed:

flatpak list --system --app --columns=application | grep -Fx com.anydesk.Anydesk || echo "NOT_INSTALLED"

Expected output:

NOT_INSTALLED

Optionally review and remove unused Flatpak runtimes after the app is gone:

sudo flatpak uninstall --unused

Remove AnyDesk Configuration and Identity Files

AnyDesk creates system and user configuration after the service or desktop client starts. These paths can include the local AnyDesk identity, logs, cached device data, and unattended-access state. List existing paths first so you remove only data that is actually present on that Fedora account or system:

The cleanup commands permanently remove AnyDesk identity and configuration data. Back up any listed path first if you plan to reinstall AnyDesk and keep the same local identity, alias, session history, or unattended-access setup.

for path in "$HOME/.anydesk" "$HOME/.var/app/com.anydesk.Anydesk"; do
    [ -e "$path" ] && printf '%s\n' "$path"
done

sudo find /etc/anydesk /var/log/anydesk.trace /var/lib/gdm/.anydesk -maxdepth 0 -print 2>/dev/null || true

If the listed paths are safe to discard, remove them with:

for path in "$HOME/.anydesk" "$HOME/.var/app/com.anydesk.Anydesk"; do
    [ -e "$path" ] && rm -rf -- "$path"
done

sudo find /etc/anydesk /var/log/anydesk.trace /var/lib/gdm/.anydesk -maxdepth 0 -exec rm -rf -- {} + 2>/dev/null || true

Troubleshoot AnyDesk on Fedora Linux

Repository Metadata Signature Error

If DNF reports a repomd.xml GPG signature verification error after using older or upstream repository instructions, check the repository file. Keep package signature checking enabled with gpgcheck=1, and disable only repository metadata signature checking with repo_gpgcheck=0.

grep -E '^(baseurl|gpgcheck|repo_gpgcheck|gpgkey)=' /etc/yum.repos.d/anydesk.repo

Expected source settings:

baseurl=https://rpm.anydesk.com/fedora/$basearch/
gpgcheck=1
repo_gpgcheck=0
gpgkey=https://keys.anydesk.com/repos/RPM-GPG-KEY

After correcting the file, refresh the AnyDesk repository metadata:

sudo dnf clean metadata
sudo dnf makecache --refresh --disablerepo='*' --enablerepo=anydesk

AnyDesk Service Is Not Active

If the RPM client opens but unattended access or incoming connection features do not work, check the background service state:

systemctl is-active anydesk
systemctl is-enabled anydesk

If either check does not return active and enabled, start and enable the service:

sudo systemctl enable --now anydesk

Display Server Not Supported on Fedora

AnyDesk’s Linux support notes state that Wayland sessions can initiate outgoing connections but cannot accept incoming sessions. Check the session type from a terminal inside your graphical login:

echo "$XDG_SESSION_TYPE"

Expected output for an incoming-session-capable Xorg login:

x11

If the output is wayland, use AnyDesk for outgoing sessions or switch to a Fedora desktop environment that still provides a supported Xorg session. On Fedora 43 and newer GNOME desktops, the former Xorg-based GNOME login option is not available by default.

AnyDesk Cannot Connect Through the Network

If AnyDesk opens but sessions fail to connect, check network filtering before changing Fedora firewalld rules. AnyDesk’s firewall documentation lists TCP ports 80, 443, and 6568 for remote connectivity, plus UDP ports 50001 through 50003 for local discovery. Organization-managed firewalls, TLS inspection, deep packet inspection, or blocked outbound access to *.net.anydesk.com can break sessions even when anydesk.service is active.

Compare Other Fedora Remote Desktop Tools

If AnyDesk’s support or display-server limits do not fit your workflow, Fedora has other remote desktop options with different ownership and protocol tradeoffs.

Tool	Best Fit	Fedora Guide
Remmina	Open-source client for RDP, VNC, SSH, SPICE, and multiple saved connections	Install Remmina on Fedora
TeamViewer	Proprietary remote support client with its own RPM packaging and background daemon	Install TeamViewer on Fedora

Conclusion

AnyDesk is installed on Fedora through either the RPM repository with anydesk.service enabled, or the Flathub package with Flatpak owning updates. Before depending on incoming unattended access, confirm that the desktop session and network path match AnyDesk’s Linux support limits.