Short answer: first check that the server is running and finished setting up (a new Windows server needs 10–20 minutes), then copy the address, username and password again without spaces, and make sure nothing blocks port 3389. Error 0x204 means the app can't reach the server; "credentials did not work" means it reached it but the login failed. If you're stuck, restart the server from the dashboard, wait two minutes and try again.
Remote Desktop error messages are famously vague. The good news: almost every failed connection to a VPS comes down to a handful of causes. Work down this list in order; most people are connected again by step 3.
01First, Read the Error
| What you see | What it means | Go to |
|---|---|---|
| Error code 0x204 (Mac, iPhone, Android) | Can't reach the server | Fixes 1–4 |
| "Remote Desktop can't connect to the remote computer" (Windows) | Can't reach the server | Fixes 1–4 |
| "The credentials that were used to connect did not work" | Reached it, login rejected | Fix 5 |
| "The user account is not authorized for remote login" | Login valid, user not allowed | Fix 6 |
| Connects, then black screen | Session is up, display isn't | Fix 7 |
| "CredSSP encryption oracle remediation" | Security update mismatch | Fix 8 |
| "No Remote Desktop license servers available" | Too many sessions | Fix 9 |
| Was fine yesterday, now times out | Server stopped, renewed late, or rebooting | Fix 1, then 10 |
021. Is the Server Ready and Running?
A new Windows server takes about 10–20 minutes after payment to install. After a reinstall, the same again. After a restart, give it two minutes; after Windows updates, up to 15.
Check the server page in your dashboard: it should say ready and running. If it shows suspended or expired, renew it from the balance first.
032. Copy the Address Exactly
- Copy the IP address from the server page rather than typing it.
- If the address has a port, like
203.0.113.18:3389, keep the port. - No spaces before or after. Paste into a text editor first if you're unsure.
043. Restart the Server from the Dashboard
A restart from the dashboard fixes more RDP problems than any setting.
If the server hung, a Windows update stalled, or a firewall rule went wrong, a restart from the dashboard (not from inside Windows) brings it back to a known state. Wait two full minutes, then connect again.
054. Check What's Blocking Port 3389
RDP uses TCP port 3389. Things that can block it:
Your own network
Office, school and hotel Wi-Fi often block 3389. Try your phone's hotspot to test.
A VPN on your computer
Some VPNs block outgoing RDP. Disconnect it and try again.
The Windows Firewall on the server
If you changed firewall rules, you may have closed 3389. Restart from the dashboard; if that doesn't help, contact support or reinstall.
A changed RDP port
If you moved RDP to another port, add it to the address: IP:PORT.
Quick test from a terminal on your own computer:
# macOS / Linux
nc -vz 203.0.113.18 3389# Windows PowerShell
Test-NetConnection 203.0.113.18 -Port 3389"Succeeded" or "open" means the port is reachable and the problem is the login (fix 5). A timeout means something between you and the server blocks it.
065. "The Credentials That Were Used to Connect Did Not Work"
The server is reachable; Windows rejected the login.
- 1Copy the username from the server page. On our Windows servers it's
Administrator. - 2If your PC adds a domain, type
.\Administratorso Windows uses the local account. - 3Copy the password from the server page; paste it rather than typing it. Watch for keyboard layout differences (Y/Z, special characters) if you do type.
- 4If you changed the password inside Windows, the dashboard still shows the first one. Use your new one.
- 5If you tried many wrong passwords, Windows may lock the account for a while. Wait and try again, or restart the server.
076. "The User Account Is Not Authorized for Remote Login"
You created a new Windows user, but it isn't allowed to use Remote Desktop. Log in as Administrator and add the user to the Remote Desktop Users group (Computer Management, Local Users and Groups), or use the Administrator account.
087. Connected, but the Screen Is Black
- Wait 30 seconds; the first login after setup builds the user profile.
- Press Ctrl + Alt + End (Windows client) to bring up the security screen, then cancel.
- Lower the resolution or turn off "use all monitors" in your RDP app's display settings.
- On Mac, turn off "Optimize for Retina displays" for that connection.
- Still black: disconnect and reconnect, or restart the server from the dashboard.
098. CredSSP / Encryption Oracle Error
This appears when one side has a security update the other lacks. Install the latest Windows updates on your own computer. Don't weaken the policy on your PC to work around it; updating is the real fix.
109. "No Remote Desktop License Servers Available"
Windows Server allows two simultaneous administrator sessions without extra licences. If you see this message, someone else (or an old session of yours) is still logged in. Log off other sessions, or restart the server.
1110. It Worked Yesterday
Server renewed late or expired
Check the paid-until date on the server page.
Windows rebooted for updates
Wait 15 minutes.
Your IP changed
and you had restricted RDP to your old one. Update the firewall rule.
Password changed
by you or a script. Use the current one.
12Still Stuck?
Open a ticket in the dashboard or message us on Telegram with the server name, the exact error text and what you've tried. Don't send your password. For first-time setup on each device, see How to Connect to a Windows RDP Server. Once you're in, secure your RDP server so the login screen isn't open to everyone.
Connected, but everything feels sluggish? See Remote Desktop Slow or Laggy? 9 Fixes.
Microsoft's Remote Desktop apps on Mac, iPhone and Android show 0x204 when they can't reach the server at all: it's off or still setting up, the address is wrong, or a firewall or network blocks port 3389.
- remote desktop can't connect
- rdp error 0x204
- rdp not connecting
- remote desktop credentials did not work
- rdp black screen
- rdp connection error