How to Fix the RustDesk Error: “Not Ready. Please Check Your Connection”

Ever found yourself in a rush to handle something remotely, only to open RustDesk and see the message "Not ready. Please check your connection"—leaving you stuck and anxious, not knowing what to do?

Don't worry—this issue isn't complicated. This notification typically means that RustDesk is unable to register with its ID server. This could be due to network restrictions, incorrect server settings, or issues with your self-hosted infrastructure. Read on to learn about the necessary checks and how to resolve the problem.

Why does RustDesk need to check connections

Why does RustDesk display "Not ready, please check your connection"? This message typically appears when the RustDesk client fails to establish communication with its ID (rendezvous) server. Several issues can cause the status to remain stuck as "Not ready":

• Internet or network issues: Unstable connections, restrictive firewalls, VPNs, proxies, or DNS problems may prevent RustDesk from accessing its servers.
• Public server issues: Temporary problems with RustDesk's public infrastructure can affect device registration.
• Incorrect self-hosted setup: An incorrect ID server address, a public key mismatch, or inconsistent settings across devices can interfere with registration.
• Server service or port configuration: If a self-hosted hbbs service is unavailable, or if required ports are blocked, the client may fail to register successfully.
• Outdated or incompatible versions: Mismatches between client and server versions can lead to compatibility issues, particularly during troubleshooting or server upgrades.

How to Fix RustDesk “Not Ready” Errors

Based on this error, this guide outlines the following steps; it is recommended to try them in the order presented. Please note: once RustDesk returns to a "ready" state, you should stop—try to avoid changing multiple settings at the same time.

Step 1: Check Your Internet Connection and Restart RustDesk

1. 1.Open a website or another application to verify that your internet connection is working properly.
2. 2.Close RustDesk completely, then launch it again.
3. 3.If the status remains unchanged, restart your computer.
4. 4.Try switching to a different network (for example, a mobile hotspot).

If RustDesk works correctly on another network, the issue may lie with your original network connection, firewall, DNS, VPN, or proxy settings.

If devices on multiple, unrelated networks all show the same error when using the RustDesk public servers, please check RustDesk's official channels and try again later.

Step 2: Check Whether You Use Public or Self-Hosted Servers

Open the RustDesk Settings > Network menu and check the server configuration. Note that in some versions, modifying these settings may require administrator privileges.

• If using a public server: Check your network connection and verify whether the service is temporarily unavailable. Unless you have configured a custom ID server or a public key, do not enter an arbitrary server address.
• If using a self-hosted server: Verify that the ID server address and public key are correct on both devices. Ensure that both clients are pointed to the same server.

Step 3: Verify the ID Server and Public Key

This step applies to self-hosted RustDesk deployments.

1. 1.On the client, open Settings > Network.
2. 2.Ensure that the ID Server field contains the correct server hostname or IP address.
3. 3.Verify that the public key matches the key generated by your RustDesk server.
4. 4.Check that any other remote devices are using the same ID Server and key.
5. 5.Save the configuration and restart RustDesk.

RustDesk typically stores the server's public key in a file named id_ed25519.pub. If the server key has been changed, existing clients may need to be updated to match it.

It is best to avoid regenerating the server key or deleting the key file, as doing so could invalidate the configurations currently in use by other devices.

Step 4: Check the RustDesk Server and Required Ports

If you are managing your own server, please ensure that its services are running. If you are using a public server, you may skip this step.

RustDesk Server consists of two main components: hbbs, which handles ID registration and connection coordination, and hbbr, which provides relay services when a direct connection cannot be established.

Check the service status or container logs for any startup errors. Additionally, verify that your server firewall, cloud security groups, Docker port mappings, and router forwarding rules are correctly configured and consistent.

At a minimum, RustDesk typically requires TCP ports 21115–21117 and UDP port 21116; depending on your specific deployment and the features in use, additional ports may also be required.

Step 5: Check DNS, VPN, and Firewall Restrictions

If your server configuration is correct, the next step is to examine the network path.

• Verify that the server hostname resolves to the expected IP address.
• Test the connection from an approved network—without using a VPN or proxy—to see if the behavior changes.
• Check for firewall or antivirus rules that might be blocking RustDesk traffic.
• If you are hosting RustDesk at home, ensure that your router has a public IP address and that port forwarding is correctly configured.
• For self-hosted setups, issues such as incorrect public hostname resolution, missing port forwarding, or Carrier-Grade NAT (CGNAT) can prevent incoming connections from reaching the server. If the problem only occurs when connecting via a public hostname from within the same local network, it may involve NAT loopback or split DNS.

Use restrictive "allow" rules for the necessary traffic; do not leave your firewall disabled.

Step 6: Update RustDesk and Recheck Its Configuration

Update the RustDesk clients on both endpoints to a stable, compatible version. For self-hosted deployments, check the server version and logs before proceeding with the RustDesk upgrade.

If only one device consistently fails, try noting down its current settings, re-entering the server information, and testing it again. Reinstalling the application is also a viable option.

If the issue persists—and provided that you do not specifically require RustDesk's open-source or self-hosted capabilities, or simply wish to avoid spending hours maintaining a server—exploring alternatives to RustDesk might be a more practical solution.

AweSun: A Simple and Easy-to-Use RustDesk Alternative

RustDesk appeals to users who value open-source software and want to maintain control over their own remote access infrastructure. While highly flexible, it requires a certain level of technical expertise, and troubleshooting issues can involve more complex steps.

AweSun, by contrast, takes a different approach. It is a simple, easy-to-use remote desktop solution that eliminates the need for ongoing server or network maintenance.

Why is Awesun a good alternative to RustDesk?

Complex troubleshooting can be a hassle; switching to a different remote access solution might be a more convenient alternative. AweSun is a lightweight, quick-to-install, and easy-to-use tool—an excellent choice if you need a fast replacement for RustDesk to handle urgent tasks.

• Simple Setup: Just download, install, and log in—connect your devices in three easy steps, with no need to deploy your own servers.
• Cross-Platform Access: Supports major platforms including Windows, macOS, Android, and iOS, allowing for seamless connections across different devices.
• Unattended Access: Configure authorized computers in advance to connect whenever and wherever you need.
• High Frame Rate & High Resolution: Native support for streaming at up to 4K/144 FPS or 8K/60 FPS, ensuring smooth, high-definition visuals—perfect for remote work, technical support, and more.
• High-Speed File Transfer: Easily transfer files directly or via simple drag-and-drop during a remote session.

While switching to AweSun won't fix the underlying issues with RustDesk, it does offer an alternative way to connect. Please note that if the root cause lies in a faulty remote computer or an unstable network, using a different application may not necessarily resolve the problem.

Connect in Three Quick Steps: A User Guide for AweSun

1.Download and install AweSun: Install the appropriate version on all the devices you wish to connect.

2.Log in and configure your devices: Follow the on-screen prompts to log in and authorize the remote computer.

3.Start a remote session: Initiate a connection by selecting a device from your list or by entering the remote device ID as prompted. You can also set up "unattended access" in advance to ensure you can connect anytime, from anywhere.

FAQ

Why Does RustDesk Say “Not Ready” on Only One Computer?

The issue may lie with the network connection, DNS settings, VPN or proxy configuration, or the RustDesk version on this specific device; you only need to troubleshoot this particular computer. If a custom ID server is being used, please verify that the server address and public key match those on a device that is working correctly.

What is the difference between “Not Ready” and “Failed to Connect to Relay Server”?

“Not Ready” typically indicates an issue during the ID server registration phase, which occurs before a remote session begins. A “Failed to Connect to Relay Server” error, by contrast, occurs at a later stage.

Do both of RustDesk's server components need to be running?

In a standard self-hosted deployment, hbbs handles ID registration and connection coordination, while hbbr provides relay services. If hbbs is unavailable, the client may remain in a “Not Ready” state. If only hbbr is unavailable, the registration process might still succeed, but sessions that require a relay connection will fail to be established.

How to determine if an issue is specific to RustDesk?

While keeping the remote computer and network environment unchanged, try connecting to the same remote computer using a different remote access application (such as AweSun). If the other software connects successfully, the issue may be related to RustDesk's configuration or its connection services; if it also fails to connect, you should check the host, network, firewall, and access permission settings.

Conclusion

You initiate a remote session to get tasks done—not to waste half your time troubleshooting connection issues. If RustDesk is disrupting your workflow, why not explore an alternative? Give AweSun a try on your go-to devices and see if it's a better fit for your needs.