# 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-10-08

---

A server's console is a screen and keyboard attached directly to your server — it's your way in when SSH won't connect. This article is for anyone who needs to reach a server that's gone quiet over the network.

## Overview

- The console talks to your server the way a physical monitor and keyboard would, so it works even when nothing on the server is listening on the network.
- Use it when:
  - 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 in a new tab.

You can also open it straight from the **Servers** list: open the **⋯** menu on a running server's row and choose **Console**.

Some OVHcloud servers do not offer a console InfraNest can show itself. For those, the new tab opens OVHcloud's own console page instead.

<!-- 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.

## Tips

> [!NOTE]
> Opening the console is written to the audit log as **Console accessed**, so your team can see who connected and when.

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

## Troubleshooting

- **A message says the console could not be opened** — InfraNest shows the reason your provider gave, and that reason usually says where to go instead. **"Failed to request console access"** means the provider refused without a reason: check the integration is healthy on the **Integrations** page, then try again.
- **There is no Console item** — your provider does not offer a console through its API (DigitalOcean, for example). Open the console from the provider's own control panel.
- **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.
- **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.