When a server can't be patched yet against a critical vulnerability, the advice is to take its sites offline until it can be. SpinupTUI now does that a whole server at a time, or one site at a time, and remembers exactly what it took down, so bringing everything back is one step and never touches a site you'd disabled for some other reason.
Highlights
- Take a server's sites offline (
a). The server actions menu has a new last row, Take all N sites offline. It uses SpinupWP's own disable setting: nginx stops answering for every domain on those sites, so visitors can't connect and no request reaches PHP, including requests aimed straight at the server's IP. Files, databases and certificates are untouched. On a server SpinupTUI took offline, the same row becomes Bring N sites back online. - Or one site (
O). PressOon a site in Servers, Search or Stacks, andOagain to bring it back. PHP is shared by every site on a server, so the confirmation tells you how many other sites are still up and points you toawhen it's the server you need to protect. - It brings back exactly what it took down. Each site is recorded the moment SpinupWP accepts its disable, so an interrupted run can still be undone. A site disabled some other way stays disabled, a failed re-enable stays recorded so running it again finishes the job, and sites taken offline one at a time come back with their server.
- From the command line too.
spinuptui offline <server>… --yesandspinuptui online <server>… --yes, plus--allfor every server and--site <domain>for one site. Without--yesthey print the plan and change nothing.spinuptui offlineon its own lists what's offline. Servers must be named exactly (name, IP or id); a partial name is refused with suggestions. - No alert flood. With Uptime Kuma connected, the affected sites' monitors go into one maintenance window per server. Sites leave it as they come back, and the window is removed when the last one does.
- You can see what's down. Offline sites show
⏻ offin the site list. Servers show⏻ offwhen all their sites are offline and⏻ 3 offwhen some are, and they're listed under the Overview's "Needs attention".
Notes
- Offline means a connection error, not a maintenance page. Visitors see their browser's "can't connect" message. Disabling or re-enabling a site takes a few seconds; SpinupWP works through one server's sites in turn, so a server with 20 sites takes a minute or two.
- The site's PHP-FPM pool and cron keep running. The pool only listens on a local socket, so it isn't reachable from outside.
- Details in docs/taking-sites-offline.md.