You can now run the update from your dashboards and Sonarr will show as an install-able package. The version bump will follow here within the next hour along with an announcement and changelog adjustments.
1 Like
So sonarr is installable from the dashboard, but I might be missing the obvious as to how to get to the sonarr interface itself. Should there be a link from the dashboard, or documentation on it that I overlooked?
edit - oh I see that sonarr is installed and set to ON in the service controller, but the service itself still shows as disabled.
just wait for it as it will show up in the menu left once the service is running.
Might try Reload Services after popping the service controllers…
It popped on and showed after a few secs and a browser reload 
1 Like
Are you running Debian by chance?
Yes I am running debian 8
Then what you my friend have is a case of the “Deebs” it’s nothing epic and not contagious… thanks to @globber I was able to narrow this issue down… and it turns out it is Debian doesn’t like the official mono repository.
So, here is what you can do…
- The easy way
- Update QuickBox from your dashboard after you uninstall Sonarr. Then reinstall Sonarr and the service should come online after a minute (the cron needs to pick it up to initiate the service first… this might be your case right now)
- The more complicated way
- Follow the instructions below:
rm /etc/apt/sources.list.d/mono-xamarin.list
sudo apt-key adv --keyserver hkp://keyserver.ubuntu.com:80 --recv-keys 3FA7E0328081BFF6A14DA29AA6A19B38D3D831EF
echo "deb http://debian.meebey.net/pkg-mono ./" | sudo tee /etc/apt/sources.list.d/mono-meeby.list
sudo apt-key adv --keyserver keyserver.ubuntu.com --recv-keys FDA5DFFC
echo "deb https://apt.sonarr.tv/ master main" | sudo tee -a /etc/apt/sources.list.d/sonarr.list
sudo apt-get -y update
sudo apt-get install -y mono-devel
sudo apt-get install -y nzbdrone
sudo rm /etc/apt/sources.list.d/sonarr.list
Ahaa you made me immune to this eh 
Just joking…and thanks for the explanation why mine is working and his isn´t!
I think there may be a mismatch in mono-devel versions. I had to adjust your steps a bit, and it still doesn’t look like it’s starting up.
I had to -
- update quickbox from dashboard
- uninstalled/reinstall sonarr from dashboard
- apt-get install mono-devel from ssh
- THEN add the sonarr.tv repo and install nzbdrone.
But now if I go to do an apt-get upgrade it’s throwing dependency issues re: mono-devel and holding back packages.
Did you remove the old source for the mono-xamarin.list?
Which I guess… would be sort of important to include in the installer… in the event it exists on the system. I’ll do an if [ this.list] find and rm function here in a few.
Yeah I did.
After my last reply I ran apt-get install mono-devel again to see if it would kick in those packages being held back, it installed stuff from both repo’s. I then was able to run apt-get upgrade without it giving me dependency errors.
Perhaps there should have been and apt-get purge in there somewhere in relation to clearing out the old mono-devel before replacing it?
I’ve restarted the service and am now waiting to see if it shows as enabled/active and I get the dashboard entry.
edit - woo, the sonarr service is green and enabled now at least. refreshed the page to get the dashboard menu entry for it.
1 Like
Your perhaps is spot on kind sir. I will throw in an apt purge along with an autoremove and clean. Updating this in the next 15 minutes.
1 Like
So now that i’ve got sonarr up and running, any tips on getting it to pass torrents along to rtorrent?
What is the typical settings page for rtorrent to look like? I’ve tried the server IP, with /RPC and port 80 or 8080 and provided the username and password for the account, but neither works. Port 8080 gives connection refused, and port 80 “Unknown exception: Error writing headers” which googling leads me to believe is mono telling me it is having issues authenticating?
See if this solution works for you:
Hmm, that seems to be a step closer as now I get an unauthorized response when testing. I’ve confirmed the user/pass is correct though.
I think I may have gotten it figured out through a bit of trial and error.
The Url path it’s looking for is (in my example using httprpc as the handler) ; /rutorrent/plugins/httprpc/action.php
host : localhost
port : 80
SSL : off
Once I got SSL turned off and the path above figured out, the client tested fine and could be added.
One additional issue I’m running in to with the Sonarr implementation on quickbox;
When I try to add an RSS source that uses SSL, the log shows an error along the lines of -
And googling this seems to indicate that Mono is failing handling SSL and should be falling back to curl. I’ve checked and libcurl is present. Could there perhaps be an issue with the version of libcurl in use or required by quickbox that differs from what Sonarr is trying to fall back to?
This may very well be an issue with the source that mono is installed from on Debian - meeby source and not the recommended by sonarr, mono-project. I will dig into their requirements and see if that is the case, although, it really shouldn’t be.
1 Like
Just to revisit the Sonarr installation on Debian thing from yesterday ;
FYI, On a fresh install it is now using the meebey.net repo, but is not installing mono-devel.
Additionally the sonarr.tv repo was not added, so nzbdrone (sonarr) was not actually installed when the task was initiated from the dash.
1 Like
I’ll look into this now that the dust has settled on some of the updates today.