# Open a server's console

> The console is a screen and keyboard attached directly to your server — the way in when SSH won't connect.

Source: https://infranest.io/docs/server-console
Last updated: 2026-08-30

---

The console gives you direct screen-and-keyboard access to a server, for the times when you can't reach it any other way. It's for anyone managing servers in InfraNest who needs a backup way in.

## Overview

- The console connects to your server the way a monitor and keyboard would, so it works even when nothing on the server is listening on the network.
- It's the way in when SSH won't connect, the network is misconfigured, or the server won't finish booting.
- Availability depends on your provider — not every provider supports it.

## When you need it

Use the console when the normal route is closed:

- SSH refuses connections, or you've locked yourself out with a firewall rule.
- The server won't finish booting.
- You changed the network configuration and lost the connection.
- You need to see boot messages or use single-user mode.

## Open the console

1. Go to **Servers** and open the server.
2. Open the actions menu (**⋯**) and choose **Console**.
3. InfraNest requests access from your provider and opens the console.

<!-- manual-screenshot: server-console — needs a live provider console session, which a seeded demo org cannot produce — capture by hand -->

If you'd rather use your own tool, the **Console access** panel gives you what you need: a **WebSocket URL** for a browser terminal, or a **VNC host**, **VNC port** and **password** for a VNC client. Each has a **Copy** button.

> [!NOTE]
> Console credentials are temporary. They're requested when you open the console and expire shortly after. If the connection drops, request access again rather than reusing an old URL.

## Good to know

- **Availability depends on the provider.** The console is offered where the provider supports it — on others, the menu item won't appear.
- **You still need to log in.** The console gives you the screen; your normal server login still applies.
- **It's recorded.** Opening the console is written to the audit log as **Console accessed**, so your team can see who connected and when.

## Troubleshooting

- **"Failed to request console access"** — usually the provider refusing. Check the integration is healthy on the **Integrations** page, then try again.
- **The console is blank** — the server may be powered off. Power it on and reopen.
- **Keyboard input does nothing** — select inside the console area first so it takes focus.

> [!TIP]
> If you're locked out by your own firewall rule, the console lets you fix it without needing SSH at all.