OtherSide Posted March 24, 2022 Share Posted March 24, 2022 (edited) Thank you binhex for your apps! Everything seems to be working fine but just wanted to confirm few things. My Setup: Prowlarr : Added Indexers in Full Sync. Added Sonarr & Radarr. Enabled Proxy to SABnzbdVPN Privoxy, added my localhost IP to Ignored address. Sonarr: SABnzbdVPN as download client. Indexer (Prowlarr) Radarr: SABnzbdVPN as download client. Indexer (Prowlarr) SABnzbdVPN : Wireguard & Privoxy Enabled - I watched Spaceinvader one's video tutorial in setting proxy in Sonarr & Radarr, but he wasn't using another app managing indexers Questions: 1. 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. - Read binhex FAQ about this , but he mentioned setting in Jackett, just wanted to confirm same with Prowlarr 2. If I added SABnzbdVPN as download client in Prowlarr, Can I remove SABnzbdVPN in Sonarr and Radarr like I did with Indexers? 3. How do I confirm if Prowlarr or Sonarr is using proxy when connecting to Indexers? 4. With my setup, are Sonarr and Radarr and connecting to Prowlarr locally, no internet? Thanks! Edited March 24, 2022 by OtherSide 1 Quote Link to comment
brainbudt Posted April 12, 2022 Share Posted April 12, 2022 is it possible to add a VPN version like your other torrent dockers? Quote Link to comment
H2O_King89 Posted May 2, 2022 Share Posted May 2, 2022 (edited) After last night's update I woke up to this. Tried force updated and can't get it fix. Is there a way to roll back? Looks like a fix has been push out by the devs. Binhex needs to update his image? Thank you!! https://www.reddit.com/r/prowlarr/comments/uge52l/error_failed_to_load_indexers_from_api/?utm_medium=android_app&utm_source=share Edited May 2, 2022 by H2O_King89 1 Quote Link to comment
wgstarks Posted May 2, 2022 Share Posted May 2, 2022 15 minutes ago, H2O_King89 said: Is there a way to roll back? Enter this in the repository field for the docker- binhex/arch-prowlarr:0.2.0.1678-1-01 1 Quote Link to comment
H2O_King89 Posted May 2, 2022 Share Posted May 2, 2022 Enter this in the repository field for the docker-binhex/arch-prowlarr:0.2.0.1678-1-01 Awesome back up and running. Thank you! Sent from my SM-S908U using Tapatalk Quote Link to comment
wgstarks Posted May 2, 2022 Share Posted May 2, 2022 (edited) 8 minutes ago, H2O_King89 said: Awesome back up and running. Thank you! Sent from my SM-S908U using Tapatalk You can do that with most of the dockers on unRAID. Just go to the dockerhub page and grab the tag for the version you want. Enter the tag number after the name in the repository field separated by a colon. Edited May 2, 2022 by wgstarks Not with Unifi Quote Link to comment
airy52 Posted May 17, 2022 Share Posted May 17, 2022 @binhexNeed you to update container for this fix, BTN broken because non-https URL: https://github.com/Prowlarr/Prowlarr/commit/2820ef9375e632388c891832600ae7dca1123f4d Quote Link to comment
tjb_altf4 Posted May 17, 2022 Share Posted May 17, 2022 1 hour ago, airy52 said: @binhexNeed you to update container for this fix, BTN broken because non-https URL: https://github.com/Prowlarr/Prowlarr/commit/2820ef9375e632388c891832600ae7dca1123f4d Binhex's release from 2 weeks ago has that fix (Prowlarr release 0.3.0.1730) Quote Link to comment
Royalflash5220 Posted June 25, 2022 Share Posted June 25, 2022 (edited) Is Prowlarr still getting updates or is your version being deprecated? Last version is 2 months old and prowlarr has received a few updates in the last 2 months. Love your docker containers Edited June 25, 2022 by Royalflash5220 Quote Link to comment
wgstarks Posted June 25, 2022 Share Posted June 25, 2022 32 minutes ago, Royalflash5220 said: Is Prowlarr still getting updates or is your version being deprecated? Last version is 2 months old and prowlarr has received a few updates in the last 2 months. Love your docker containers I'm seeing an update on GitHub (20 hours old) but its not on dockerhub yet. Quote Link to comment
wgstarks Posted June 25, 2022 Share Posted June 25, 2022 Looks like the most recent version in the arch repo is 0.3.0.1730-1 though. Quote Link to comment
Royalflash5220 Posted June 25, 2022 Share Posted June 25, 2022 23 minutes ago, wgstarks said: Looks like the most recent version in the arch repo is 0.3.0.1730-1 though. Im sorry, I thought I saw that the version in my docker container was v0.2.0.1678 from April 10th, but it was 0.3.0.1730, the latest one excluding the one from yesterday. Thank you for correcting me! Again sorry, probably looked like a dick expecting an update after 20 hours Quote Link to comment
wgstarks Posted June 25, 2022 Share Posted June 25, 2022 Not really. Pretty sure it’s all automated though. Once the arch build is released the docker image will grab it. 1 2 Quote Link to comment
nicklesz Posted July 2, 2022 Share Posted July 2, 2022 I am also getting the error "Value cannot be null. (Parameter 'returnType')" on the latest release. I tried rolling back to several different previous versions with no luck. I also see this error when checking the logs: 2022-07-02 10:29:38,932 DEBG 'start-script' stdout output: [Fatal] ProwlarrErrorPipeline: Request Failed. GET /api/v1/indexer What can I do to fix this? Thanks! Quote Link to comment
SRTG Posted July 31, 2022 Share Posted July 31, 2022 I have an issue connecting indexers to Prowlarr and am a bit stumped. Newby here with a one week old server out of my depth but I will try explain. I have prowlarr set up using flaresolverr as a proxy, which tests fine, but I get errors when testing any indexer connection. If I disable RSS then re-enable the indexers appear to work (green tick) but when I actually search in Prowlarr, the logs produce this and I go back to failure: Radarr also shows this: Frustratingly close to getting this working after much tinkering so appreciate a steer from anyone. Quote Link to comment
SRTG Posted August 1, 2022 Share Posted August 1, 2022 (edited) I managed to get around this by disabling flaresolverr and using deluge proxy instead. I can now add indexers which return searches in prowlarr. These also show up in radarr as linked indexers "(prowlarr)". The problem now is I have lost connection to Deluge in both apps with the same download client configuration settings as before. Is there an additional setting I need to add when using Deluge proxy ? Pulling my hair out at this stage! My proxy settings in prowlarr - http(s), local server address, port 8118, bypass proxy for local addresses ticked. Log states as follows: Edited August 1, 2022 by SRTG 1 Quote Link to comment
luisalrp Posted September 8, 2022 Share Posted September 8, 2022 (edited) I have the same problem as @SRTG. Since I routed the traffic through binhex-delugevpn, I cant connect anymore to binhex-delugevpn. I selected the bypass local address option in the proxy settings. Any idea? Edited September 8, 2022 by luisalrp Quote Link to comment
SRTG Posted September 9, 2022 Share Posted September 9, 2022 (edited) @luisalrp My issue was incorrect server addresses and port mappings across the Arr apps. I just didn't have an understanding of what to use for these but since figuring it out all are working perfectly. The Prowlarr, Radarr and Sonarr proxy address should be your server address - as below My next issue was using host addresses instead of app addresses when linking prowlarr to other Arr apps. These should be http://app address:port map i.e. when on unraid docker screen port mappings are listed "app to host" left to right. Use the app address on the left hand side of this list not the host address on the right when linking apps. Use the same app address when linking deluge in Arr apps. The "Host" field should have the app address only, no http. Edited September 9, 2022 by SRTG Quote Link to comment
hendeeze Posted September 17, 2022 Share Posted September 17, 2022 I am having trouble linking prowlarr to a deluge instance on my seedbox. Using the same settings as my sonarr/radarr on my local device prowlarr (local) refuses to connect. I am getting "Failed to test connection: Not authenticated (code 1) errors in the log". Any ideas? Quote Link to comment
AGuyInTheWrongRoom Posted September 17, 2022 Share Posted September 17, 2022 Hi My binhex-prowlarr container keeps stopping for no apparent reason. The logs show this: 2022-09-12 03:00:11,095 WARN received SIGTERM indicating exit request 2022-09-12 03:00:11,095 DEBG killing start-script (pid 65) with signal SIGTERM 2022-09-12 03:00:11,095 INFO waiting for start-script to die 2022-09-12 03:00:11,230 DEBG 'start-script' stdout output: [Info] ConsoleApp: Exiting main. 2022-09-12 03:00:11,231 DEBG fd 8 closed, stopped monitoring <POutputDispatcher at 23285748612304 for <Subprocess at 23285748610336 with name start-script in state STOPPING> (stdout)> 2022-09-12 03:00:11,231 DEBG fd 10 closed, stopped monitoring <POutputDispatcher at 23285749057616 for <Subprocess at 23285748610336 with name start-script in state STOPPING> (stderr)> 2022-09-12 03:00:11,231 INFO stopped: start-script (exit status 143) 2022-09-12 03:00:11,231 DEBG received SIGCHLD indicating a child quit Does anybody have any idea what this could be? Thanks. Quote Link to comment
jakadia Posted December 31, 2022 Share Posted December 31, 2022 On 10/10/2021 at 5:52 PM, mathgeek97 said: I can't seem to get this running and I don't know what the container might be missing to have this error. Unraid 6.9.2 2021-10-10 18:42:55.103477 [info] Host is running unRAID 2021-10-10 18:42:55.132781 [info] System information Linux d803c532142d 5.10.28-Unraid #1 SMP Wed Apr 7 08:23:18 PDT 2021 x86_64 GNU/Linux 2021-10-10 18:42:55.170916 [info] OS_ARCH defined as 'x86-64' 2021-10-10 18:42:55.208211 [info] PUID defined as '99' 2021-10-10 18:42:55.250655 [info] PGID defined as '100' 2021-10-10 18:42:55.342888 [info] UMASK defined as '000' 2021-10-10 18:42:55.380514 [info] Permissions already set for '/config' 2021-10-10 18:42:55.418258 [info] Deleting files in /tmp (non recursive)... 2021-10-10 18:42:55.464281 [info] Starting Supervisor... 2021-10-10 18:42:55,679 INFO Included extra file "/etc/supervisor/conf.d/prowlarr.conf" during parsing 2021-10-10 18:42:55,680 INFO Set uid to user 0 succeeded 2021-10-10 18:42:55,682 INFO supervisord started with pid 7 2021-10-10 18:42:56,684 INFO spawned: 'shutdown-script' with pid 58 2021-10-10 18:42:56,687 INFO spawned: 'start-script' with pid 59 2021-10-10 18:42:56,687 INFO reaped unknown pid 8 (exit status 0) 2021-10-10 18:42:56,722 DEBG 'start-script' stderr output: Failed to create CoreCLR, HRESULT: 0x80004005 Thanks, mathgeek97 Edit: I'm going to assume this is a permission problem. But, maybe it's been compiled for newer architecture than I have? Any suggestions? @mathgeek97Did you ever figure this out? After the last update I have my Prowlarr and Radarr containers doing this. Quote Link to comment
binhex Posted January 1, 2023 Author Share Posted January 1, 2023 @mathgeek97Did you ever figure this out? After the last update I have my Prowlarr and Radarr containers doing this.Try updating to latest stable unraid, I think this is kernel relatedSent from my 22021211RG using Tapatalk Quote Link to comment
Furion Posted January 17, 2023 Share Posted January 17, 2023 Hope someone can help - having trouble getting Prowlarr (and Jackett previously) to work. 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. Thought Prowlarr might be a better fit (already using the other 'arrs). But same as before it wont let me add any indexers. Have provided the log below, but happy to provide any other logs / settings - any help would be amazing! I get the following in the log: [v1.0.1.2220] FluentValidation.ValidationException: Validation failed: -- : Unable to connect to indexer, check the log for more details at Prowlarr.Api.V1.ProviderControllerBase`3.VerifyValidationResult(ValidationResult validationResult, Boolean includeWarnings) in D:\a\1\s\src\Prowlarr.Api.V1\ProviderControllerBase.cs:line 209 at Prowlarr.Api.V1.ProviderControllerBase`3.Test(TProviderDefinition definition, Boolean includeWarnings) in D:\a\1\s\src\Prowlarr.Api.V1\ProviderControllerBase.cs:line 195 at Prowlarr.Api.V1.ProviderControllerBase`3.Test(TProviderResource providerResource) in D:\a\1\s\src\Prowlarr.Api.V1\ProviderControllerBase.cs:line 144 at Microsoft.AspNetCore.Mvc.Infrastructure.ActionMethodExecutor.SyncObjectResultExecutor.Execute(IActionResultTypeMapper mapper, ObjectMethodExecutor executor, Object controller, Object[] arguments) at Microsoft.AspNetCore.Mvc.Infrastructure.ControllerActionInvoker.InvokeActionMethodAsync() at Microsoft.AspNetCore.Mvc.Infrastructure.ControllerActionInvoker.Next(State& next, Scope& scope, Object& state, Boolean& isCompleted) at Microsoft.AspNetCore.Mvc.Infrastructure.ControllerActionInvoker.InvokeNextActionFilterAsync() --- End of stack trace from previous location --- at Microsoft.AspNetCore.Mvc.Infrastructure.ControllerActionInvoker.Rethrow(ActionExecutedContextSealed context) at Microsoft.AspNetCore.Mvc.Infrastructure.ControllerActionInvoker.Next(State& next, Scope& scope, Object& state, Boolean& isCompleted) at Microsoft.AspNetCore.Mvc.Infrastructure.ControllerActionInvoker.InvokeInnerFilterAsync() --- End of stack trace from previous location --- at Microsoft.AspNetCore.Mvc.Infrastructure.ResourceInvoker.<InvokeFilterPipelineAsync>g__Awaited|20_0(ResourceInvoker invoker, Task lastTask, State next, Scope scope, Object state, Boolean isCompleted) at Microsoft.AspNetCore.Mvc.Infrastructure.ResourceInvoker.<InvokeAsync>g__Awaited|17_0(ResourceInvoker invoker, Task task, IDisposable scope) at Microsoft.AspNetCore.Mvc.Infrastructure.ResourceInvoker.<InvokeAsync>g__Awaited|17_0(ResourceInvoker invoker, Task task, IDisposable scope) at Microsoft.AspNetCore.Routing.EndpointMiddleware.<Invoke>g__AwaitRequestTask|6_0(Endpoint endpoint, Task requestTask, ILogger logger) at Prowlarr.Http.Middleware.BufferingMiddleware.InvokeAsync(HttpContext context) in D:\a\1\s\src\Prowlarr.Http\Middleware\BufferingMiddleware.cs:line 28 at Prowlarr.Http.Middleware.IfModifiedMiddleware.InvokeAsync(HttpContext context) in D:\a\1\s\src\Prowlarr.Http\Middleware\IfModifiedMiddleware.cs:line 41 at Prowlarr.Http.Middleware.CacheHeaderMiddleware.InvokeAsync(HttpContext context) in D:\a\1\s\src\Prowlarr.Http\Middleware\CacheHeaderMiddleware.cs:line 33 at Prowlarr.Http.Middleware.UrlBaseMiddleware.InvokeAsync(HttpContext context) in D:\a\1\s\src\Prowlarr.Http\Middleware\UrlBaseMiddleware.cs:line 27 at Prowlarr.Http.Middleware.VersionMiddleware.InvokeAsync(HttpContext context) in D:\a\1\s\src\Prowlarr.Http\Middleware\VersionMiddleware.cs:line 28 at Microsoft.AspNetCore.ResponseCompression.ResponseCompressionMiddleware.InvokeCore(HttpContext context) at Microsoft.AspNetCore.Authorization.Policy.AuthorizationMiddlewareResultHandler.HandleAsync(RequestDelegate next, HttpContext context, AuthorizationPolicy policy, PolicyAuthorizationResult authorizeResult) at Microsoft.AspNetCore.Authorization.AuthorizationMiddleware.Invoke(HttpContext context) at Microsoft.AspNetCore.Authentication.AuthenticationMiddleware.Invoke(HttpContext context) at Microsoft.AspNetCore.Diagnostics.ExceptionHandlerMiddleware.<Invoke>g__Awaited|6_0(ExceptionHandlerMiddleware middleware, HttpContext context, Task task) Quote Link to comment
binhex Posted January 18, 2023 Author Share Posted January 18, 2023 13 hours ago, Furion said: Hope someone can help - having trouble getting Prowlarr (and Jackett previously) to work. 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. Thought Prowlarr might be a better fit (already using the other 'arrs). But same as before it wont let me add any indexers. Have provided the log below, but happy to provide any other logs / settings - any help would be amazing! I get the following in the log: [v1.0.1.2220] FluentValidation.ValidationException: Validation failed: -- : Unable to connect to indexer, check the log for more details at Prowlarr.Api.V1.ProviderControllerBase`3.VerifyValidationResult(ValidationResult validationResult, Boolean includeWarnings) in D:\a\1\s\src\Prowlarr.Api.V1\ProviderControllerBase.cs:line 209 at Prowlarr.Api.V1.ProviderControllerBase`3.Test(TProviderDefinition definition, Boolean includeWarnings) in D:\a\1\s\src\Prowlarr.Api.V1\ProviderControllerBase.cs:line 195 at Prowlarr.Api.V1.ProviderControllerBase`3.Test(TProviderResource providerResource) in D:\a\1\s\src\Prowlarr.Api.V1\ProviderControllerBase.cs:line 144 at Microsoft.AspNetCore.Mvc.Infrastructure.ActionMethodExecutor.SyncObjectResultExecutor.Execute(IActionResultTypeMapper mapper, ObjectMethodExecutor executor, Object controller, Object[] arguments) at Microsoft.AspNetCore.Mvc.Infrastructure.ControllerActionInvoker.InvokeActionMethodAsync() at Microsoft.AspNetCore.Mvc.Infrastructure.ControllerActionInvoker.Next(State& next, Scope& scope, Object& state, Boolean& isCompleted) at Microsoft.AspNetCore.Mvc.Infrastructure.ControllerActionInvoker.InvokeNextActionFilterAsync() --- End of stack trace from previous location --- at Microsoft.AspNetCore.Mvc.Infrastructure.ControllerActionInvoker.Rethrow(ActionExecutedContextSealed context) at Microsoft.AspNetCore.Mvc.Infrastructure.ControllerActionInvoker.Next(State& next, Scope& scope, Object& state, Boolean& isCompleted) at Microsoft.AspNetCore.Mvc.Infrastructure.ControllerActionInvoker.InvokeInnerFilterAsync() --- End of stack trace from previous location --- at Microsoft.AspNetCore.Mvc.Infrastructure.ResourceInvoker.<InvokeFilterPipelineAsync>g__Awaited|20_0(ResourceInvoker invoker, Task lastTask, State next, Scope scope, Object state, Boolean isCompleted) at Microsoft.AspNetCore.Mvc.Infrastructure.ResourceInvoker.<InvokeAsync>g__Awaited|17_0(ResourceInvoker invoker, Task task, IDisposable scope) at Microsoft.AspNetCore.Mvc.Infrastructure.ResourceInvoker.<InvokeAsync>g__Awaited|17_0(ResourceInvoker invoker, Task task, IDisposable scope) at Microsoft.AspNetCore.Routing.EndpointMiddleware.<Invoke>g__AwaitRequestTask|6_0(Endpoint endpoint, Task requestTask, ILogger logger) at Prowlarr.Http.Middleware.BufferingMiddleware.InvokeAsync(HttpContext context) in D:\a\1\s\src\Prowlarr.Http\Middleware\BufferingMiddleware.cs:line 28 at Prowlarr.Http.Middleware.IfModifiedMiddleware.InvokeAsync(HttpContext context) in D:\a\1\s\src\Prowlarr.Http\Middleware\IfModifiedMiddleware.cs:line 41 at Prowlarr.Http.Middleware.CacheHeaderMiddleware.InvokeAsync(HttpContext context) in D:\a\1\s\src\Prowlarr.Http\Middleware\CacheHeaderMiddleware.cs:line 33 at Prowlarr.Http.Middleware.UrlBaseMiddleware.InvokeAsync(HttpContext context) in D:\a\1\s\src\Prowlarr.Http\Middleware\UrlBaseMiddleware.cs:line 27 at Prowlarr.Http.Middleware.VersionMiddleware.InvokeAsync(HttpContext context) in D:\a\1\s\src\Prowlarr.Http\Middleware\VersionMiddleware.cs:line 28 at Microsoft.AspNetCore.ResponseCompression.ResponseCompressionMiddleware.InvokeCore(HttpContext context) at Microsoft.AspNetCore.Authorization.Policy.AuthorizationMiddlewareResultHandler.HandleAsync(RequestDelegate next, HttpContext context, AuthorizationPolicy policy, PolicyAuthorizationResult authorizeResult) at Microsoft.AspNetCore.Authorization.AuthorizationMiddleware.Invoke(HttpContext context) at Microsoft.AspNetCore.Authentication.AuthenticationMiddleware.Invoke(HttpContext context) at Microsoft.AspNetCore.Diagnostics.ExceptionHandlerMiddleware.<Invoke>g__Awaited|6_0(ExceptionHandlerMiddleware middleware, HttpContext context, Task task) are you pointing prowlarr at a proxy such as privoxy? if so check connectivity is working there first (check /config/supervisord.log) Quote Link to comment
Furion Posted January 18, 2023 Share Posted January 18, 2023 (edited) 1 hour ago, binhex said: are you pointing prowlarr at a proxy such as privoxy? if so check connectivity is working there first (check /config/supervisord.log) Thanks for the reply (and all the work you do for the community!). I'm not no - not using proxy or VPN (though i know i probably should be!). Edited January 18, 2023 by Furion Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.