SSH terminal from the Rack Editor

What it is

You can open a full SSH terminal to any device in your rack without leaving the Rack Editor. Select the device, click one button, and a terminal opens in the editor.

The connection runs through the Local Agent (CreaRackAgent.exe) installed on your PC. The Agent sits on your network, so it can reach devices on private IPs that the CreaRack cloud cannot.

Since the 2026 security hardening, the browser never handles SSH credentials for configured devices. It only tells the Agent which device to connect to (the device ID). The Agent then fetches the credentials from the CreaRack server over its own authenticated channel. You are never asked for a password when opening a session, and the password never appears in your browser.

How to set it up (one time per device)

1. Open the rack in the Rack Editor and click the device.
2. In the properties panel, tick the Network Mgmt checkbox.
3. Click SSH Config.
4. Fill in the form: management IP Address, SSH port (22 by default), Vendor (leave on autodetect if unsure), Username, Password, and an optional enable password for Cisco-style privileged mode.
5. Click Test Connection to verify, then Save Configuration.

That’s it. The credentials are stored encrypted on the server. From now on, every SSH session, config backup, and port read for this device works without asking you for them again.

Opening SSH Config requires the Network module permission (View or above) in addition to your Racks access — see [[crearack—conceptos—usuarios-y-permisos]]. With the default role permissions this changes nothing; it only matters for a user whose Network permission was set to None by hand.

How to open a session

1. Select the device in the editor.
2. Click SSH Terminal in the properties panel.
3. The terminal loads inside the editor, connected through the Local Agent. Type commands as in any SSH client — colors and full-screen output work normally.

If the Local Agent is not running, the editor tries to launch it and retries for a few seconds. Close the terminal window or type exit to end the session.

The properties panel also shows a live status indicator (online/offline) next to the device IP. For private IPs, reachability is checked through the Local Agent.

Troubleshooting

“Local Agent not detected”

• Make sure CreaRackAgent is installed and running. It listens on 127.0.0.1:5050.
• If it was just installed, wait a few seconds and click SSH Terminal again.

Device unreachable

• Verify the management IP in SSH Config is correct.
• Check that your PC (where the Agent runs) can reach the device on port 22 — no firewall in between.

Authentication fails on the device

• The stored credentials may have changed on the device. Open SSH Config, update them, and click Save Configuration.

Wrong prompt or garbled commands

• Set the correct Vendor in SSH Config instead of autodetect. Cisco, Arista, and Juniper each use different terminal handling.

“SSH Config” is missing or greyed out

• It needs the Network module permission (View or above), on top of Racks access. Ask an Admin to check your permissions in Users Management — see [[crearack—conceptos—usuarios-y-permisos]].

Related

• [[crearack—racks—dispositivos]] — add devices and set their management IP
• [[crearack—racks—config-backups]] — configuration snapshots over the same SSH channel
• [[crearack—racks—port-mapping]] — read port and VLAN config from the device
• [[crearack—terminal—que-es-terminal]] — the standalone Terminal hub
• [[crearack—terminal—local-agent]] — what the Local Agent is and how to install it
• [[crearack—settings—credential-store]] — where device credentials live

Véase también

• [[crearack—racks—dispositivos]]
• [[crearack—racks—config-backups]]
• [[crearack—racks—port-mapping]]
• [[crearack—terminal—que-es-terminal]]
• [[crearack—terminal—local-agent]]
• [[crearack—settings—credential-store]]