Skip to main content
Park nod combines self-connected servers and nodes from Axottle. Here you look for machines, check the readiness of SSH and agent, open the work page, terminal and files. Telepúrte connects existing servers; the purchase of a cloud machine is performed separately, for example through providers Axottle.

Choice of how to connect

To change the directory, you need node control permissions, and the ability to view the park does not give you access to the terminal.

Addendum for SSH

  1. Open Park Node → Add nodes and select an existing Linux server.
  2. Enter the name, address and SSH port. For a batch add-on, fill out a separate card for each machine.
  3. Check addresses: the first time you connect, the wizard automatically pins the SSH node key. There is no separate field for manually entering the host key in the current wizard. For independent verification, check the key with a trusted channel, such as the provider’s console.
  4. Select a password or private key for a one-time connection. The user must be root or have a suitable sudo without a password.
  5. Check the summary and start the preparation. Initial login details are used for this operation and do not become a permanent password for operators.
  6. Wait for the final state and open the node card.
Preparation adjusts the SSH trust to Telepúrte, checks the sshd configuration before use and checks for reconnection. On subsequent connections, changing the fixed key blocks access. If the error occurs later, the node record may remain unprepared - this should be corrected, not considered a successful connection.
Don’t confirm a new host key just because the old one doesn’t fit. Changing the key could mean a server reinstallation, an erroneous address, or another machine. First establish the reason through an independent channel.

Package addendum

Machines are processed sequentially, the results are shown separately. Success on the first servers does not mean the success of the entire pack. Correct specific failed records and verify partial results before repeating. When added to the tag group, Telepúrte applies the group conditions to the selected nodes. The conflicting existing tag should not be imperceptibly replaced: disassemble the conflict before retrying. Unrelated tags are retained.

What states mean

Web SSH requires a validated node, valid user access, and a ready-made bastion at the same time, a suitable agent and rights to every action for a playbook.

Search and organization

Search by name, IP, domain, project, location, and tags. Use source, project, SSH readiness, and agent status filters. For repetitive server selection, enter tags and group, for site locations. The name of the node opens workpage: connection parameters, metrics, processes, services, access, restrictions and history.

Change of address and disconnection

Renaming and descriptive fields do not change SSH identity. Changing IP resets the previous validation and associated permissions, existing connections are closed. Re-check host key and issue the necessary permissions; old grants do not automatically come to life. Disabling the node stops its use in new operations, preserving the history, it does not turn off the Linux server from the provider or delete hosted applications.

Verification

Check the card, host key, SSH-readiness and agent, open the terminal and execute hostname and whoami. After batch connection, compare the successful and unsuccessful results with the original list.

Rollback

Revoke test permissions or disable an erroneously connected node. If the preparation partially changed the SSH on the server, check its configuration through an independent input; deleting a string from the panel does not restore sshd files. Feature availability depends on the panel version, bastions, and agents; older builds may not contain the features described.