I installed nzbdrone which works nicely with SABnzbd for about a week, and then it can no longer connect. I would restart, and it would work again. Another week goes by, same issue with not being able to connect, and now nothing seems to work. Not a restart, not a shutdown.
I read through a few posts that said SABnzbd can not be on 127.0.0.1 for host, but that’s the only way SABnzbd seems to work with my set up. Other programs i.e., CouchPotato seems to connect just fine.
I am on Windows 7 with log attached below. Any help would be much appreciated.
NzbDrone.Core.Download.Clients.DownloadClientException: Unable to connect to SABnzbd, please check your settings —> System.Net.WebException: Unable to connect to the remote server —> System.Net.Sockets.SocketException: An attempt was made to access a socket in a way forbidden by its access permissions 127.0.0.1:8080
at System.Net.Sockets.Socket.DoConnect(EndPoint endPointSnapshot, SocketAddress socketAddress)
at System.Net.ServicePoint.ConnectSocketInternal(Boolean connectFailure, Socket s4, Socket s6, Socket& socket, IPAddress& address, ConnectSocketState state, IAsyncResult asyncResult, Exception& exception)
— End of inner exception stack trace —
at System.Net.HttpWebRequest.GetResponse()
at RestSharp.Http.GetRawResponse(HttpWebRequest request)
at RestSharp.Http.GetResponse(HttpWebRequest request)
— End of inner exception stack trace —
at NzbDrone.Core.Download.Clients.Sabnzbd.SabnzbdProxy.CheckForError(IRestResponse response) in m:\BuildAgent\work\328d72309b633a8\src\NzbDrone.Core\Download\Clients\Sabnzbd\SabnzbdProxy.cs:line 149
at NzbDrone.Core.Download.Clients.Sabnzbd.SabnzbdProxy.ProcessRequest(IRestRequest restRequest, String action, SabnzbdSettings settings) in m:\BuildAgent\work\328d72309b633a8\src\NzbDrone.Core\Download\Clients\Sabnzbd\SabnzbdProxy.cs:line 69
at NzbDrone.Core.Download.Clients.Sabnzbd.SabnzbdProxy.GetHistory(Int32 start, Int32 limit, SabnzbdSettings settings) in m:\BuildAgent\work\328d72309b633a8\src\NzbDrone.Core\Download\Clients\Sabnzbd\SabnzbdProxy.cs:line 111
at NzbDrone.Core.Download.Clients.Sabnzbd.Sabnzbd.GetHistory() in m:\BuildAgent\work\328d72309b633a8\src\NzbDrone.Core\Download\Clients\Sabnzbd\Sabnzbd.cs:line 111
Which version of Sonarr (drone)?
Which version of SAB?
Are SAB and Sonarr on the same Windows 7 system?
In SAB’s settings, on the general, what do you have “SABnzbd Host” set to?
Are you able to open up a browser and connect to http://127.0.0.1:8080 on the machine running Sonarr? What about internet explorer?
Do you have a firewall or anti-virus running on this machine? If yes, which one(s)?
Have you tried configuring sab to listen on 0.0.0.0 ? That is the preferred way as I understood. It will listen on all interfaces.
I am on version 2.0.0.2169 of drone
SAB is 0.7.18
SAB and Sonarr are on the same Windows 7 system.
I believe I could open up the browser and connect previously. However, I also tried to change the setting on SAB to listen on 0.0.0.0 and now it started asking for a username and password. I did not set one, but now I also can not get back into SAB. This seems to have happened before as well and I reinstalled SAB entirely after deleting the .ini files.
I use zonealarm for firewall and avg for antivirus.
I don’t know if that helps. The odd thing is that everything seems to work for about a week before it fails. I eventually get to this step where I reinstall everything, which is a hassle.
I don’t know why I’m also being asked for a username and password on SAB when I have set none in both settings and the .ini file, but I suppose this is a question for a different support forum.
Thanks for helping.
Once you get SAB working again you should ensure that Sonarr and its data files are not being monitored by zonealarm or AVG, and the same for SABnzbd as it looks like one of the two is blocking communications, why it works for a week before failing doesn’t make any sense.
ROTFL! Being a SysAdmin, i would totally agree with you but i can tell you this used to happen to me with SAB. It would work fine for a while then i’d start seeing the connect errors. This was on a machine with no software firewall! I did some extensive troubleshooting for quite some time before i concluded it was possessed by a demon.
I switched to NZBGet and i was blown away at how much better it is IMHO.
Anyway, the problem could be sidestepped for people experiencing this simply by having a way of increasing the connection timeout on clients sending stuff to SAB.
-Pr.