Release notes.
What changed in JSOPanel, one version at a time. Newest first.
v0.1.336
31 October 2026
- Added: DB Monitor, under Server (administrators only) - every live MariaDB connection on the server, with how long it has been running or idle, what it is doing, and a one-click way to end a connection that is stuck or runs away with the server.
v0.1.335
31 October 2026
- Fixed: the Dashboard's "Largest disk users" card now shows a large account's space in GB once it passes 1024 MB, instead of a long, hard-to-read number of megabytes.
v0.1.334
30 October 2026
- Added: the public API's account details now include real, live usage - disk, bandwidth, file count, and how many domains, subdomains, databases, mailboxes and FTP accounts are in use against the package's own limits. Listing accounts can include the same figures for a whole page at once with `?usage=1`. A reseller account's details also show its combined accounts/disk/bandwidth usage against its own allowance. A domain's own disk usage can be requested the same way when listing an account's domains.
v0.1.333
30 October 2026
- Updated: the Drupal one-click installer now installs the current release (11.4.11) instead of a slightly older one (11.4.9).
v0.1.330
30 October 2026
- Fixed: leaving a DNS Cluster, or removing a single server from one, used to fail every time with a "configuration rejected, it has been put back" error - the change was rolled back with no real explanation. Two settings that depend on each other were being updated in the wrong order, so for a brief moment one referred to something the other had already removed, and the server's own DNS software correctly refused it. They are now updated in the right order, so leaving a cluster or removing one server from it works as expected.
v0.1.329
30 October 2026
- Fixed: Apple's own search indexing crawler (Applebot) could be shown the "just a moment" bot-check page on some sites protected by the automatic bot filter, instead of the automatic filter's own built-in exemption for it actually taking effect. It is now checked against Apple's published addresses independently, so it no longer depends on that built-in exemption working correctly.
v0.1.328
30 October 2026
- Fixed: Google Search Console's "Inspect URL" tool (and, separately, Google's site-verification and ad-review tools) could still be shown the "just a moment" bot-check page on some sites protected by the automatic bot filter, even after the fix for this in the previous release - because Google sometimes sends this traffic from its ordinary, general-purpose crawl network rather than the narrower address range its own documentation describes. That network is now recognised too, for the same three Google tools, checked against Google's own published addresses the same way as before.
v0.1.327
29 October 2026
- Fixed: entering a repository password under "Repository password (recovery)" when nothing was stored on this server yet used to be accepted and saved outright - and sent to the backup server itself, replacing whatever real password's copy was kept there - with no check that it was actually correct. It is now checked against the real backup repository first, over the network, before anything is saved or sent; a password that does not open an existing repository is refused, with nothing written and nothing sent. Pointing this server at a genuinely new, empty backup location is unaffected - it still accepts a fresh password normally.
v0.1.326
29 October 2026
- Fixed: pressing "Initialise" on an off-site backup repository that already has data in it, with the wrong password stored, used to say "could not create the repository" - which reads as a failure to create something, not what was actually happening. It now says plainly that something is already at that remote location and the stored password cannot open it, before you go looking for a reason a brand new repository would not create.
v0.1.325
26 October 2026
- Fixed: a reseller's Dashboard could overstate how much CPU and memory their accounts are combined allowed to use - it added up each account's own individual limit instead of checking the reseller's own combined cap (Packages -> a reseller's own row -> Combined limits), which is the figure actually enforced once that is switched on. A reseller with no combined cap switched on sees no change.
v0.1.324
26 October 2026
- Fixed: a fresh server could end up permanently introducing itself in outgoing mail by the name its hosting provider assigned it (for example a VPS provider's own default), rather than the real name you gave it - because giving a server its name and turning on its certificate were two separate steps, and only the certificate step was ever documented as something to run from the command line. There is now one command for this (`jsopctl set-hostname
`), which also corrects mail along with everything else a rename touches, and the install's own printed next steps now point at it. It also removes the leftover entry your hosting provider's own setup had already written for its own default name, rather than leaving it sitting there alongside the real one.
v0.1.323
26 October 2026
- Fixed: Google's own page-inspection tool, its site-ownership verification fetcher, and its ad-review crawler (AdsBot-Google) could be shown the "just a moment" bot-check page instead of your real site - which made Google Search Console report a page as unable to be checked, and made Google's own site-ownership verification fail, on any site with the automatic bot filter switched on. The automatic bot filter's own built-in defaults already let Google's ordinary search crawler (Googlebot) through, checked against Google's own published addresses - they never covered these other three. All four are now let through the same way, checked against Google's own published address ranges so a visitor merely claiming to be one of them is still challenged, on every site, with nothing to switch on.
- Fixed: a hosting plan's own package could be silently duplicated instead of updated when a name already in use was saved again with different letter case (for example "Basic" after "basic" already existed) - instead of updating the existing one, a second, separate package with the same name was created.
v0.1.320
25 October 2026
- Fixed: suspending a reseller account with many customers under it - including through a billing system's own integration - used to reload the web server once for every single customer account that came down with it. On a reseller with a couple of hundred customers, that meant a couple of hundred full reloads back to back, which could noticeably load the server for the time it took. It now reloads once for the whole group, whatever its size. The same fix applies to bringing a suspended reseller's group back, and to ticking many accounts at once on the Accounts page and suspending or unsuspending them together.
v0.1.290
21 October 2026
- Added: every server now generates a sensible default set of system locales (English regional variants, the major Western European languages, Russian and Polish) instead of only the bare minimum Debian ships with. Without this, an application doing locale-aware date, number or translation formatting for one of these languages silently fell back to a generic default - found live from a customer's own application logging exactly that. Existing servers pick this up automatically on their next update.
- Fixed: the Dashboard's CPU load, Memory and Disk gauges, when switched on for resellers or customers (Panel Settings), used to show the whole server's own figures - the same numbers you see - rather than that reseller's own managed accounts or that customer's own account. They now show only what each of those roles actually manages: a reseller sees their own accounts' combined usage, a customer sees only their own. If you had switched these off specifically because of this, it is now safe to turn them back on.
v0.1.288
21 October 2026
- Added: the "who's using the most right now" overview on Resource Usage now refreshes itself roughly once a minute without reloading the page, so it never resets your scroll position while you are reading it. On a server with more than a handful of accounts to show, it is now split across pages instead of listing every one of them at once.
Page 2 of 5
Want to see it running for yourself?
Get in touch and we'll walk you through it.