naptify-server 1.0.47, 1.0.48 and 1.0.49 are out. They include improvements that make database writes more reliable. If you are on 1.0.47 or earlier, we recommend updating to 1.0.49.
What’s changed
1.0.49 (2026-10-10)
- Before each hourly backup, the server now finishes writing to the database and empties the file that holds unfinished writes (main.sqlite-wal). In 1.0.48, on busy servers the write could stall and this file could keep growing.
- If the write could not be completed, a warning now appears in the admin screen’s operation log.
1.0.48 (2026-10-09)
- Safer data handling: the server first writes changes to a separate file (main.sqlite-wal) and later merges them into the database itself (main.sqlite). Until now, if that merge failed, nothing was shown anywhere. From 1.0.48, a failure appears as an error in the admin screen’s operation log.
- When the server is stopped or restarted, it now always finishes that merge before exiting. This also applies to restarts from the admin screen and to OS restarts.
- Fixed an error shown when opening the admin address with /admin/ at the end (the operation log screen now opens).
- Shortened the channel setting “Private (hide from the list)” to “Private” (in all 9 languages).
1.0.47 (2026-10-09)
- The totals in the admin screen’s bottom bar (logins, transfers and so on) now use a short notation for each language and fit on one line.
- On a phone-width admin screen, the values in the network cards now wrap instead of being cut off.
Before you update
- Updating works as before: stop the server, replace the executable (exe) and start it again. No data migration or settings change is needed.
- When you move the data folder to another PC, or copy it as a backup, always stop the server first. While it is running, recent changes may still be in main.sqlite-wal, so copying only main.sqlite would miss them.
Download
Go to the official download page from the NAPTIFY product page.