Choosing a role
Access Bastion provides access to users, including a menu of allowed nodes on the base SSH port. Transit bastion is used for assigned routes to the nodes; it does not have a common menu on the base port. Both options require a working connection to the panel and suitable network reachability, and placing multiple bastions helps organize different entry points and routes, but does not give users new grants.Installation through the panel
In Bastions, select the creation, role and placement node. Specify the desired entry parameters and check the wizard. Automatic installation uses the transport of the selected node: direct SSH or agent tunnel. The setup can use a short-lived root certificate on the pre-built node. This does not change the sshd policy: if root login is forbidden, the connection will be rejected. If the master offers a one-time password or root key and you select it, this is the method used. The server key is checked in both cases. Once installed, check the registered bastion, the status of the services and the availability of the desired listener. If the registration has passed and the service has not started, open the partially created bastion and eliminate the cause. Do not re-register blindly.SSH and Web – separate inputs
Browser terminal and Web SFTP require HTTPS Web login with WebSocket work route and file operations. A regular SSH client requires an available SSH-listener and a firewall rule on the selected port. When you manually install an SSH, the default service listens to the loopback127.0.0.1:2222. For external input, the administrator explicitly sets the address, for example, through SSH_LISTEN in /etc/telepurte-gateway/ssh.env, and configures the network. 2222 is an example of a standard setting, take the actual address from your installation.
The node can also have a dedicated route SSH port, which selects the server immediately, but does not cancel authentication, grant and recording. Open only the necessary route ports on the external network.
Entry policy
Configure the permitted methods: browser confirmation, gateway password, keys and MFA requirement. Details of user login - in the manual SSH. In a browser confirmation, a person checks the attempt on the Telepúrte page. The password of the local login gateway is set separately from the main password of the panel. Imported Axottle users log in via an SSO or client certificate. The guest SSH password is associated only with a temporary grant. Check the limits of simultaneous connections. Reaching the limit prohibits new login, even if the network and password are good.Direct SSH and agent tunnel
In the node card → Connection selects the transport: | Transport | | Requirement When | Applies |---|---|---| | Direct SSH | Achievable address and port sshd nodes | There is a route from the Telepúrte infrastructure to the | server | Tunnel through agent | Online-agent, authorized tunnel and available local sshd | Node does not accept incoming SSH connections from outside | For a separate Telepúrte Agent, the tunnel is turned on in the existing configuration by the fieldsssh_tunnel_enabled and ssh_tunnel_port. The port must correspond to sshd; the agent connects to the local address. After the change, restart the agent and wait for the status update, then switch the transport of the nodes and check the connection.
When an agent tunnel fails, Telepúrte does not switch discreetly to the direct address. Changing transport is an obvious operation, after which a new check is performed. For imported nodes, use the settings of a compatible Axottle Agent, without creating a second agent next to you unnecessarily.
