Not sure how this happened, but glad it is. I copied/pasted the 10.x.x.x address into the SAB config in Sonarr and Radarr, and lo and behold, they were able to connect and started to work. I had this set as the 192.168.1.x address of my server in Radarr and Sonarr (and I'm sure this is how it has always been!). To resolve, I noticed that when I looked at "Status and Interface Options" in the SABnzbd UI, the local IPV4 address was a 10.8.x.x address. Yesterday I lost all my dockers and had to restore from a backup, so somehow that might be part of what caused the issue - not sure. They've been working for over a year, without issue. This morning the issue I was having was that Sonarr and Radarr couldn't communicate with SABnzbd.
That's what I did with SABnzbd, Radarr and Sonarr. I normally follow Space Invader One's videos for setting dockers up rather than reinventing the wheel. I figured out my issue, but its strange that it popped up today, and the resolution wasn't what I expected. End of inner exception stack trace -Īt. ( requestBuilder, .Sabnzbd.SabnzbdSettings settings) in C:\projects\radarr-usby1\src\NzbDrone.Core\Download\Clients\Sabnzbd\SabnzbdProxy.cs:188Īt. (.Sabnzbd.SabnzbdSettings settings) in C:\projects\radarr-usby1\src\NzbDrone.Core\Download\Clients\Sabnzbd\SabnzbdProxy.cs:80Īt. () in C:\projects\radarr-usby1\src\NzbDrone.Core\Download\Clients\Sabnzbd\Sabnzbd.cs:359 DownloadClientException: Unable to connect to SABnzbd, please check your settings -> : HTTP request failed: at Īt .Execute ( request) in C:\projects\radarr-usby1\src\NzbDrone.Common\Http\HttpClient.cs:100Īt. ( requestBuilder, .Sabnzbd.SabnzbdSettings settings) in C:\projects\radarr-usby1\src\NzbDrone.Core\Download\Clients\Sabnzbd\SabnzbdProxy.cs:184 Sabnzbd: Unable to connect to SABnzbd, please check your settings
0 kommentar(er)
