I can't connect to my dedicated server via SSH or RDP. What should I do?

The most likely cause: a firewall block

On a dedicated server, administrative access - SSH for Linux, RDP (Remote Desktop) for Windows - is a sensitive entry point. This is why we recommend restricting administration ports to trusted IP addresses only, rather than leaving them open to the whole internet. This is a security best practice: it greatly reduces exposure to intrusion attempts.

The trade-off — and by far the most common cause of a failed connection — is that if your public IP address has changed (new router, connecting from a different location, VPN, 4G…), it's no longer on the allowed list, and the firewall blocks the connection. On your end, this often shows up as a connection that "hangs" and then times out, with no clear error message.

A few checks on your end

Before contacting us, a quick check may be enough:

• Try SSH port 22974. To strengthen security, our servers don't use the standard SSH port (22) but port 22974 instead. Be sure to specify it in your SSH client, for example: ssh -p 22974 user@your-server. For RDP, the port remains 3389.
• Are the address and port correct? Make sure you're targeting the right server IP, with the right port (22974 for SSH, 3389 for RDP).
• Are your credentials up to date? Username, password, or SSH key.
• Has your public IP changed? Search "what is my IP address" from the machine you're using, and compare it with the one that was authorized. A dynamic IP changes regularly.
• Is a local or network firewall blocking you? Some corporate or public networks filter outgoing SSH/RDP ports.

The fix: ask us to check the firewall

If everything looks correct on your end and the connection is still impossible, the most effective option is to let us check your server's firewall configuration. Open a ticket with our technical support specifying:

• the type of access involved (SSH or RDP);
• your current public IP address (the one you're trying to connect from);
• the exact error message or the behavior you observe (timeout, connection refused, credentials rejected…).

We then check whether your IP is authorized on the administration ports and, if needed, open access. Real humans look at the configuration with you.

Updated on: 17/07/2026