How to Fix RustDesk ‘Offline’ Status on Remote Machines

You set up unattended access on a client’s PC last week. Today it shows as “Offline” in your address book. Is the machine off? Is the service crashed? Let’s find out.

Cause 1: The RustDesk Service Isn’t Running

On Windows, RustDesk runs as a system service for unattended access. If the service stopped:

1. Open Services (services.msc) on the remote machine.
2. Find RustDesk Service.
3. Set Startup Type to Automatic.
4. Click Start.

On Linux: sudo systemctl enable --now rustdesk

Cause 2: The Machine Lost Internet

Obvious but often overlooked. If the target PC lost its Wi-Fi connection or the ethernet cable was unplugged, it will appear offline. Verify physical connectivity first.

Cause 3: Firewall Blocking Outbound Connections

Some corporate firewalls block outgoing connections on non-standard ports. RustDesk needs to reach your ID server on port 21116.

Fix: Add a firewall exception for the RustDesk executable, or configure your server to also listen on port 443 (which is almost never blocked).

Cause 4: ID Server Changed or Key Mismatch

If you rotated your server key or changed the ID server IP without updating the client, the remote machine will fail to register and appear offline.

Fix: Update the client configuration with the new server details and key.

Cause 5: “Sleep” or “Hibernate” Mode

A sleeping computer doesn’t maintain network connections. Configure the remote machine’s power settings to prevent sleep when plugged in, especially on desktops used for unattended access.

Pro Tip: Monitoring

Don’t wait for a client to tell you a machine is offline. Use Uptime Kuma or a similar monitoring tool to track the availability of your critical endpoints.

With DeployRD, your server infrastructure is always monitored. The “offline” problem almost always lives on the client side—and this guide has you covered.

Ensure Reliable Connections →