QuickBox Pro v2.0.6

Originally published at: https://quickbox.io/changelogs/quickbox-pro-v2-0-6/

This version has been released on Thursday, August 1, 2019.

This version is considered a patch/maintenance release. Though it is labeled a maintenance release, there are lot of exciting additions and adjustments that have been made! For starters, after supporting php7.3 in Debian 10 installs, we have tested across the board and are happy to now support php7.3 on all our supported OS/Distro. No worries on how to upgrade, our updater will handle all of this for you! Additionally we have added in a couple of new features and an application, which application you ask? Why, TheLounge of course! It’s been requested for a long while and we’re happy to now have it included in the lineup. New features include the ability to block public trackers on the fly! That’s right, you can now allow or deny public trackers by running qb tracker [enable/disable] public. This command will stage the necessary edits to your hosts configuration to do the blocking and/or unblocking.

Of course, there are a lot of additional fixes and adjustments that have gone into this update. Some of which revolved around applications updating their required dependencies and/or certain dependencies within php7.2/7.3 have been deprecated. As per the usual, check out the changelog below to see more!

A Quick Note On apt update/upgrades

It has come to our attention that a lot of users tend to think that doing an apt -y update && apt -y upgrade on their servers will break QuickBox functionality; it’s quite the opposite! To ensure that your QuickBox Pro updates run as smooth as possible, we encourage everyone to stay on top of their system updates. This ensures that your system stay secure, updated, and updates are successfully fulfilled. So don’t hesitate to ever run those apt upgrades on your server… QuickBox craves a nice and tidy updated system!

Release Notice!

We have rolled the update out for all lifetime holders at the moment. This is to ensure that the qbUpdater runs properly and addresses all features and upgrades we have posted within this release (hint: php7.3, better opCache settings, and more!) go out as smoothly as possible. We have additionally tested the update from versions v1.6.4 to v2.0.6. These are now rolling out with great success!

With that said, the official day for release is Thursday, August 1st, 2019. We appreciate everyone’s patience on this matter as we do only want the best and cleanest update possible for all of our amazing members.

qb tracker [enable/disable] public
TheLounge added to package lineup
PHP updated to php7.3 [All supported Distro]
Activate emby updater qb update emby USERNAME
Added emby to update autocomplete
Added explanation notice in regards to required fields
Application builds updated to support php7.3
Generalize python versioning on Couchpotato/Medusa/pyLoad services
Updated output message on vpn
Sonarr: Updated gpg key
quota check from database on rutorrent diskspace plugin
pyload build dependencies have changed (updated)
Set light-theme for discord plugin on defaulted theme
Username sanitization on installer now sets username to all lowercase
Ensure grafana services are stopped and disabled on swap/remove
Aesthetic bug on dashboard v1 bw graph on mobile
Ensure proper permissions are set on rutorrent update
Add _task plugin fix for rutorrent on update
Swapping dashboard v1 <-> v2
Dynamic OpCache settings on update

This update seems to have broken something. After updating through the dashboard, I’m now getting a 502 bad gateway error when trying to load the page, rutorrent fails to connect as well. SSH still works however. How do I fix this?

Hi there

sudo su -
qb fix dpkg
qb fix version

and give a heads up on how things are then :slight_smile:


Looks like that fixed it, thank you for the quick response. Was I supposed to run those commands too when updating, or did something else break?

It’s not a matter of breaking, rather, in this update we upgraded all instances from php7.2 to php7.3. So more than likely what happened was you had either a dpkg lock from a load of apt updates needing to be updated first, or some dependencies were missed when upgrading from 7.2 to 7.3.

Glad you got that all sorted out and thank you for confirming! :heart:

Oh ok. I’ll remember this for any future problems then. Thanks again!

Glad you got it sorted :slight_smile:

This topic was automatically closed 3 days after the last reply. New replies are no longer allowed.