> ## Documentation Index
> Fetch the complete documentation index at: https://docs.axottle.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Web SSH and a regular SSH client

> Terminal tabs, file transitions, connection recovery, bastion entry, and authorization methods.

Telepúrte allows you to work with a server from a browser and a regular SSH client. The connection passes through the bastion, checks the current access and node key, and the terminal output is stored in the session record.

## Open the terminal

Find a node in **Web SSH** or **Park nod** and open the terminal. The node, authorized system login and Web bastion should be ready. With a personal Linux account, wait for the agent to prepare it.

The panel supports multiple terminal and file tabs. Check the node name and system login in front of commands, especially when working with test and work environments at the same time. The first connection is useful to check the commands `hostname` and `whoami`.

Inside the terminal, there are regular interactive server programs that are defined by Linux logging, shell, groups and sudo. Telepúrte does not turn an unprivileged user into a root.

## From terminal to files

The link in the output can be opened with **Shift + click**. The recognized file path allows you to go to the node files or download the file with rights in mind. The current shell directory is needed for the relative path.

If the shell communicates the working directory through OSC 7, it picks up automatically. Otherwise, use **Determine the directory**: the terminal will execute `pwd`. After changing the directory, check that the path is current. The transition opens the same server, but the file operations still pass a separate access check.

Conventional SSH clients show clickable paths differently. If the client terminal does not support such a link, use the printed HTTPS Web SFTP address or open files through the dashboard.

## Short communication break

In a brief network failure, the browser can return to an existing PTY session within about 30 seconds on the same bastion, a continuation of the current terminal, rather than repeating commands.

You can't recover after you've finished a session, restarted a bastion, expired a window, so you need a new login, and two tabs can't assign a single terminal at the same time.

If the connection is lost after the change command, first check the actual result. A browser break does not prove that the command did not manage to execute.

## SSH client connection

Take the address and port in your bastion settings. The example below uses the `2222` conditional port; replace it with the actual one:

```bash theme={null}
ssh -p 2222 operator@bastion.example.com
```

The base port of the access bastion opens the menu of allowed nodes: search, pages and keyboard selection. exit from the node returns to the menu. On the dedicated node port, the server is selected immediately, but user and rights verification remains mandatory.

Telepúrte's SSH login does not open the shell of the bastion's operating system; administrative access to its Linux is serviced separately.

## Ways of entry

| Method | When using | |
| - | - | - |
| Confirmation in | Browser Bastion shows the link, the user logs in to Telepúrte or through Axottle SSO and confirms the attempt of | |
| Separate | Gateway Password For Local Accounting if the method is permitted by the | Bastion Policy |
| Registered Ed25519 | key for local accounting; private key remains on the | client |
| Short-lived | Client Certificate after logging into Telepúrte, including for imported | users |
| Guest SSH Password | Only for selected nodes of the current temporary grant | |

For browser confirmation, the client usually uses `keyboard-interactive`. Open the link shown, check the account and bastion and confirm the login. The main panel password is not entered into the SSH client. MFA is determined by the login policy; Axottle SSO also has an integration policy.

The gateway password is set by the local user in the personal account with the confirmation of the main password and MFA. It must be different from the password of the panel. Changing the main password revokes the gateway password. To log in to the key or password, the policy may additionally require TOTP; the client must maintain the corresponding request.

Imported Axottle user uses an SSO or short-lived certificate, rather than a separate local Telepúrte password. If the certificate is issued through an API, save it next to the corresponding private key and specify `CertificateFile` in the SSH client; the private key does not load anywhere.

## Limitations and recording

There are user session limits, nodes, and bastions, which can prevent a new entry when the old one is running, and SSH key checks are mandatory: don't turn it off to bypass the error.

The terminal output is recorded before delivery to the client. If the recording or re-checking of access fails, the connection is closed. The recording may contain sensitive program output; the rights to view it and the retention periods are configured separately.

## Verification

Check `hostname`, `whoami`, the working directory and the transition to the file. Complete the test session and open its entry in **Sessions**. For the SSH client, additionally check the selected login method, MFA and set of servers in the menu.

## Rollback

Close a session, revoke an unnecessary gateway key or password, or revoke access to a node. Terminal closure does not cancel executed commands or guarantee that a separately running background process will stop.

Compatible versions of the panel and bastion are required; the agent tunnel additionally depends on the agent.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.