Contents
Where it is and who can use itChecking for a new version and notificationStarting the updateSteps and progressBackup and safeguardsReturning to the previous versionOn a Linux serverCommon messagesIn-program update: seeing the new version, upgrading with one click and rolling back
An installed HNR checks indir.hnros.com for a new version by itself. An administrator sees the release notes, the download size and the estimated time under Settings › Update; after confirmation the new version is downloaded and applied, and the services restart. The database, settings and secrets do not change; only the program files are renewed.
The program never updates itself. Once a day it only checks whether there is a new version; an administrator always starts the update.
Where it is and who can use it
Settings › Update. Only system administrators see and use this section. In a run that is not an installed package (development or trial environment) the section shows Not an installed package and does nothing.
Checking for a new version and notification
Once a day, and when the section is opened, the program reads the version information on the distribution server; Check now runs the check immediately. The version information is digitally signed: if the signature cannot be verified, no update is made. The screen shows the installed version, the version on the server, the channel, the signature status, the release notes, the download size and the estimated time.
When a new version is released each administrator receives one notification; a New program version attention line also appears in Pulse and the Owner Dashboard. If there is no internet connection the check is skipped quietly: the last successful information is kept and the reason is shown on the screen.
Starting the update
The Update button opens the confirmation step: it shows the number of open sessions, the download size and the estimated time. The services stop for a few minutes; open sessions close and unsaved work may be lost. Start the update at a time when nobody is working. Nothing starts until the confirmation box is ticked.
The download does not need a download license code. If a license code was given during installation, that code is used and checked on the distribution server; it is kept protected on this server and is never written to the screen or to logs.
Steps and progress
The update goes through these steps in order: the version information is verified, the components are downloaded, the package is prepared, the program files are replaced and the services are restarted. The screen shows the downloaded size, the speed and the step log. While the program files are being replaced the server does not answer for a short time; when the connection returns the screen refreshes by itself. The update runs in a separate process, so closing the browser does not stop it.
If the download is interrupted (the connection dropped, the server shut down), restarting the update continues from where it stopped. If the SHA-256 digest of a downloaded file does not match the signed version information, the file is deleted and the installation does not change.
Backup and safeguards
The program files are backed up before they are replaced. If the new version does not start, the program returns to the previous version by itself; the screen shows The new version could not start; the previous version was restored. The database, company settings, secrets and uploaded files are not affected by the update.
Additional components (such as the database server and the PDF reader) are kept in the update cache inside the installation folder (guncelleme/onbellek). If they have not changed in the next version they are not downloaded again, so later updates download much less data.
If you did not choose local PostgreSQL during installation (SQL Server, Oracle, cloud or cluster), the update does not download PostgreSQL and your choice is kept. Details: Database at installation.
Returning to the previous version
After an update the Roll back button removes the installed version and restores the previous one. Only the program files go back; the database and settings do not change. The button appears only when a backup of the previous version exists. Rolling back also asks for confirmation and stops the services for a few minutes.
On a Linux server
If the program was installed under a user account (without system services), the update is done from this screen just as on Windows. If the services were installed as system services under the administrator (root) account, the program cannot give itself administrator rights; the screen shows the commands to run on the server for updating and rolling back, for example:
sudo /opt/hnr/hnr-kur.sh --guncelle
sudo /opt/hnr/yukselt.sh --hedef /opt/hnr --geri-al While the command runs, the progress is still shown on this screen. The installation choices (language, country, channel) and, if there is one, the saved license code are read from what was saved during installation.
Common messages
- The update server could not be reached. Check the internet connection. — Check that the server can reach indir.hnros.com over https and that the firewall does not block it.
- The license code was not accepted. — If a license code was saved during installation, the update is verified with it, and if the code is rejected the update stops. Check in Settings › License that your license is valid; if the problem continues, contact support.
- There is not enough free disk space. — Besides the download size, free space of about twice the unpacked package is needed; free up space and try again.
- An update job is already running. — Only one update or rollback runs at a time; the screen shows the progress of the running job.
- The version on the server has changed; refresh the information and confirm again. — A new version was published while you were confirming; press Check now and confirm again with the new information.
Every update and rollback start, including rejected attempts, is written to the server's audit log with who did it and the number of open sessions at that moment; the license code is not written to this log.
Related guides
- I use it on my own: getting started in 10 minutesFor a small shop, workshop or freelancer using the program alone: the steps from installation to the first invoice and the month end.
- Practical User HandbookThis page is for an employee using the program for the first time and needing to complete daily work safely. Read the common rules here first.
- Your First Day — For People Sitting Down at the Program for the First TimeThis is the first page everyone should read and it takes ten minutes. We are not teaching accounting here, only how to drive the screen: how windows open.
- The Document Chain — The Backbone of the ProgramThis guide is not about one window but about the links between windows. The real gap in a newcomer's head is not "what does this button do" but "I sent a.
- First 10 days: role-based onboarding planA new employee gets a task list for their first 10 working days based on their role. Every item is a real task: it appears in the Tasks window and on the.
- Academy: role-based lessons, exams and certificatesThe academy gathers the lessons for an employee's role in one place, in order. Lesson content is the help center's own sections.