Hetzner Control Panel Walkthrough: Cloud, Robot and Console

Hetzner Control Panel Walkthrough: Cloud, Robot and Console

Hetzner does not manage everything from one screen. Cloud servers are handled in the Hetzner Console (Cloud), dedicated servers and related hardware tasks in Robot, and account, billing and general topics in the account area, with separate documentation sections for each. The most useful first step is therefore to identify which panel matches the product you actually have, then learn the handful of screens you will return to most often.

Which Hetzner Panel Do You Need?

Hetzner's documentation is organised by platform, with distinct sections for General, Cloud, Robot, Managed, Network & Security and Storage. That structure reflects a real product split rather than a quirk of the documentation.

What you manage Where it lives
Cloud servers, volumes, floating IPs, load balancers Hetzner Console (Cloud)
Dedicated servers, colocation, domain registration Robot
Account, payment and general topics Account area

The Cloud API can manage cloud services and the resources linked to them, such as Floating IPs, Volumes and Load Balancers. The Robot Web Service, by contrast, manages dedicated servers and their related resources. If you are unsure which product you have, the hardware itself settles it: a dedicated root server belongs in Robot, while an hourly cloud instance belongs in the Cloud Console.

Hetzner Docs describes itself as the reference work for Hetzner Online GmbH clients, covering product panels and products including Robot, konsoleH, Hetzner DNS, Hetzner Cloud, Dedicated Servers, Storage Share and Storage Boxes. That makes it the sensible place to look up a specific screen once you know which product family you are working in.

First Login and Account Context

The account area carries general topics such as account management and payment, so this is where you confirm billing details and account-level settings before touching any server. From there, the product you ordered determines whether you land in Cloud, Robot or another panel.

Hetzner's Cloud product page describes the management interface as intuitive and clearly laid out, with all relevant settings configurable and direct server access available. Treat that as a starting orientation rather than a menu map: menu labels and exact button names are the part most likely to drift over time, so look for the function rather than memorising a path.

Cloud Console Tour

The Cloud Console is the working area for cloud servers and the resources attached to them. Because the Cloud API covers the same objects, the panel and the API tend to expose a similar set of concepts: servers, floating IPs, volumes and load balancers.

When you open the console, the practical approach is to work top down: locate the server you want, check its current state, and only then act. Power actions, rebuilds and network changes all live downstream of selecting the correct server, and selecting the wrong one is the most common way to cause an avoidable problem.

Everyday Cloud Console Actions

  • Power management: start, stop and restart the selected server.
  • Rebuild: reinstall the operating system on the server.
  • Snapshots and backups: capture the server state before a risky change.
  • Networking: firewalls, floating IPs and private networks.
  • SSH keys: manage the keys authorised on new and existing servers.

The single most valuable habit in this panel is taking a snapshot before a rebuild. A rebuild replaces the installed system, and the restore path afterwards depends on having something to restore from.

Robot Tour for Dedicated Servers

Robot is the interface for dedicated servers and the resources related to them. Its most important screens are the server overview, the Rescue tab and the Reset tab, because those are the three you will need when a server stops behaving normally.

The Rescue System is activated from Robot by selecting the server and choosing the Rescue item in the server overview. More precisely, you click Servers, select the correct server, open the Rescue tab, choose the correct type and architecture, and activate it.

The Robot Rescue System Step by Step

The Rescue System is a Debian-based Linux live environment that gives administrative access to a server even when the installed system no longer boots. It starts using network boot (PXE) and runs in server memory without touching the drives or the data on them.

Follow this sequence:

  1. Activate the Rescue System in Robot for the correct server, type and architecture.
  2. Reboot or reset the server, because activation only schedules the next boot and does not switch the running system.
  3. Log in via SSH as root on ports 22 and 222 using the password you received at activation.
  4. Alternatively, select an SSH key already uploaded to Robot and log in without a password.

Two timing details catch people out. Activation is valid for only one boot, so a second visit to the rescue environment requires reactivating it in Robot. And if you do not reboot within 60 minutes of activation, the scheduled rescue boot becomes inactive and a later restart boots from the internal drives instead.

If you no longer have access to the server at all, use the reset function in Robot, found under the Reset tab for the correct server. That is what turns a scheduled rescue activation into an actual rescue session.

What You Can Repair from the Rescue System

Once inside, you can mount the installed system's partitions, for example under /mnt, to repair the system, access data, create backups, check hardware or install operating systems.

A common job is resetting a forgotten root password on Linux or BSD: mount the system partition, use chroot to enter the mounted system, and run passwd. For full reinstalls, Hetzner provides Installimage, a script for installing an operating system and customising drives, RAID levels, hostname, partitions and LVM.

Console and VNC Access When SSH Fails

Not every access problem is a boot problem, and Hetzner provides more than one route back in. Besides the Linux-based Rescue System, there is also a vKVM Rescue System, and you can use a KVM Console together with a bootable ISO image of your choice as an alternative to the Rescue System.

This matters when you need to see the screen rather than just a shell, for example to watch boot messages or work through an installer.

Leaving vKVM mode needs care. First restart the VM with Send Ctrl-Alt-Del to avoid damaging the file system, then restart the server using a reset option in Robot such as automatic hardware reset. Restarting from within the operating system is not sufficient to leave vKVM mode; a reset via Robot is required.

Settings Worth Changing Early

A little setup in advance saves a lot of improvisation later.

  • Upload an SSH key to Robot. If a key is already on file, you can select it and log into the Rescue System without a password.
  • Know where reset lives. The Reset tab is your route back in when the server is unreachable.
  • Know where support tickets are opened. Support tickets can be opened via Robot, for example to request that Plesk or cPanel licences be bound to vSwitch or Failover IPs.

Third-Party Panels Are Separate from Hetzner's Own

It helps to separate Hetzner's panels from the hosting control panels you might run on top of a server. cPanel is a web hosting control panel in its own right, and Hetzner's documentation covers its licensing, installation and access on dedicated servers.

Several constraints apply. cPanel must be installed manually by the customer, and Hetzner does not help with installation, since that kind of support is not included with dedicated root servers. cPanel cannot be installed on Windows and is only supported on Linux. As of 15 January 2025, new cPanel and Plesk licences can no longer be purchased from Hetzner, and upgrades and downgrades are no longer possible.

Once installed, WHM is the administration interface reachable on port 2087, and cPanel is the account-level interface reachable on port 2083.

Practical Cautions Before You Click

Panel actions are powerful, and a few deserve a deliberate pause.

  • Rebuild replaces the operating system. Take a snapshot first if the data matters.
  • Rescue activation does nothing on its own. It schedules the next boot, so a reboot or reset must follow, within 60 minutes.
  • Rescue mode lasts one boot only. Reactivate it each time you need it.
  • Closing vKVM is not the same as restarting the OS. Use Send Ctrl-Alt-Del, then a Robot reset.

Where a function is not exposed in the panel, support tickets opened via Robot are the documented route for account-specific requests. Beyond that, the reliable guide to any given screen remains the product documentation for that platform, since menu wording shifts over time while the underlying functions stay recognisable.

Leave a Comment

Your email address will not be published. Required fields are marked *

Scroll to Top