Skip to content

← Production Guide · VM lifecycle

PG-31 · Console does not open?

Console does not open? Operational lesson: A console is a chain of hops. The API answer or the proxy log says which one refused.

Operational lesson. A console is a chain of hops. The API answer or the proxy log says which one refused.

The memo as text

Situation. The noVNC page stays blank, fails at once, or the token "is invalid or has expired". The instance itself is not affected: only its console.

First checks (read-only):

  1. Can the API build a URL?: openstack console url show <server-id>
  2. Is its nova-compute up?: openstack compute service list --host <compute>
  3. Why the proxy refused: nova-novncproxy.log, on the controllers
  4. The guest's VNC server: virsh vncdisplay <instance-name>

Think before acting:

  • ⚠️ State-changing. Restarting the console proxy disconnects the open consoles.
  • ℹ️ Know this. Through Kolla-Ansible's HAProxy, a session is cut after one hour. Users reconnect with a new URL.

Go deeper

This memo is a memory aid. The procedure, with every command, its risk warning and its limits, is in the runbook:

Where this holds. The runbook is a draft, written from the Nova 2026.1 remote console guide and source and from Kolla-Ansible 2026.1; it was not reproduced on a lab. It follows noVNC, Kolla-Ansible's default; SPICE is covered only by equivalence. Causes covered: an expired token, a public URL the browser cannot use, a proxy that cannot reach the compute's VNC ports, the compute down or VNC off, the proxy down. VNC TLS, serial consoles and Horizon's own configuration are not covered.

LinkedIn kit

"The console doesn't work." It is one of the vaguest tickets an OpenStack team gets, and usually nothing is wrong with the instance.

A console connection is a chain of four hops:
→ the browser opens the public URL of the console proxy
→ the proxy checks the token, and its lifetime
→ the proxy connects to the compute, on the guest's VNC port
→ the guest's own VNC device, in libvirt

Each one fails differently: a blank page, an Origin error, "the token is invalid or has expired", a connection refused. The API's answer, then the console proxy log, tell you which hop refused.

Start with the most boring cause: a URL opened too late, or reused.

Source runbook status: draft.

Runbook: https://github.com/OzarLand/ozarland-academy/blob/main/docs/runbooks/lifecycle/console-not-available-or-disconnects.md
More memos: https://github.com/OzarLand/ozarland-academy/tree/main/docs/production

#OpenStack #Nova #Troubleshooting #CloudOperations #SRE #OzarLand

Source: console-does-not-open.yml. Found an error, or does your platform behave differently? Open an issue or see CONTRIBUTING.