Skip to main content

Web terminal

Connect to a registered server directly from the browser as a console, without a separate SSH client. When you are reviewing a vulnerability and need to log in to check a setting or update a package, you can open a console with the same access details without leaving the screen. Use it with services registered as a Server / Host.

  • Connection : Based on the registered SSH access details; private networks go through a gateway (hop)
  • What you need : A service registered as a Server / Host, and SSH authentication for the target server. Not needed if it was saved at registration.
  • Security : Connects with a one-time session ticket; passwords and keys are never passed to the console screen

How to open it​

  1. Open the host / server service and go to [Dashboard].
  2. Click Web terminal at the top to open the connection dialog.
  3. Check the connection target (user@address:port).
    • Credentials saved : If SSH credentials (including gateways) were saved at registration, you can open it without entering anything.
    • Credentials not saved : Enter the SSH password or private key under Target device authentication. If the key has a passphrase, enter it as well.
    • Through gateways (hops) : If you go through gateways in a private network, enter the authentication for each hop as well.
  4. Click Open terminal to open a full-screen console in a new tab.
Web terminal consoleWeb terminal console
A full-screen console opened in a new tab. The top bar shows the connection status, and you run commands on the server without leaving the browser.

How it works​

  • The connection dialog first issues a one-time session ticket, and the new tab uses that ticket to connect to the console.
    • The ticket is valid only once for a short time.
    • The console tab removes it from the address bar immediately.
  • The SSH password, private key, and passphrase stay only on the server side that opens the session and are never passed to the console screen (new tab). So sharing the console address does not expose credentials.
  • The console top bar shows the connection status: connecting, connected, session ended, or error.
Saved SSH credentials are used

If SSH credentials (including gateways) were saved at registration, the console opens without asking for input. If not, you enter the authentication when opening it, and the values are remembered only until you reload or close the page, to prefill the next connection.

Closing the tab ends the session

Closing the console tab or losing the connection ends the session. To reconnect, open a new session with Web terminal on the dashboard.