· troubleshooting, pro, web-console, ssl

RustDesk Pro Web Console Not Loading: Fixes and Solutions

Troubleshoot the most common issues preventing the RustDesk Pro web console from loading, including SSL, port, and proxy configuration errors.

RustDesk Pro Web Console Not Loading: Fixes and Solutions

You upgraded to RustDesk Pro for the web console. You navigate to https://your-server:21114 and… nothing. White screen, timeout, or SSL errors. Here’s how to fix it.

Problem 1: Port 21114 Not Open

The web console runs on port 21114. This is a Pro-specific port that isn’t needed for the OSS version, so many guides don’t mention it.

sudo ufw allow 21114/tcp
sudo ufw reload

Don’t forget your cloud provider’s firewall too.

Problem 2: SSL Certificate Issues

If you see “Your connection is not private” (ERR_CERT_AUTHORITY_INVALID):

  1. You’re accessing via HTTPS but using a self-signed certificate.
  2. Fix: Use Let’s Encrypt with a reverse proxy (Nginx) in front of port 21114.
sudo certbot --nginx -d console.yourdomain.com

Problem 3: Wrong URL Format

Common mistakes:

  • ❌ http://your-ip:21114 (wrong protocol if SSL is configured)
  • ❌ https://your-ip:21114 (SSL certs don’t work with raw IPs)
  • ✅ https://console.yourdomain.com (correct with Nginx proxy)

Problem 4: API Service Not Running

The Pro web console depends on the API service (hbbs with Pro extensions). Verify:

docker logs rustdesk-hbbs --tail 20

Look for lines mentioning “API” or “web console” startup. If absent, ensure you’re using the Pro Docker image, not the OSS one.

Problem 5: Browser Cache

After fixing configuration issues, your browser may cache the old broken state.

  • Fix: Hard refresh with Ctrl+Shift+R or open in an incognito/private window.

The Managed Alternative

Web console configuration is one of the trickiest parts of a RustDesk Pro deployment. With DeployRD, the console is pre-configured with SSL, proper DNS, and a reverse proxy—accessible from day one.

Get a Working Console →

← Back to Blog