Version 1.5.0
Latest October 12, 2026BackendSideMon rebuilt from the ground up. The same web dashboard, the same API and the same MonDesk Android support — installed over 1.4 as an upgrade that keeps your settings, with a long list of security hardening and fixes.
Upgrading from 1.4
- Your settings come with you. On its first start, 1.5 imports the listening addresses and ports, HTTPS on/off with the same certificate, the admin username and password, the monitoring interval and retention settings, and the failed-login history still within its retention period. The 1.4 files are only read, never changed
- Servers already added in MonDesk keep connecting — no change needed on the phone
- Passwords with accented or other non-English characters keep working; the stored password is upgraded to a stronger hash on the first sign-in
- Not carried over: the process / connection / firewall snapshot history. It fills up again within a few days of normal running, and the old database could be many gigabytes
- Data now lives in a new folder under
%ProgramData%, readable by administrators only
Security
- The default
admin/adminpassword must now be changed at first sign-in — 1.4 offered the change screen but never actually required it - Sign-in is rate-limited (10 attempts a minute per address), and every sign-in, failed sign-in, firewall change and password change is logged
- Changing the password signs out every other session; sessions also end after 24 hours at most
- Another website can no longer act on your behalf through your open dashboard session
- The firewall page can only delete rules BackendSideMon created — previously any Windows Firewall rule could be deleted through it, including built-in ones
- A mistyped protocol no longer creates an “allow everything” firewall rule; invalid protocols, ports and addresses are rejected with a clear message
- Generating a certificate can no longer overwrite other files on the server, and the HTTPS certificate now includes the details modern browsers expect
Fixed
- Failed sign-ins are no longer lost during an attack. When more than 500 arrived between two checks, the older ones were silently skipped. Missed events are now picked up on the next check, and events from while the service was stopped are collected when it starts
- Disk read/write speed is reported again — it always showed 0 KB/s
- Connections and listening ports no longer vanish from a snapshot on busy servers
- One failing check no longer loses the whole snapshot — for example, with Windows Firewall stopped, no processes, connections or resource figures were recorded at all
- Protected system processes (lsass, csrss, Defender and others) show their real path and architecture instead of
<protected>/Unknown - The first snapshot after start-up no longer records 0% CPU and zero network/disk activity, and network speed no longer spikes when a VPN or virtual adapter connects
- Saving settings that would stop the service from starting is refused; if the configuration file is damaged anyway, the service starts on safe defaults and logs why
- Setting backup retention to 0 no longer deletes every backup, and automatic daily backups no longer run on every restart
- The failed-logins date filter includes the whole selected day
- The service restarts itself automatically after a crash
Changed
- Self-contained — nothing extra to install on the server
- Request logging records each request’s method, path, client address and result, with routine page refreshes kept out of the default log level