Dedicated Server Console Access

When a dedicated server will not boot or has lost its network, SSH is no longer an option and you need a console attached to the machine itself. This guide explains the two console routes Kapsule offers, when to use each, and how to request a hands-on console session.

Why Console Access Exists

Almost everything you do on a dedicated server happens over SSH. That works right up until the moment it does not: a kernel upgrade that will not boot, a firewall rule that locked out port 22, a broken /etc/fstab that drops the machine into an emergency shell, or a filesystem that needs checking before the network comes up.

Console access is the out-of-band path for exactly those situations. It attaches to the machine below the operating system, so it keeps working when the operating system does not.

Where to Find It

1. Sign in to KPanel.
2. Click Dedicated Servers in the left sidebar.
3. Click the server you need, or its Manage link.
4. On the server overview page, click Console.

The direct address is /dedicated/<server>/console. There is also a Console access tile in the Tools grid on the same overview page.

Two Routes, One Page

The console page gives you two options, and it is important to understand which one you actually want.

vKVM, the virtual console. This is the fast path. The rescue system can boot the machine into a browser-reachable virtual console that you activate yourself, immediately, with no waiting. It handles the large majority of real problems: a machine that will not boot, a broken configuration file, a filesystem that needs repair, a bootloader that needs reinstalling.

A physical console session. Bare-metal hardware has a physical KVM console that a technician attaches on request. There is no instant self-service API for that on physical hardware, so this route means opening a request and waiting for a person. Use it when vKVM genuinely cannot help.

Start with vKVM. Ask for the physical console only when the virtual one is not enough.

Using vKVM

The console page has a Need something right now? card with an Open rescue / vKVM button. That takes you to the Rescue system section of the server's Manage page.

1. In the Rescue system card, open the Rescue system dropdown and choose vKVM (virtual console).
2. Optionally paste one or more SSH public keys, one per line, to authorise root login in the rescue environment.
3. Click Activate rescue.
4. If you did not supply a key, a one-time root password is shown. Copy it immediately: it is displayed once and cannot be retrieved later.
5. Click Reset now to enter rescue to reboot the machine into the rescue environment.

When you are finished, come back to the same card and click Deactivate, then reset the server again so it boots the installed operating system rather than the rescue environment.

The full rescue workflow, including the plain Linux rescue images, is covered in Managing a Dedicated Server.

Requesting a Hands-On Console

If vKVM is not enough, request a physical console from the same page.

1. In Request console access, describe briefly what you need it for. The field is optional, but a sentence like "the server is not booting after a kernel update" gets you help far faster than an empty request.
2. Click Request console access.
3. A support ticket is created and its reference is shown in a confirmation toast.

Our team attaches a console and sends you the connection details.

Every request you have made is listed under Your requests with its reference, subject, and status:

Click View ticket on any row to open the full support conversation, where you can add detail or reply.

Who Can Request a Console

Requesting console access needs the dedicated server write permission on the account. If your role is read-only, the button is disabled and hovering it explains why. Ask an account owner to make the request, or to change your role.

What to Do Before You Ask

A little preparation makes the session much shorter.

• Note the exact symptom. "Boots to a grub prompt", "hangs after the disk check", "responds to ping but not SSH" all point at very different fixes.
• Note what changed. A kernel update, a firewall save, an /etc/fstab edit, or a disk that filled up are the usual causes.
• Check the obvious remote things first. Is the machine powered on? The Power state on the overview page tells you. If it reads Powered off, a graceful restart from the Manage page may be all you need.
• Have a backup position. If you are about to try something risky, know what you would restore from. Bare-metal servers are not covered by site backups: see Cloud Server Backups for how server-level backups work.

When Console Access Is Not the Answer

Some problems look like console problems and are not.

• You locked yourself out with a firewall rule. The upstream firewall on the Manage page filters traffic before it reaches the machine, so you can fix the rule there and regain SSH without a console at all. Keep Allow platform services switched on to avoid this class of lockout entirely.
• You want to start again from a clean operating system. That is a reinstall, not a console session. It is under Advanced on the Manage page, behind a typed confirmation, and it erases every disk.
• The server is fine but a website on it is broken. That is an application problem. Start with your logs.

Getting More Help

Console access is one of the places where talking to a person is quicker than clicking. If you are unsure which route you need, open a ticket from Support in KPanel or email support@kapsulehost.com with the server name and server number from the overview page, and describe what the machine is doing.

For the rest of the toolset, see Managing a Dedicated Server and Dedicated Servers Overview.