Skip to main content

Sonarr 5 and Radarr 7 Are Here: Back Up, Update and Roll Back on QuickBox Pro

Sonarr 5 is in beta, Radarr 7 is on its nightly branch, and neither goes back to the old major without a backup. On QuickBox Pro that backup is one click in the Asset Management Center, the jump is the Update badge on the app's row, and the way back is Restore on the same row. Here is how each step works, the update mistake we fixed along the way, and how your Sonarr and Radarr logins stay yours.

JMSolo 👑7 min read

Sonarr 5 doesn't go back to Sonarr 4 unless you restore a v4 backup. On QuickBox Pro that backup is one click, the update is one more, and if the new major misbehaves, rolling back to the exact version you had is a third.

Sonarr announced the v5 beta on 12 October 2026, almost two years after v4. Radarr 7 is out on its nightly branch too. Both are new majors, both moved to .NET 10, and both raise the same question for anyone running them on a server: what happens to your data, your login and your update tool when the app jumps a major?

What changed upstream

Sonarr 5 is a big release, with nearly 1,000 commits from close to 100 contributors. For an operator, three things matter more than the feature list.

  • No way back without a backup. Sonarr says downgrading from 5 to 4 isn't possible unless you restore a v4 backup, and tells you to take that backup while you're still on 4.
  • Databases can break. Sonarr warns that the several database migrations in v5 can break some databases that were fine on v4.
  • A login is not optional. Basic auth is gone, forms login is the default, there's OIDC, and too many failed attempts lock you out. If you haven't set a login, Sonarr 5 creates a user called sonarr and writes its password to its log at startup. Set the authentication method to None and Sonarr switches it back to Forms.

Radarr 7 is on the same road. Its 7.0.0 build is a GitHub pre-release (7.0.2 is the newest at the time of writing), it bumps .NET to 10, and it adds OIDC. Radarr's master branch still ends at 6.4.4, so on QuickBox Pro you reach Radarr 7 through the Nightly channel.

Back up first, from the dashboard

Sonarr's own advice is to back up before you move, and QuickBox Pro does that for you with a Full Backup. You can start one from two places:

  • Content > Asset Management Center > Application Backups. Expand the app, click Back up now and pick Full backup.
  • The App Dashboard. Expand the app's row, and under Operations click Backup > Full backup.

A Full Backup takes the app itself and its whole config folder (~/.config/Sonarr for Sonarr, database included), minus the transient logs. That's what lets it bring back both the version and the data later. Every SQLite database in it is copied through SQLite's online-backup API, so the copy is consistent even while Sonarr or Radarr is running and writing to it. You don't need to stop the app, and you don't need to cp a database by hand.

From the CLI it's one line:

bash
qb manage software -o backup -o app -u username -s sonarr

Moving to Sonarr 5

Sonarr 5 is still a beta, and it lives on Sonarr's develop branch, which QuickBox Pro calls Nightly. If you want it, do it deliberately.

  1. Take the Full Backup above, while you're still on 4.
  2. On Sonarr's row in the App Dashboard, switch the channel to Nightly. (On a new install, pick Nightly in the install dialog.) Switching the channel and updating moves Sonarr to that channel's latest build.
  3. Click the amber Update badge on Sonarr's row.
  4. Sign in with your QuickBox username and password (more on that below).

The Update badge runs exactly the same update as the CLI, qb update sonarr -u username with the channel you picked, so every guard in the next section applies whichever one you use. A fresh install straight onto Nightly is:

bash
qb install sonarr -u username --nightly

If you'd rather stay on 4, leave the channel on Stable and nothing here changes for you. On the stable branch the newest Sonarr major is still 4, so that's where QuickBox keeps you. The Channels & Versions page explains how channels work.

The mistake we made, and fixed

A user in our Discord had Sonarr update itself to 5.0. QuickBox didn't know Sonarr 5 existed yet. It offered 4.0.20 as an "update", and running it put Sonarr 4 on top of a database that 5.0 had already migrated. Sonarr 4 then logged no such column: MinSize.

That one is on us, and we fixed it the same day. The fix has been in stable since the 3.2.2.9545 release, and it covers Radarr, Lidarr and Prowlarr as well as Sonarr. That user got back by reinstalling 5.0 from Sonarr's own System > Updates. Today the cleaner way back is the Full Backup you took before the jump.

What QuickBox Pro does on every update now

It follows the branch you run. An update reads the branch from the account's Sonarr config.xml, and the Nightly channel is Sonarr's develop branch. On develop, QuickBox offers Sonarr 5, as an update and on a new install.

It never lowers the major. The version QuickBox aims at is the major you already run, or the branch's newest major when that's higher. It's never lowered, and for Sonarr never below 4. The latest version is picked only from that major's entries in the feed, so a 4.x build can't be mistaken for the newest thing on a branch that now carries 5.x too.

It sees what the app did to itself. QuickBox reads the installed version from the app's own update history (read-only, as your account). If Sonarr moved itself to 5.0, QuickBox knows it's on 5.0 and plans from there.

It only offers real updates. The update check shows an update only when the available version is newer than the one you run. That covers Sonarr, Sonarr4K, Radarr, Radarr4K, Lidarr and Prowlarr, so the Update badge never turns up for a step backwards.

It refuses to cross a major downwards. Say you run Radarr 7 and switch it back to master, which tops out at 6.4. QuickBox installs nothing, tells you why, and leaves the app exactly as it was. The message tells you to switch Radarr back to the branch it was installed from, or to update it from inside Radarr.

A failed update doesn't leave the app stopped. If an update stops the service and then finds no usable package, QuickBox starts the service again before it exits. There's nothing for you to do, and the App Dashboard row shows the app running.

If the new major misbehaves, roll back

This is what the Full Backup was for. On the app's row in the App Dashboard, under Operations, click Restore ("Restore from backup") and pick the backup. Rolling back to a Full Backup puts back the earlier version and its data together, so Sonarr 5 becomes the Sonarr 4 you had, on the database you had.

QuickBox handles the parts that usually trip up a manual restore:

  • It clears stale database journals. Before it restores a database, QuickBox removes the -wal, -shm and -journal files beside it. Left in place, those belong to the database you're replacing and can stop the app at start.
  • It waits for the app to answer. QuickBox reports success only once the app is listening on its port again, not just when the files are back.
  • It keeps going if you close the dialog. The rollback runs as a background job on the server, so closing the dialog doesn't stop it.

From the CLI:

bash
qb manage software -o rollback -o app -u username -s sonarr

Your Sonarr login

Sonarr 5 won't run without a login, and you shouldn't want it to. QuickBox gives Sonarr, Sonarr4K, Radarr, Radarr4K, Lidarr and Prowlarr each their own forms login when you install or reinstall them, set to your QuickBox username and password. An update keeps whatever login the app already has, so a login you set yourself stays yours.

If Sonarr moved itself to 5 and now shows a login page you never created, that's the sonarr user it invented. You don't need to dig its password out of a log. On Sonarr's row in the App Dashboard, go to API & Secrets, click Use my QuickBox password again under the password, and confirm with Switch back. Sonarr then signs in with your QuickBox username and password. From the CLI:

bash
qb user apppasswd -s sonarr -u username -o reset

Radarr stays private

Radarr 7's notes add OIDC and a way to bypass authentication for localhost. On QuickBox Pro, Radarr isn't reachable from the outside in the first place: it listens on 127.0.0.1 only, and nginx sits in front of it. Each app's row in the App Dashboard has a Web login switch. With it on, Radarr's page asks for your QuickBox username and password before it opens, and your browser remembers that login across every app with the switch on.

Behind that, Radarr has its own forms login, set from your QuickBox account when it's installed. Keep both on. With the switch on, whatever Radarr 7 changes about its own defaults, your Radarr still sits behind your QuickBox login.

Where to read more

The Sonarr docs and the Radarr docs cover installing, channels and the full CLI. Before you take either app to a new major: Full Backup first, Update badge second, and Restore is there if you need it.

See it running before you decide

QuickBox Pro brings these tools together in one managed platform. The live demo needs no signup, so you can click through the real dashboard first.