- Posted by JMSolo
- On November 2, 2018
ABOUT THIS RELEASE
Coming off of the massive core rewrite that was
v0.6.5 , we are now closer to total stability in terms of the applications handled. This update addresses some remaining issues left-over. QuickBox Staff would like to give a big thank you to all the reports coming in that are helping us address this in such a fast turn around.
So let’s discuss a couple of these changes.
changed app_log key length to 500 to avoid conflicts in certain environments
The updater, for many users (but not all), was apparently not building the System Response table properly due to the primary key value on the table being too long. Certain systems were reporting errors as they wanted no more than 756 bits on the primary key. In short, stuff was just too long and it didn’t get built.
addressed Tautulli build
This was a result of a bad call on the application install directory. We’ve wrapped things in pretty quotes to get this fixed. It now properly installs without the dreaded “Failed to build Tautulli” message on the System Response.
addressed letsencrypt package to avoid conflict with system command
This issue occurred from a simple clash between the name of our application for install, and the actual name of
letsencrypt, the actual let’s encrypt command. We have avoided future occurrences by renaming our package
addressed nginx reverse in ombi
There was a bad reverse wherein on install, the
$scheme value wasn’t properly escaped
\$scheme on import of the config. We’ve added the proper characters where the characters need to be. Tada, a working Ombi reverse.
addressed dpkg errors when attempting to reinstall Web Console
When installing Web Console, there would be an issue where it would cause a dependency lock on the system. This was a result of the directory already containing files, thus the symlink would fail… and fail it did. We’ve corrected this by ensuring the directory is empty of unnecessary files.
addressed SABnzbd build
Oh the joys of SABnzbd! We have upgraded our SABnzdb package to now utilize SABnzbdplus. We had some issues configuring the systemd file as the values are a bit different for SABnzbdplus. No longer using the
--daemon, we are now simply running it as a background process with the magic of ampersand (
addressed an issue where users created were not being given proper ssh/ftp access
uuuuhhhh, JMSolo says what now!? Yup, can we just pretend like this never happened guys! Guys? ….. guys?
addressed x2Go build
There was an issue with the x2Go installer where it was expecting a start file for starting services. This is something x2Go does not require on the build. We have removed this need for a successful build.