## 0.3.0 (2026-09-29)

### Security
- A burst of sign-in or setup attempts can no longer exhaust the server's memory, and sign-in takes the same time whether or not the account exists.
- The console sends a Content Security Policy, so scripts from anywhere else cannot run in it.
- In a high-availability cluster, a standby installs a release from the active server only after checking its TarleyNode signature.
- API keys can no longer change sign-in settings.
- Updated the WinRM login library, which a malicious Windows host could otherwise use to stop monitoring.
- Wrong passwords for someone's email from another address no longer lock them out. Behind a proxy such as pfSense, set UPSTREAM_PROXY so each person's own address is counted.
- Resetting someone's two-step sign-in also signs them out everywhere else.
- Saved device configurations are stored encrypted, including ones saved before this release.
- The high-availability witness can no longer read or write the cluster's measurements.

### New
- Licences can count sensors, as PRTG does: one for each check on a device, with paused checks free. Settings › License shows sensors used, and adding checks past the licence is refused with the reason. Sensor licences have unlimited users. Licences without a sensor count keep their device and user limits.
- Trials start with an email address and a code, one per machine (locked to its hardware), and are unlimited for 30 days; a new server runs TarleyNode Free until then. Afterwards TarleyNode Free keeps monitoring 100 sensors with unlimited users, for free. Checks over 100 when the trial ends are paused, not deleted, and resume when a licence is activated.
- TarleyNode On call, a phone app your server serves itself: open alerts, acknowledge them and snooze a device; search devices, see their checks and history, pause a check; see sites and business services and put a site into maintenance; with notifications sent straight from your server. Pair phones in Settings › Mobile devices; each can be removed on its own. The gateway's mobile port publishes the app without the console. See docs/mobile.md.
- Support packs: Settings › Support makes a cleaned bundle of diagnostics, shows every file, and sends it to TarleyNode support only when you choose, or you download it and email it.
- Locations on the Devices page, like PRTG's groups: make a tree of places (a building, a floor, a rack) and drag devices, with their checks, onto them.
- Ready-made dashboards: Network, Servers, Internet and websites, and Open alerts, built from your own checks.
- Acknowledged incidents move from the inbox to Archived; nothing is deleted.
- Software updates has Check now, and checks again straight after a licence is activated or a release installed.
- People can change their own password under Settings › Your account, and administrators can set a new one for someone who forgot theirs. Either way the person is signed out on their other devices.

### Changed
- The console, its messages and the documentation now speak of connected sites (Other sites, Connect a site, Monitored from).
- The installation guide gives server sizes for 500 to 10,000 sensors, and the installer warns below the smallest.

### Fixed
- What's new in Settings › Software updates opens again; a release with nothing listed under it stopped it.
- Removing a device closes its open incidents; ones left open that way are closed on upgrade.
- Every card on the Overview opens its list, and the open-source licences are readable, grouped and searchable.
- New status page works before any service exists and explains what to make first; the licence card's figures line up; each phone in Mobile devices shows its account.
- Each release tags its application images with its own version, so the previous release's images stay on the server and going back to it works. Older ones are removed.
- A certificate that fails to install is no longer retried every 20 seconds, which restarted the server each time.
- Feedback with a screenshot larger than about 48 KB is accepted.
- An email alert still reaches the other recipients when the mail server refuses one address.
- Azure health covers every resource in large subscriptions.
- Public status pages are served from a 30-second cache.