Using a Containerized Console#

Once a server is configured for Containerized Consoles (see Setting Up a Console Server), the experience for an end user (customer or staff member) is:

  1. On the server’s management page, click Launch KVM.
  2. SynergyCP creates the session and, as soon as it’s ready, opens the console in a new browser tab automatically.
  3. If the Console Server is still obtaining its certificate, the user sees a message that the session is warming up. The session can be opened from Manage Consoles a moment later, once it’s ready.

The Manage Consoles page lists active sessions and shows, for each one, the server, the Console Server handling it, the source and destination IPs, when it was created, and when it expires. From there a session can be opened (when ready) or deleted.

Console images#

Each server is assigned a Console Image (with a Console Tag) as part of its Launch KVM Action — this is the container that actually runs the session. We provide two images today; both target vintage Java-applet BMCs and are functionally identical apart from the container clock:

  • Legacy Console Image (synergycp/bm-console-container-legacy) — the standard image; the right choice in most cases.
  • Fixed-Date Console Image (synergycp/bm-console-container-legacy-fakedate) — the same image running its clock in the past, for BMCs whose Java applet won’t launch because of expired signed code or date checks.

Session behavior#

A session stays alive for 24 hours. If the same user launches a console again for the same server from the same source IP while a session is already active, SynergyCP reuses that existing session instead of spinning up a new container — and resets its lifetime to a fresh 24 hours. Each session is locked to the source IP that created it and is automatically removed once it expires, even if the user forgets to close it.

Permissions#

Two sets of permissions control access to this feature.

Console Server administration:

  • Read (network.console.read) — view the Console Servers page.
  • Write (network.console.write) — create, edit, and delete Console Servers.

Console session management:

  • Read (network.console_session.read) — view active console sessions on the Manage Consoles page.
  • Write (network.console_session.write) — create and manage console sessions.
  • Delete (network.console_session.delete) — terminate (delete) console sessions.

Assign these to staff groups as you would any other SynergyCP permission. Customers do not need these permissions to launch a console for their own servers.

Backward Setting Up a Console Server Legacy Console Image Forward