Two connectivity options
For imported nodes, Axottle Agent is used with a separate binding to Telepúrte. The connection is started from Import Axottle; you do not need to install a second agent just for the sake of integration. For the standalone node, a separate Telepúrte Agent is provided. It is installed from a signed delivery and registered with a one-time code associated with the desired node. Do not transfer the configuration with the identity of one server to another.What to watch in the panel
Agents and the Agent tab in the node card show communication, version and readiness. Verify that the agent of the desired machine is selected. Online status means a recent message, but does not confirm support for all new actions. Before working, check separately:- the presence of the node and the correct binding of the agent;
- the time of the last communication;
- version and support of the desired action;
- local permission for a specific resource;
- the result of SSH preparation, if you need a terminal;
- the status of personal or temporary records, if the entrance goes through them.
Connecting a separate Telepúrte Agent
Take theinstall-agent.sh and a set of one version from the official delivery. As for the panel, first run the --dry-run, then install the selected version and the --bundle. The installer saves the configuration and keys when you update.
Create a private /etc/telepurte-agent/config.json configuration with the control_origin panel address, instance_id installation ID, host_id node ID, and identity file paths. Use your installation values. The file must belong to the service user and have a 0600 mode.
Place the resulting registration code in the protected file available to telepurte-agent and execute:
check checks the files, and the server online will appear after communication with the panel.
Permits for operations
These are the settings of a separate Telepúrte Agent; in the integrated Axottle Agent, use its supported setup procedure. Don’t replace the entire existing configuration with a fragment example.
The permission in the list does not increase the rights of Linux. For privileged typed actions, you need appropriate local assistants with their own policies. To write a file, you also need directory rights and permission to write in the system limitations of the service. Empty lists should not be interpreted as “all is allowed.”
SSH training
Agent training adjusts the trust of the SSH and confirms the node key. Regular heartbeat does not replace this procedure.ca_conflict or config_conflict errors mean that existing settings need to be disassembled before being replaced.
If you have an incomplete change operation with the status of an uncertain result, first check the actual sshd and trust on the machine. A blind automatic repeat can overwrite the already changed state.
For imported nodes, there is a clear mass replacement of the former SSH CA in the agent section, run this only after checking the target composition and compatibility of the Axottle Agent; communication details are here.
Update
Updating the Telepúrte panel does not automatically update individual agents. If the action requires a new feature, first update the agent in a manner supported for its type, wait for a fresh message and repeat the task preview. Changing the policy after preview can givepolicy_changed: create a new goal check. This is the expected execution protection against outdated permissions.
