RustDesk Relay Not Working? Fix It in 5 Minutes
Quick diagnostic steps to get your RustDesk relay server back online when connections start failing.
RustDesk Relay Not Working? Fix It in 5 Minutes
Your relay was working fine yesterday. Today, nobody can connect. Before you panic, run through this 5-minute diagnostic checklist.
Minute 1: Is the Service Running?
# Docker
docker ps | grep hbbr
# Systemd
sudo systemctl status rustdesk-hbbrIf the service is stopped, restart it:
# Docker
docker-compose up -d
# Systemd
sudo systemctl restart rustdesk-hbbrMinute 2: Check Disk Space
A full disk is the silent killer of Docker containers. RustDesk logs can grow unexpectedly.
df -hIf your disk is >95% full, clear old logs:
sudo journalctl --vacuum-time=3d
docker system prune -fMinute 3: Verify Ports from Outside
Use an online port checker or run this from a different machine:
nc -zv your-server-ip 21117If the port is closed, your firewall rules may have been reset (common after OS updates).
sudo ufw allow 21117/tcp
sudo ufw reloadMinute 4: Check for IP Changes
If your VPS has a dynamic IP (rare but possible), the IP may have changed. Verify with:
curl ifconfig.meCompare this to the IP configured in your RustDesk clients.
Minute 5: Review the Logs
# Docker
docker logs rustdesk-hbbr --tail 50
# Systemd
journalctl -u rustdesk-hbbr --since "1 hour ago"Look for error messages like “bind failed” (port conflict) or “permission denied” (user/group mismatch).
Still Broken?
If none of the above works, the fastest path to recovery is redeployment. With DeployRD, you can spin up a new relay server in under 5 minutes with all your settings preserved. No more guessing.