JSOPanel Get started

Release notes.

What changed in JSOPanel, one version at a time. Newest first.

v0.1.247 4 October 2026
  • New: restore one mailbox from a backup. Choose "One mailbox" in the restore options and pick the address from the list. Only that mailbox goes back, and every other mailbox is left alone. It works for both kinds of backup copy. The old "Mail only" choice is now called "All mail".
  • A deleted mailbox comes back too, with the password it had on the day of the backup. Its domain must still be on the account.
  • Safe to undo: the mailbox being replaced is saved first (the newest three are kept), and undoing the restore puts back only that mailbox.
  • Fixed: a backup could contain other customers' mailbox addresses and password records from the same server, if their details included the account's name. Backups now keep only the account's own. Older backups still contain them; they are never listed or restored, and they go away as those backups age out.
v0.1.242 3 October 2026
  • New: a customer who has been blocked on the server (for example after mistyping a password a few times) can now lift the block on their own IP address from your billing system, where they can still log in - an "Unblock my IP" button in the WHMCS and ClientExec modules and a tab in the Blesta module. Off until you turn it on, in two places: tick "Check and release a customer's own blocked IP address" on the API token, and tick the new option on each product that should offer it.
  • It only ever lifts blocks the server made by itself (a Fail2Ban ban or the shared list of known-bad addresses). A block you set by hand stays, and the customer is told to contact you. Each release is limited to one address, five times an hour per account and three times an hour per address, is refused for suspended accounts, and is written to the Audit Log.
v0.1.233 3 October 2026
  • The file manager's Extract button now also works on a plain `.gz` file, not only `.tar.gz` and the other archive formats it already handled.
v0.1.232 3 October 2026
  • Fixed PHP 5.6 and 7.4 staying on "always ready" workers forever once moved onto their own, separate PHP program - even after the server's default (or an account's own choice) was already set to "start when needed." Switching an account onto its own PHP program now puts every website it already had back exactly the way the account's own setting says, not however it happened to be before the move.
  • Added a way to re-apply every account's "always ready / start when needed" PHP workers setting to its real websites right now, for any website left behind by the fix above or by anything else that changed since - `jsopctl php-pm reapply`.
v0.1.231 3 October 2026
  • Fixed PHP's "shared pool, not currently running" message so it names the real number of websites using that PHP version, instead of a blanket claim that could be wrong in either direction.
  • Fixed "Remove this PHP version" silently never moving stranded websites to another version, even when it reported finding them - removing a version now actually moves any website still on it, rather than leaving it behind.
  • Faster bulk actions across the whole server (e.g. turning the visitor check on or off for every website at once) on servers with many accounts, from fixing one setting that was being re-checked far more often than it needed to be.
v0.1.230 3 October 2026
  • Fixed PHP 5.6 and 7.4 showing none of the "Workers per site" style settings on Service Configuration -> PHP, where every other PHP version shows eight of them. They now match.
  • Fixed saving a Service Configuration setting being able to try to start a currently stopped service instead of leaving it stopped - for a service with no quick way to confirm it started, this could make Apply sit for up to a minute and a half. Saving now leaves a stopped service stopped and says so plainly.
  • Fixed a confusing message on PHP's "Workers per site" style settings: saving one named a PHP program as "not running" even when real websites on that same PHP version were working normally. It now explains that the setting only affects a shared, unused program - every website already runs its own, separate one.
v0.1.229 2 October 2026
  • New: choose how PHP workers are kept, for the whole server and for each account. "Always ready" (the way every server has always worked) keeps a couple of workers waiting for each website; "Start when needed" keeps none until a visitor arrives, which uses far less memory for quiet sites and lets an account with many sites run under a low process limit. The server default is on Service Configuration, PHP tab; one account is set under Accounts, Manage, Limits. Changing the default moves only accounts set to follow it - an account with its own choice stays as chosen. A newly installed server starts on "Start when needed"; servers already installed keep "Always ready" until you change it, so nothing changes on them unless you use it.
  • Fixed Adminer showing "Session expired" straight after signing in from the panel.
v0.1.228 2 October 2026
  • Suspending a reseller now also suspends every account underneath them - including a sub-reseller's own customers - the same as suspending any account already stops their sites, mail, databases and cron. Unsuspending the reseller brings back only the accounts that were suspended along with them; any account already suspended on its own, for its own reason, stays suspended.
  • Fixed the firewall refusing a real Moodle course save because of how two of its own built-in settings happen to be named - "Group mode" and "Force group mode" both contain a sequence of letters the firewall reads as an attempt to run a server command. Saving a course, including those two settings, is no longer blocked.
v0.1.227 1 October 2026
  • Fixed a bug where editing a Node.js application could delete it entirely if the new settings were rejected - a mistyped port or file name, for example, now leaves the existing application exactly as it was, with nothing lost.
v0.1.223 1 October 2026
  • A reseller can now be trusted to turn SSH and terminal access on or off for their own customers directly, instead of every request going through support. Off by default for every reseller - an administrator turns it on for one reseller at a time, from their Manage dialog. It never reaches a sub-reseller's own account, and never the reseller's own account either - only their ordinary, direct customers.
v0.1.221 1 October 2026
  • Node.js Applications: Start and Stop now grey themselves out when pressing them would not change anything - Start once the app is already running, Stop once it is already stopped - so it is obvious at a glance which one will actually do something.
  • The "x" to remove a Node.js version no longer appears next to your server's own system-installed version, since that one was never something this panel could remove - pressing it used to fail with a confusing "is not installed" message.
v0.1.220 1 October 2026
  • The two Node.js versions a server sets up by default are now 26.10.0 (current latest) and 24.21.0 (current LTS) - the previous default, 25.x, reached its own end of life and is no longer installed anywhere by this panel. Already-running servers pick up both automatically on their next upgrade, not only a brand new install.
  • Fixed `node-versions list` sometimes showing the same Node.js version twice, once correctly and once mislabelled "system" - it was reading whichever version happened to be the current default rather than the server's own distro-installed copy.
  • The "Install Node.js" action under Services now defaults to the current LTS line when no version is given, instead of the same now-end-of-life 25.x.
v0.1.219 1 October 2026
  • Node.js Applications: you can now edit an existing app's name, domain, port, entry point, start script, folder or Node.js version in place, instead of deleting it and creating a new one.
  • Fixed a bug where a server's own system-installed Node.js version could stop appearing as a choice once a second, managed Node.js version was installed - nothing was actually removed, the list just stopped showing it.
  • A fresh server install now sets up two Node.js versions by default instead of one, so there is a real choice available from the start.
  • Fixed the server-wide firewall sensitivity setting (anomaly score thresholds) silently never taking effect, on every server - the setting was always accepted and saved, but the underlying protection kept using its old, more sensitive default instead of the configured value.
v0.1.218 30 September 2026
  • Migrating a domain in from DirectAdmin, cPanel or Enhance now brings its real DNS records across, not just JSOPanel's own defaults. An external mail provider's own MX, a third-party verification record, and any other custom record a client had added are kept exactly as they were; only the website's own address and JSOPanel's own SPF, DKIM and DMARC records are updated to this server.
  • Fixed outbound mail authentication (SPF) not including the relay address configured under Outbound Mail, on both new domains and a DNS zone reset.
  • Transferring an account between two JSOPanel servers now also moves the domain's SPF record to the new server's address - it used to keep naming the old one.
  • Fixed a rare, brief outage that could affect every website using the automatic bot-protection feature at once, even though the feature itself was never actually down - one momentary hiccup reaching it was enough to make it look briefly unreachable to every site relying on it. The same fix was applied to the standby/failover feature's own connection back to a live server.
  • Updated the Joomla installer to its latest release.
v0.1.217 30 September 2026
  • Updated the Drupal installer to its latest release.
  • Updated the phpBB installer to its latest release.
  • Fixed a bug that sent a webmail warning email on every upgrade, even when nothing was actually wrong.
Page 5 of 5

Want to see it running for yourself?

Get in touch and we'll walk you through it.