Knowledge Base

Cannot Connect to VDS: RDP and SSH Troubleshooting

This guide explains the key concepts, practical steps and important considerations for cannot connect to vds: rdp and ssh troubleshooting.

Check Server Status

Confirm in the customer panel that the VDS is powered on and running. Allow any restart or maintenance operation to finish.

IP Address and Port

Verify the server IP and management port. RDP commonly uses 3389 and SSH commonly uses 22, but custom ports may be configured.

Credentials

Windows commonly uses Administrator; Linux may use root or another configured user. Check keyboard layout, capitalization and stored old credentials.

Firewall

The operating-system firewall or an upstream network firewall may block the management port. If access is restricted by source IP, confirm that your public IP has not changed.

Is the Service Running?

If Remote Desktop Services or SSH is stopped, a firewall rule alone will not make the service accessible.

Timeout vs Refused

A timeout often indicates that traffic is being dropped or no response is received, while connection refused can indicate that the host is reachable but no service is accepting the connection on that port.

Console Access

If RDP or SSH is unavailable, use a provider console feature when available to repair firewall or service settings.

Restarting

Avoid repeated restarts without diagnosis. Check logs and service state first when possible.

Conclusion

Troubleshoot RDP and SSH systematically: server state, IP, port, credentials, firewall and service. Also review the most recent configuration changes on your İde Bilişim VDS.

Frequently Asked Questions

Before making major changes, record the current configuration and maintain a usable backup. Critical networking, storage and security changes on production servers should be planned and tested carefully.