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 withtelepurte-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
- Open Settings → Update Telepúrte.
- Check the stable release and description of the changes.
- Check the current and selected versions.
- Confirm restart and installation.
- Keep an eye on the steps and the log; after the connection is restored, wait for the final result.
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: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.
