Skip to main content
Settings shows the installation ID, the actual number of nodes, users and temporary accesses, the installed build and service settings. View requires security.read, changing the timing and updating - the corresponding control rights. The installation ID is used to identify and recover data.

Before the update

Check the free space, make an independent backup copy of and make sure that the master key is saved. Choose a time when allow a short break: the panel restarts, connections may be interrupted. Auto-update is designed for a standard signed installation with telepurte-updater.service. Non-standard paths or builds without a validation key can block it.If the service is missing, first install the supported delivery with the updater; repeating the button will not add the missing system service.

Update from the interface

  1. Open Settings → Update Telepúrte.
  2. Check the stable release and description of the changes.
  3. Check the current and selected versions.
  4. Confirm restart and installation.
  5. Keep an eye on the steps and the log; after the connection is restored, wait for the final result.
The updater checks the signature and the archive, creates a consistent verified copy, stops the panel and applies migrations to the prepared data, the new version must pass the launch test, returns the original data and the previous binary if it fails. Closing the page doesn’t stop the update. During a restart, the API is temporarily unavailable; the interface resumes reading the status. Don’t run another setup just because of a brief disconnect. The dashboard and the built-in interface are updated. Individual agents and bastions are not replaced by this action - check their compatibility and update separately if necessary.

If the update fails

Download the log and check the result: the previous version is restored or requires intervention. If the panel is not available, use the administrative login to the server:
With recovery_failed, first save the log and the data directories, then restore the consistent installation. Do not remove the service marker for the sake of bypassing the verification, and do not run the old binary on the new database. For standard installation, progress is stored in /var/lib/telepurte-updater/status.json, verified copies are stored in /var/lib/telepurte-update-backups/. Original and unsuccessful data directories are stored separately; see the exact paths in the transaction log. They are not automatically cleared.

Storage periods

In Settings → Storage Periods are available for six independent periods from 1 to 3650 days or indefinitely: The new categories are by default indefinite. Save the policy doesn’t delete everything immediately: the cleanup is done when you start the panel and then every hour in packets. A large amount of accumulated volume can be processed by multiple passes. Free SQLite pages are reused; the size of the database file does not have to decrease immediately. The system journal, backups and update directories have a separate life cycle.

Service plan

Regularly check the location, condition of agents and bastions, queue of tasks and freshness of integration. Check the backup with recovery in an isolated environment. Before reducing storage, hold the necessary records and save the materials of unfinished investigations. After a successful update, make sure you are up to date, transfer the necessary copies to a secure repository and only then clear the unnecessary old directories in their exact ways.

Verification

Check the version in settings, local input and MFA, SSH on test node, one file operation and a reading task. For integration, check fresh import and SSO. Make sure there is no active maintenance status.

Rollback

The auto-update returns the original installation when the update fails. Use the proven master key kit for independent recovery. Extending the shelf life does not return the already cleaned records: you can restore them only from a previously saved copy. The commands refer to a standard Linux installation; the actual paths are checked in your configuration.