Updates & Changelog

The Updates & Changelog page is your central hub for keeping QuickBox Pro current. It shows the installed version versus the latest available version for both the QuickBox CLI and the Dashboard, displays a browsable changelog with rendered release notes, and lets you trigger updates directly from the browser.

Key features

Update status

The top of the page shows three cards. The first two are status cards, each showing the installed version and, when one is waiting, the latest available version:

• QuickBox — The core command-line tool that manages your server
• Dashboard — The web interface you are currently using
• Maintenance > Actions — The maintenance buttons, described below

When a newer version is available, the corresponding status card highlights the difference and shows an Update button. The button is only there while an update is waiting, so an up-to-date card has no button.

The Maintenance > Actions card always shows two buttons, Fix version and Update QuickBox. Either button opens the maintenance window with that operation already selected, and the window lists every maintenance operation as a choice, so this card is also the way into the two operations that have no button of their own, Fix rTorrent libcurl and Secure PHP. See Maintenance actions.

Changelog browser

The changelog is displayed in a split-pane layout:

• Left panel — A browsable list of changelog entries, newest first
• Right panel — The selected entry rendered as formatted markdown

Browse through entries to review what changed in each release before deciding to update.

Available in your next update

When your installation is behind by one or more versions, the dashboard gathers the release notes for every version between the one you have installed and the latest available, and groups them under an Available in your next update heading at the top of the changelog list — with a badge showing how many pending releases are waiting. This lets you read exactly what each pending update contains before you download and apply it, so you are never updating blind.

• The group appears above your installed version and release history, so the changes you have not applied yet are the first thing you see.
• When nothing is ahead of your installed version, the list stays flat with no group heading — identical to a fully up-to-date installation.
• The QuickBox CLI and the Dashboard are separate components on independent version lines, so each shows its own pending release notes measured against its own installed version. A pending dashboard release and a pending CLI release are never mixed together.

Updating the dashboard

When a dashboard update is available, click Update on the Dashboard status card to open the Dashboard Update Modal. The modal provides:

1. Pre-update summary — Shows the version you are updating from and the version you are updating to
2. Live progress stream — Real-time streaming console showing each step of the update process as it runs
3. Automatic verification — After the update completes, the dashboard polls the health endpoint to confirm the new version is online before showing the completion state

After the update finishes, the modal confirms the result:

• Success — The new version is verified and running. Click Reload Dashboard to see the updated interface
• Reinstall — The same version was reinstalled (common on development or beta channels). No action required
• Needs attention — The version did not change as expected. Check the progress output for details

Updating QuickBox CLI

When a QuickBox update is available, click Update on the QuickBox status card. The update starts at once, without the list of operations, and triggers qb update quickbox on the server, which pulls the latest CLI version, updates the dashboard as part of the same pipeline, and reports the result.

A maintenance modal streams live output during the update. Because qb update quickbox includes a dashboard update step, the dashboard restarts mid-pipeline - the modal handles reconnection automatically and resumes streaming post-dashboard steps (configuration syncs, autocomplete, manpage, and similar finishing steps) before showing the final completion state.

Maintenance actions

The Maintenance > Actions card on the same page has two buttons, Fix version and Update QuickBox. Clicking either one opens the maintenance window with a Select a maintenance operation list. The list always offers the same four operations, so you can switch to any of them before you start:

Nothing runs until you press the action button at the bottom of the window. Choosing Update QuickBox in the window shows a warning that the update may take several minutes and could require service restarts.

Fix version

Fix version runs qb fix version, which downloads the current QuickBox release again and re-runs the update from the start. It replaces the qb, fix and manage programs and their fix, manage and update modules, then runs the full update in fix mode. On a dev or beta install it runs that channel’s updater instead. Use it when an update failed or will not start, when the install looks broken, or when the version shown is wrong. It does not reinstall your apps.

Fix rTorrent libcurl

Fix rTorrent libcurl runs qb fix libcurl to repair libcurl when it is below the version rTorrent needs. When no fixed build is published for your system yet, the job still finishes but the modal ends with an amber notice that nothing was changed, and if the repair is attempted and does not complete, the job is marked failed. See Fix libcurl for what the command does on each distro and how to fall back to rTorrent 0.15.7.

Secure PHP

Secure PHP runs qb fix php --security to bring the PHP of ruTorrent, phpMyAdmin and Nextcloud up to its security floor, the lowest build that carries the current PHP security fixes. Only the PHP version each app already runs on is updated, and an app that is already at its floor is left alone.

The PHP security block appears in the window only while Secure PHP is the selected operation, under the list of operations. It has one row per PHP app: the app, its PHP version, the installed build and the floor, with a green dot when the app is at its floor, a red dot when it is below, and a yellow dot when the installed version could not be read. The block also shows when the server last checked, and says so when PHP has not been checked yet or when no PHP app is installed.

When no fixed build is published for your system yet, the job still finishes but the modal ends with an amber notice that nothing was changed. If the installed PHP version cannot be read, or the update is attempted and does not complete, the job is marked failed and the modal says which. See Fix PHP for the exit codes and what the command does.

The status block reads the last recorded check, which the update check and every update refresh. The sidebar status dot is a second way in, for administrators only, and it shows on desktop-width screens only. It sits at the bottom of the sidebar’s icon rail, and it is green when all is well, amber when an update is waiting or a PHP app is below its security floor, and red when server health is degraded or the status cannot be read (red wins over amber). Open its popover and, only while a PHP app is below its floor, it offers a PHP below its security floor button that opens the maintenance window with Secure PHP already selected. When no PHP app is below its floor the button is not shown. The warning is refreshed when the job finishes. On smaller screens there is no status dot, so reach Secure PHP from System > Changelog as described above.

CLI equivalent

Best practices

FAQ

Related pages