Latest
v2.4.8
Released 2026-11-1610Security1New4Improved9Fixed
Security10
- SecurityEnabling or resetting an API key, and widening its IP allowlist (adding an address or clearing it), now asks for your current password or authenticator code first; admins managing a user's key enter their own. Narrowing the allowlist needs no confirmation
- SecurityPrefetch URLs now only accept ports 80, 443 or the site's configured listen ports, and nodes refuse to prefetch to ports they are not listening on
- SecurityThe master now checks node-reported site/tenant/global bans against the config delivered to that node and no longer broadcasts mismatched ones
- SecurityThe master only tracks attack state and rate limits for sites delivered to the reporting node, with capped tables; node uplink batches now have item-count limits
- SecurityThe Add Node install command now downloads this version's install script and verifies its sha256 before running it, and only uses https download addresses (no command is given when only http addresses are configured)
- SecurityOnce a node connects with its renewed certificate, the previous certificate is invalidated immediately: it can no longer connect, renew or download the agent, and sessions still using it are closed
- SecurityAgent downloads authenticated with a node certificate now check the node registry: nodes deleted in the panel or moved back to pending can no longer download
- SecurityThe re-run install command on the master System Update page now verifies the install script checksum and refuses to run it on mismatch
- SecuritySite health check host now rejects spaces, line breaks and other control characters so they cannot be injected into probe request headers
- SecurityNode list adds a Revoke Certificate action: it invalidates the selected nodes' current certificates and closes their connections; nodes recover by automatically obtaining a new certificate with their identity key. The action is recorded in the operation log
New1
- NewError pages gain a "Direct access by node IP" page: customize the 200 page returned when a node is accessed directly by IP (region/node overrides supported); leave empty for the built-in minimal page
Improved4
- ImprovedPackage "Bandwidth" is now labeled "Business bandwidth" (buy package, my packages, package editor, sold packages) to tell it apart from node bandwidth
- ImprovedOn the attack log page, Export CSV now sits on the right of the list tab bar next to Refresh, so the page header no longer takes up its own row
- ImprovedNew single-host deployment guide: super admin, materials site, website and demo master on one machine (nodes still need a separate machine), with install order, per-step success markers, shared MariaDB and memory tier notes, and a port table
- ImprovedUninstalling the master now also removes the demo environment on the same host: demo timers and units, the outbound firewall table, the demo script directory and the demo panel's nginx site (nginx is reloaded only if its config test passes); the demo snapshot is removed only with --purge
Fixed9
- FixedLeak-protection custom regexes and replay-guard path regexes now reject octal escapes above ASCII (e.g. \344), which never matched on nodes
- FixedWhen exporting a certificate private key with a wrong password, the error now shows how many attempts are left
- FixedAfter the security-event JSONL file is rotated away or deleted, new events go to a fresh file instead of the rotated one
- FixedRule regexes with \x escapes of 0x80 or above are now rejected on save (master and node matched them differently, so the rule silently never fired on nodes)
- FixedDouble-clicking "Add to line" in the pending IP pane of the line settings page no longer resets the progress of the batch already in flight; the batch completes item by item as usual
- FixedMaster uninstall --purge now keeps MariaDB when it still holds other databases (such as the super admin's on the same host), removing only the master's own database, account and config snippets
- FixedDemo master seed data follows the current API: cache rules attach through a platform cache group and demo plans include custom CC rule quota; the demo outbound firewall unit takes effect right after setup instead of after a reboot
- FixedOn the demo master, commands sent to the synthetic demo nodes are no longer recorded as failed tasks, so the error log no longer shows "queued task finally failed" every minute
- FixedNode log lines for request bodies rejected with 413 because they exceed the site upload limit are no longer counted as platform errors; they are now classified as transport noise, and the node log summary files them under the client category
No changes of this type