: Unable to connect to indexer, check the log for more detailsĪt 1.ProviderControllerBase`3.VerifyValidationResult(ValidationResult validationResult, Boolean includeWarnings) in D:\a\1\s\src\1\ProviderControllerBase.cs:line 209Īt 1.ProviderControllerBase`3.Test(TProviderDefinition definition, Boolean includeWarnings) in D:\a\1\s\src\1\ProviderControllerBase.cs:line 195Īt 1.ProviderControllerBase`3.Test(TProviderResource providerResource) in D:\a\1\s\src\1\ProviderControllerBase.cs:line 144Īt .(IActionResultTypeMapper mapper, ObjectMethodExecutor executor, Object controller, Object arguments)Īt .ControllerActionInvoker.InvokeActionMethodAsync()Īt .ControllerActionInvoker.Next(State& next, Scope& scope, Object& state, Boolean& isCompleted)Īt .ControllerActionInvoker.InvokeNextActionFilterAsync() FluentValidation.ValidationException: Validation failed: Have provided the log below, but happy to provide any other logs / settings - any help would be amazing! But same as before it wont let me add any indexers. Thought Prowlarr might be a better fit (already using the other 'arrs). The tests on links stopped working in Jackett ( spit out the following Connection reset by peer: The SSL connection could not be established, see inner exception.) But i was never able to get to the bottom of why it wasn't working. Hope someone can help - having trouble getting Prowlarr (and Jackett previously) to work.
UNRAID SONARR DOCKER UPDATE UPDATE
But, maybe it's been compiled for newer architecture than I have? Any you ever figure this out? After the last update I have my Prowlarr and Radarr containers doing this. 18:42:56,722 DEBG 'start-script' stderr output:įailed to create CoreCLR, HRESULT: 0x80004005Įdit: I'm going to assume this is a permission problem.
18:42:56,687 INFO reaped unknown pid 8 (exit status 0)
18:42:56,684 INFO spawned: 'shutdown-script' with pid 58 18:42:55,682 INFO supervisord started with pid 7 18:42:55,680 INFO Set uid to user 0 succeeded 18:42:55,679 INFO Included extra file "/etc/supervisor/conf.d/nf" during parsing I can't seem to get this running and I don't know what the container might be missing to have this error. With my setup, are Sonarr and Radarr and connecting to Prowlarr locally, no internet? How do I confirm if Prowlarr or Sonarr is using proxy when connecting to Indexers?Ĥ.
UNRAID SONARR DOCKER UPDATE DOWNLOAD
If I added SABnzbdVPN as download client in Prowlarr, Can I remove SABnzbdVPN in Sonarr and Radarr like I did with Indexers?ģ. Read binhex FAQ about this, but he mentioned setting in Jackett, just wanted to confirm same with ProwlarrĢ. Is it right setup to just enable proxy in Prowlarr since it's the one connecting to indexers? And leave Sonarr and Radarr proxy off. I watched Spaceinvader one's video tutorial in setting proxy in Sonarr & Radarr, but he wasn't using another app managing indexersġ. Enabled Proxy to SABnzbdVPN Privoxy, added my localhost IP to Ignored address. Once I did this, Sonarr/Radarr could now connect to both SabNZB & my indexers.Everything seems to be working fine but just wanted to confirm few things. For this I had to go into the SabNZB download client settings within Radarr, and change the 'Host' from my local IP of the server, to the word 'localhost'. However, these dockers could not connect to SabNZB anymore - only the indexers were testing OK, not the download clients. This allowed me to see the Sonarr/Radarr webguis.Make sure that your ports for Sonarr/Radarr/Lidarr are added into that field, separated by commas. Add the Radarr/Sonarr docker port numbers that you're running through Binhex-DelugeVPN, into the ADDITIONAL_PORTS field in the Binhex-DelugeVPN docker container settings.With the recent updates my docker web guis stopped working, so as others have mentioned I had to do this: This might help some people who are running docker containers such as Sonarr & Radarr through a VPN container like Binhex-DelugeVPN (using the -net=container:binhex-delugevpn method) and are getting connection issues.
0 kommentar(er)
