![]() ![]() I turned off the proxy in radarr/sonarr and when testing it appears they are routing all traffic through the VPN (checked external IP from radarr/sonarr's shell and inspected firewall traffic when performing searches).I was going to update General > Proxy in radarr/sonarr to use localhost, but. Updated radarr/sonarr deluge download client settings to use localhost (as noted in A24 Notes section, # 1) Updated swag/nginx reverse proxy configs for radarr/sonarr subdomains to point to binhex-delugevpn container I think I added it when trying to resolve the issue last time. I also removed the 172.18.0.0/16 proxynet subnet specified in the LAN_NETWORK variable, this isn't necessary.specified those ports in the VPN_INPUT_PORTS variable added in # 2.added port configurations in binhex-delugevpn config/template for radarr/sonarr ports.Is ADDITIONAL_PORTS now deprecated? If so, should any ports previously specified there be specified in VPN_INPUT_PORTS?.Is there a way to pull down updated templates within unRaid, rather than checking changes to delugevpn.xml in github and aligning changes manually via unRaid's GUI? I suppose pulling down an updated template would overwrite the entire xml file, wiping my setup.added VPN_INPUT_PORTS and VPN_OUTPUT_PORTS variables to my binhex-delugevpn config/template manually (via GUI).This leaves me open to easily revert the changes, if desired someday. I didn't want to remove the port configs so I used Advanced View > Edit: cleared the port's Default Value, changed Required to No and then cleared the port specified in the config.updated radarr/sonarr container network configs as outlined in A24 (adding -net=container:binhex-delugevpn to Extra Parameters, changing Network Type to None and unspecifying port configurations).Feeling like this issue can be closed out now (but please :) answer my 3 questions). I outlined the changes I made below for reference. Following A24 in the VPN FAQ resolved it and binhex-delugevpn:latest is working as expected (radarr/sonarr can connect to deluge download client). Nothing has changed besides this docker and I can roll it back and it is fine.Ĭonfirming this was related to #272 for me. End of inner exception stack trace -Īt .ManagedHttpDispatcher.GetResponse ( request, cookies) in C:\BuildAgent\work\5d7581516c0ee5b3\src\NzbDrone.Common\Http\Dispatchers\ManagedHttpDispatcher.cs:113Īt .FallbackHttpDispatcher.GetResponse ( request, cookies) in C:\BuildAgent\work\5d7581516c0ee5b3\src\NzbDrone.Common\Http\Dispatchers\FallbackHttpDispatcher.cs:53Īt .ExecuteRequest ( request, cookieContainer) in C:\BuildAgent\work\5d7581516c0ee5b3\src\NzbDrone.Common\Http\HttpClient.cs:121Īt .Execute ( request) in C:\BuildAgent\work\5d7581516c0ee5b3\src\NzbDrone.Common\Http\HttpClient.cs:57Īt. ( requestBuilder, .Deluge.DelugeSettings settings, System.Boolean reauthenticate) in C:\BuildAgent\work\5d7581516c0ee5b3\src\NzbDrone.Core\Download\Clients\Deluge\DelugeProxy.cs:290Īt. (.Deluge.DelugeSettings settings) in C:\BuildAgent\work\5d7581516c0ee5b3\src\NzbDrone.Core\Download\Clients\Deluge\DelugeProxy.cs:203Īt. (.Deluge.DelugeSettings settings, System.String method, System.Object arguments) in C:\BuildAgent\work\5d7581516c0ee5b3\src\NzbDrone.Core\Download\Clients\Deluge\DelugeProxy.cs:210Īt. (System.String label, .Deluge.DelugeSettings settings) in C:\BuildAgent\work\5d7581516c0ee5b3\src\NzbDrone.Core\Download\Clients\Deluge\DelugeProxy.cs:96Īt. () in C:\BuildAgent\work\5d7581516c0ee5b3\src\NzbDrone.Core\Download\Clients\Deluge\Deluge.cs:96Īt .DownloadMonitoringService.ProcessClientDownloads ( downloadClient) in C:\BuildAgent\work\5d7581516c0ee5b3\src\NzbDrone.Core\Download\TrackedDownloads\DownloadMonitoringService.cs:89 : The operation has timed out.: ' -> : The operation has timed out.Īt ( 1 workerTask, System.Int32 timeout, System.Action abort, System.Func1 aborted, cts) in :0Īt () in :0Īt .ManagedHttpDispatcher.GetResponse ( request, cookies) in C:\BuildAgent\work\5d7581516c0ee5b3\src\NzbDrone.Common\Http\Dispatchers\ManagedHttpDispatcher.cs:82 The operation has timed out.: ' Looking at the log, this is what I am finding in the logs: linuxserver/sonarr and linuxserver/radarr are not able to connect after updating this docker to the latest. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |