I receive the following error when I attempt to update from 2.3.7 via the dashboard:
Pulling QuickBox Ecosystem …
fatal: could not read Username for ‘https://github.com’: No such device or address
quickbox_setup :: fatal: could not read Username for ‘https://github.com’: No such device or address
quickbox_rutorrent :: fatal: could not read Username for ‘https://github.com’: No such device or address
quickbox_rutorrent-plugins :: fatal: could not read Username for ‘https://github.com’: No such device or address
quickbox_packages :: fatal: could not read Username for ‘https://github.com’: No such device or address
quickbox_dashboard :: fatal: could not read Username for ‘https://github.com’: No such device or address
Checking for quotas and adding lock file if necessary …
Does anyone have any idea how I can fix this please?
Updating from versions previous to v2.4 is a massive overhaul and takes another command that is more of an easter-egg. It’s our legacy upgrade. part of the issue you will have is due to the fact that we use our own git now rather than relying on third-party solutions.
Run the commands below as root. You can become root from your sudo account easily by typing sudo su
Do the following to get started with your upgrade:
cd
wget -O upgradeQuickBox https://lab.quickbox.io/QuickBox/quickbox_packages/raw/master/system/upgradeQuickBox
bash upgradeQuickBox
The above will activate the new EcoSystem on your server, it basically sets up a local repository that makes updating QuickBox in the future much easier and also allows a fallback in the offchance that anything gets set improperly.
Next, you will need to run a quick update of your system by typing the following:
cd
bash QuickBox/packages/system/updateQuickBox
Next you will need to adjust your directories structure to match the new structure for QuickBox’s apache configuration. This structure is referrencing the /home/USERNAME/torrents as we now separate deluge from rtorrent for easier organization between the two.
This is done for you by typing adjust-user-directory. You will next need to manually select ‘Save to…’ on your torrents in ruTorrent to save them to the new /home/Username/torrents/rtorrent directory.
###Pro Tip
Pressing Ctrl+A in ruTorrent will select all torrents simaltaneaously.
For more about this, check out this post:
With these steps done, you can do one final command to ensure that you are completely caught up and running a stable v2.4.7 of QuickBox. That command is box upgrade. Just like that, you’re done. Not so hard!
Honestly @RaymondSchnyder, if you followed the steps above, there is no way you would still be on v2.3.7. Please ensure that you have followed the steps outlined exactly.
No, you do not. I would need to know more information however.
Is your issue exactly the same as the one stated by @RaymondSchnyder?
What version of QuickBox are you on?
Have you followed the above method to upgrade if under 2.4
I can’t provide any clarity if you provide little to no information. I can say that we no longer use GitHub as we self-host our own gitlab for QuickBox now.
Correct, more than likely it was just memcache and/or your browser caching. If it happens to where it looks like updates versioning doesn’t post… just type service apache2 restart and be sure to clear browser cache. System reboots aren’t normally needed.
I just want to point I am having the same problem of being asked for github username (ofc did server restart and downloaded new upgrade script too).
(Running QB 2.3.7 on Ubuntu 16.04 x64)
Thanks.
Edit: just wanted to note that following this => QuickBox v2.4 Released!
After copying new repo files the command “updateQuickBox” worked, and I was able to upgrade to 2.4.7.
Only remaining issue is the http/apache server is denying me access to dashboard now (everything else, plex, ssh, ftp… etc) is working.
