Skip to main content
Telepúrte is installed as a stand-alone service on Linux. There are two ways: a wizard in Axottle or a signed installer on the server.

What to prepare

You need Linux with systemd, amd64 or arm64 architecture, administrative access and a separate HTTPS domain, such as access.example.com. The domain should be different from the Axottle domain. To automatically configure the certificate in the wizard, prepare an A-record on the IPv4 servers and the available ports 80/443. Dedicated machine simplifies independent maintenance. Installation on the Axottle server is also supported: the wizard asks for confirmation of the match; the panel, bastion and agents are separate components; installation of the panel completes the entry check, and the readiness of the terminal is checked after setting up the bastion and node.

Through Axottle

To view the partition you need settings.view, to install - settings.manage. Open Services → Telepúrte (/new/telepurte).
1

Choose a car.

Select an existing node or Machine Axottle. IP node is substituted from the card. Incorrect address first correct at the source.
2

Set up a domain and DNS

Enter a domain without protocol and path. Create an A-record manually or through the connected area of Cloudflare. Press Check DNS now and wait for the address to match. For the Axottle machine, use the real IPv4 server, not the proxy address in front of the panel.
3

Prepare SSH.

The node uses stored root or sudo props without a password. For an Axottle machine, the wizard separately requests the port, user, password or key and the sudo method.
4

Create an owner.

Set a separate local Telepúrte login and a password no shorter than 15 characters. Login - 3-64 characters, starts with a Latin letter; Latin letters, numbers, dot, hyphen and underline are allowed. Save this SSO-independent login.
5

Check and install.

Compare the machine, domain and available stable release, then start the installation. If the release is not available, eliminate the reason shown and update the check.
Axottle checks the signed release, installs the service, creates the owner, configures HTTPS and panel communication, then checks the availability and reception of the inventory. Supports Caddy/Nginx system and managed Axottle proxy containers. Conflict of someone else’s route stops the installation; the use of a proxy can briefly interrupt connections. Installation log shows the stage and cause of the error, is available for copy and download and is saved after restarting Axottle.

Self-contained installation

Take the install.sh and a set of one version from the official releases of Telepúrte. Use a trusted installer: checking the archive does not protect against swapping the script itself along with the verification key. In the example, replace the vX.Y.Z with the selected published version; the kit directory must contain its archive and signed manifesto.
The installer checks the delivery, creates the service user, configuration, identity and database, installs the systemd services. When you install the owner yourself, create a separate file with a new password that is only available to the administrator, and transfer it through stdin:
The command is executed from the administrative shell, which can read the protected file. Do not pass the password with the command line argument. Once you have created the owner, delete the temporary password file in the way you have installed. Specify in /etc/telepurte/config.json a separate origin:
This is a fragment of an existing configuration, not a complete file. Configure HTTPS via reverse proxy before 127.0.0.1:8097, saving the original Host, or via TLS service settings. External listener requires the absolute paths of tls_cert and tls_key. Without public_url, web entry is not open.
When you first log in, set up the MFA and save the backup codes. bastion and first-node.

Installation data

Save the -consistent backup, configuration, and master key. The key is not part of the normal backup kit. Do not create a new identity on top of an existing installation to fix the login.

Mistake and repetition

Before repeating, find out which steps have already been completed. The partially installed service and the existing owner should not be quietly replaced by a new installation.

Verification

Check HTTPS, local login, MFA and setup settings. For the Axottle wizard, wait for successful completion and fresh synchronization. Then separately check SSH and file operation on the test node.

Rollback

If you fail, save the log, configuration and existing data. To update, the signed installer saves the original directory and returns it if you make an error. Do not restore the old binary on top of the new database scheme manually. Return the entire installation from the verified backup; DNS and external proxy settings are checked separately. Older panel assemblies, bastions, and agents may not contain the features described.