IPMI (Intelligent Platform Management Interface) and its KVM-over-IP console give you access to your dedicated server at the hardware level — independent of the operating system, network stack, or whether SSH is currently responding. This is essential for troubleshooting a server that’s genuinely stuck.
What IPMI can do that SSH can’t
- Show you the actual console output/screen, including boot messages and kernel panics, even before an OS has finished loading.
- Perform a hard power cycle or reset, equivalent to pressing the physical power button, when the OS is completely unresponsive.
- Mount a virtual ISO/CD remotely, useful for OS reinstalls or rescue-mode booting.
- Monitor hardware sensors — temperatures, fan speeds, power supply status — independent of OS-level monitoring.
Accessing the IPMI interface
Your dedicated server provisioning email includes a separate IPMI IP address, username and password — distinct from your server’s normal network login. Log in to this address via a web browser (it hosts its own management interface, typically over HTTPS on a non-standard port).
Launching the KVM console
Inside the IPMI web interface, look for “Remote Console” or “KVM Console” — this launches a Java or HTML5-based viewer showing exactly what a monitor plugged directly into the server would display, along with virtual keyboard/mouse control.
Performing a safe reboot
Where possible, reboot from within the OS itself (reboot via SSH) rather than IPMI, since a graceful shutdown lets services and the filesystem close cleanly. Reserve IPMI’s power-cycle option for when the server is genuinely unresponsive to SSH and a normal reboot isn’t possible.
Keep IPMI credentials secure
IPMI access bypasses your OS’s own login and firewall entirely, so treat its credentials with at least the same care as root access — change the default password immediately, and restrict access by IP allow-list if your provider’s IPMI interface supports it.