What should I check when a dedicated server is powered on but SSH never returns?
Power-on state only confirms one part of the startup path. A server can be stopped at a firmware prompt, missing a boot device, waiting for a filesystem, or fully booted with a network/SSH problem. Observe the console before trying repeated resets or starting an installation.
Before you start
- Authorised access to the dedicated server and the named inspection tools.
Instructions
1. Read the current console screen
Use the authorised BMC or provider console and capture the exact stage and message. Check whether POST completes, the expected boot loader starts and the OS reaches a login prompt. Preserve hardware-event evidence before clearing anything.
2. Test only the expected SSH endpoint
From the management workstation, test the known OS address and configured SSH port. This distinguishes a TCP connection failure from later authentication problems, but does not prove the OS is healthy.
Test-NetConnection vps.example.com -Port 22Replace the documentation hostname and port with the verified dedicated-server endpoint. The command does not log in.
3. Follow the identified failure layer
For a boot error, use the distribution/vendor recovery procedure. For a normal OS console, inspect the actual interface, route and SSH service locally before changing boot settings.
Check the result
- The incident is assigned to an evidenced startup or connectivity stage, and the eventual repair restores both console and authenticated OS access.
Troubleshooting
- The console has no signal
- Check power state, viewer connection and platform video behaviour; no signal alone does not establish a failed OS.
- A prompt requests disk recovery
- Stop automated resets and follow the filesystem-specific recovery plan.
Official references
Use the documentation for your installed version when a flag, service name or platform feature differs.