[Support] binhex - Jackett


binhex

Recommended Posts

It appears that some time in the last few days jackett has become unreachable for me for both Sonarr and Radarr. I am not able to complete auto searches or manual searches.  Reading the log in Sonarr shows:

 

System.Net.WebException: Error getting response stream (ReadDoneAsync2): ReceiveFailure: 'http://192.168.1.69:9117/api/v2.0/indexers/all/results/torznab/api?t=tvsearch&cat=5030,5040,5070,100003&extended=1&apikey=DELETEDFORPRIVACY&offset=0&limit=1000' ---> System.Net.WebException: Error getting response stream (ReadDoneAsync2): ReceiveFailure at System.Net.WebResponseStream.InitReadAsync (System.Threading.CancellationToken cancellationToken) [0x000e6] in /build/mono/src/mono/mcs/class/System/System.Net/WebResponseStream.cs:458 at System.Net.WebOperation.Run () [0x0018f] in /build/mono/src/mono/mcs/class/System/System.Net/WebOperation.cs:283 at System.Net.WebCompletionSource`1[T].WaitForCompletion () [0x0008e] in /build/mono/src/mono/mcs/class/System/System.Net/WebCompletionSource.cs:111 at System.Net.HttpWebRequest.RunWithTimeoutWorker[T] (System.Threading.Tasks.Task`1[TResult] workerTask, System.Int32 timeout, System.Action abort, System.Func`1[TResult] aborted, System.Threading.CancellationTokenSource cts) [0x000e8] in /build/mono/src/mono/mcs/class/System/System.Net/HttpWebRequest.cs:956 at System.Net.HttpWebRequest.GetResponse () [0x0000f] in /build/mono/src/mono/mcs/class/System/System.Net/HttpWebRequest.cs:1218 at NzbDrone.Common.Http.Dispatchers.ManagedHttpDispatcher.GetResponse (NzbDrone.Common.Http.HttpRequest request, System.Net.CookieContainer cookies) [0x0011b] in C:\BuildAgent\work\5d7581516c0ee5b3\src\NzbDrone.Common\Http\Dispatchers\ManagedHttpDispatcher.cs:82 --- End of inner exception stack trace --- at NzbDrone.Common.Http.Dispatchers.ManagedHttpDispatcher.GetResponse (NzbDrone.Common.Http.HttpRequest request, System.Net.CookieContainer cookies) [0x001ca] in C:\BuildAgent\work\5d7581516c0ee5b3\src\NzbDrone.Common\Http\Dispatchers\ManagedHttpDispatcher.cs:113 at NzbDrone.Common.Http.Dispatchers.FallbackHttpDispatcher.GetResponse (NzbDrone.Common.Http.HttpRequest request, System.Net.CookieContainer cookies) [0x000b5] in C:\BuildAgent\work\5d7581516c0ee5b3\src\NzbDrone.Common\Http\Dispatchers\FallbackHttpDispatcher.cs:53 at NzbDrone.Common.Http.HttpClient.ExecuteRequest (NzbDrone.Common.Http.HttpRequest request, System.Net.CookieContainer cookieContainer) [0x0007e] in C:\BuildAgent\work\5d7581516c0ee5b3\src\NzbDrone.Common\Http\HttpClient.cs:121 at NzbDrone.Common.Http.HttpClient.Execute (NzbDrone.Common.Http.HttpRequest request) [0x00008] in C:\BuildAgent\work\5d7581516c0ee5b3\src\NzbDrone.Common\Http\HttpClient.cs:57 at NzbDrone.Core.Indexers.HttpIndexerBase`1[TSettings].FetchIndexerResponse (NzbDrone.Core.Indexers.IndexerRequest request) [0x0004b] in C:\BuildAgent\work\5d7581516c0ee5b3\src\NzbDrone.Core\Indexers\HttpIndexerBase.cs:321 at NzbDrone.Core.Indexers.HttpIndexerBase`1[TSettings].FetchPage (NzbDrone.Core.Indexers.IndexerRequest request, NzbDrone.Core.Indexers.IParseIndexerResponse parser) [0x00000] in C:\BuildAgent\work\5d7581516c0ee5b3\src\NzbDrone.Core\Indexers\HttpIndexerBase.cs:298 at NzbDrone.Core.Indexers.HttpIndexerBase`1[TSettings].TestConnection () [0x0000e] in C:\BuildAgent\work\5d7581516c0ee5b3\src\NzbDrone.Core\Indexers\HttpIndexerBase.cs:335

 

Not sure what the issue is. I have touched nothing, and have actually been out of town all week.

If I copy and paste "http://192.168.1.69:9117/api/v2.0/indexers/all/results/torznab/api?t=tvsearch&cat=5030,5040,5070,100003&extended=1&apikey=DELETEDFORPRIVACY&offset=0&limit=1000" into a browser on its own i get responses. So I have no idea why Sonarr/Radarr have "ReceiveFailure". Not even sure if the problem is with Radarr, Sonarr, or Jackett....

 

Edit for more info:

Just looked at the settings for deluge in sonarr as well, and attmepted to test and it kicked back a red error on that page after failing stating "Unknown exception: Unable to write data to the transport connection: The socket has been shut down." So it seems something big is going on....

 

Turning off PIA for deluge seems to fix everything..... however, not a realistic everyday fix. So clearly the issue is with the way VPN is being handled in a recent update? Checked the credentials, and they are fine and my PIA account is up to date.

 

Edit 2:

After pulling down the image for deluge with PIA off, and confirming everything worked I then pulled down the image with it turned back on. After retesting the indexer and download client in both Sonarr and Radarr, everything seems to be working correctly again. Not sure how long it will last, or what caused the hiccup in the first place but I will update later if it conks out again. 

 

Edit 3:

After 2 manual searches, it is back the the same behavior I reported at the beginning of the post.

Edited by jebusfreek666
Link to comment

Any ideas why this is showing up for this docker? None of my other dockers show this:

 

image.png.c6ec25ed74daca1a2790cf9af85997c2.png

 

I have not made any changes but noticed this has changed to not available. I haven't checked things in about a week, so it would have happened between then and now.

Edited by DDock
Link to comment
1 minute ago, DDock said:

Any ideas why this is showing up for this docker? None of my other dockers show this:

 

image.png.c6ec25ed74daca1a2790cf9af85997c2.png

that is either a unraid bug or docker hub was unavilable at the time the check happened, i can assure you it very much is 'available' :-), just run check for updates now and for me its reporting:-

image.png.5eb6945bba0fb3be1ea3e01a109c6791.png

 

try running 'check for updates'.

Link to comment
On 8/26/2020 at 10:52 PM, binhex said:

yes 'additional_ports' its required to allow access to specific ports as the strict iptable rules will block by default, you may have an out of date template perhaps that doesnt have this setting, if so please add it as a config type of 'variable' to delugevpn, it should look something like the below:-

 

image.thumb.png.3acda313fe3456960a08201e8c5f021f.png

 

I have added the following, and am still having no luck (I have also tried adding them one at a time, in case I didn't need both)

variable.png

port.png

edit.png

Link to comment
3 hours ago, 4554551n said:

I have added the following, and am still having no luck

ok please go to unraid web ui, docker tab, toggle on 'advanced view' then screenshot the main screen showing all the containers, i am most interested in the port and networking settings for jackett and delugevpn.

 

also can you post a screenshot showing the settings for delugevpn, preferably with advanced view toggled on.

Link to comment
On 9/2/2020 at 9:29 PM, binhex said:

ok please go to unraid web ui, docker tab, toggle on 'advanced view' then screenshot the main screen showing all the containers, i am most interested in the port and networking settings for jackett and delugevpn.

 

also can you post a screenshot showing the settings for delugevpn, preferably with advanced view toggled on.

Is there any way I can DM you that information?

Link to comment
  • 1 month later...
  • 2 weeks later...
57 minutes ago, Byrd said:

If anyone is having issues with IPT, the website layout was updated and cookies are broken. The official Jackett container has fixed this in the newest version.

I'm having this issue due the IPT's update.  I see where you can manually add the cookies with the supplied directions, but I'm still getting an error about 

" An error occurred while updating this indexer
Your cookie did not work: Found 0 results in the tracker"

 

Has anyone been able to get passed this part?

Link to comment

I am having the exact same issue. @binhex can you please update the container to the newest version so all of us having issues can get it resolved. Thank you! :)

 

EDIT: Update ran. to version .1999 This fixes the issue. 

NOTE: you may have to remove and re-add the IPT entry in Jackett

 

Edited by theshabobo
Link to comment
1 hour ago, theshabobo said:

I am having the exact same issue. @binhex can you please update the container to the newest version so all of us having issues can get it resolved. Thank you! :)

 

EDIT: Update ran. to version .1999 This fixes the issue. 

NOTE: you may have to remove and re-add the IPT entry in Jackett

 

Yup...just did a force update and configured IPT with cookies and had no issues.  

Link to comment

Good morning. I'm having trouble with the latest version of Jackett connecting to both RADARR and SONARR.  I had to revert back to arch-0.16.1937-1-01 to get them to talk to each other.  I very cleverly fixed the problem without writing down the error, but it said something (truncated) "please check the capabilities (t=caps) and make sure the search mode and categories are supported.".  I could search and download from inside of Jackett, but Jackett and RADARR/SONARR just wouldn't talk to each other.

Link to comment
  • 3 weeks later...

I've been struggling to get Jackett working with Sonarr.

 

I finally found the final bit that got me working (api location).  Here are the settings that worked for me when adding Torznab to Sonarr.  Notice the api location I had to change to get it working (FINALLY!!!)

 

I hope it helps others searching for a solution that works.

 

FYI, I didn't set up any proxy in Jackett

Jackett config.jpg

Jackett config2.jpg

Link to comment

I'm having a lot of issues with indexers just failing for some reason. Today all of them failed and i can't get them back up. I removed them all and added these three again to test, same thing. 

 

image.png.4f990655686543620e3d2206403b8f83.png

 

Logs below: 


2020-11-27 17:31:50,777 DEBG 'jackett' stdout output:
   at System.Net.Http.DecompressionHandler.SendAsync(HttpRequestMessage request, CancellationToken cancellationToken)
   at System.Net.Http.DiagnosticsHandler.SendAsync(HttpRequestMessage request, CancellationToken cancellationToken)
   at CloudflareSolverRe.ClearanceHandler.SendRequestAsync(HttpRequestMessage request, CancellationToken cancellationToken)
   at CloudflareSolverRe.ClearanceHandler.SendAsync(HttpRequestMessage request, CancellationToken cancellationToken)
   at System.Net.Http.HttpClient.FinishSendAsyncBuffered(Task`1 sendTask, HttpRequestMessage request, CancellationTokenSource cts, Boolean disposeCts)
   at Jackett.Common.Utils.Clients.HttpWebClient2.Run(WebRequest webRequest) in /tmp/makepkg/jackett/src/Jackett-0.16.2220/src/Jackett.Common/Utils/Clients/HttpWebClient2.cs:line 165
   at Jackett.Common.Utils.Clients.WebClient.GetResultAsync(WebRequest request) in /tmp/makepkg/jackett/src/Jackett-0.16.2220/src/Jackett.Common/Utils/Clients/WebClient.cs:line 174
   at Jackett.Common.Indexers.BaseWebIndexer.RequestWithCookiesAsync(String url, String cookieOverride, RequestType method, String referer, IEnumerable`1 data, Dictionary`2 headers, String rawbody, Nullable`1 emulateBrowser) in /tmp/makepkg/jackett/src/Jackett-0.16.2220/src/Jackett.Common/Indexers/BaseIndexer.cs:line 495
   at Jackett.Common.Indexers.CardigannIndexer.PerformQuery(TorznabQuery query) in /tmp/makepkg/jackett/src/Jackett-0.16.2220/src/Jackett.Common/Indexers/CardigannIndexer.cs:line 1276
   at Jackett.Common.Indexers.BaseIndexer.ResultsForQuery(TorznabQuery query, Boolean isMetaIndexer) in /tmp/makepkg/jackett/src/Jackett-0.16.2220/src/Jackett.Common/Indexers/BaseIndexer.cs:line 385
   --- End of inner exception stack trace ---
   at Jackett.Common.Indexers.BaseIndexer.ResultsForQuery(TorznabQuery query, Boolean isMetaIndexer) in /tmp/makepkg/jackett/src/Jackett-0.16.2220/src/Jackett.Common/Indexers/BaseIndexer.cs:line 392
   at Jackett.Common.Indexers.BaseWebIndexer.ResultsForQuery(TorznabQuery query, Boolean isMetaIndexer) in /tmp/makepkg/jackett/src/Jackett-0.16.2220/src/Jackett.Common/Indexers/BaseIndexer.cs:line 659
   at Jackett.Common.Services.IndexerManagerService.TestIndexer(String name) in /tmp/makepkg/jackett/src/Jackett-0.16.2220/src/Jackett.Common/Services/IndexerManagerService.cs:line 278
   at Jackett.Server.Controllers.IndexerApiController.Test() in /tmp/makepkg/jackett/src/Jackett-0.16.2220/src/Jackett.Server/Controllers/IndexerApiController.cs:line 129
   at Microsoft.AspNetCore.Mvc.Infrastructure.ActionMethodExecutor.TaskOfIActionResultExecutor.Execute(IActionResultTypeMapper mapper, ObjectMethodExecutor executor, Object controller, Object[] arguments)
   at Microsoft.AspNetCore.Mvc.Infrastructure.ControllerActionInvoker.<InvokeActionMethodAsync>g__Awaited|12_0(ControllerActionInvoker invoker, ValueTask`1 actionResultValueTask)
   at Microsoft.AspNetCore.Mvc.Infrastructure.ControllerActionInvoker.<InvokeNextActionFilterAsync>g__Awaited|10_0(ControllerActionInvoker invoker, Task lastTask, State next, Scope scope, Object state, Boolean isCompleted)
   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>g__Awaited|13_0(ControllerActionInvoker invoker, Task lastTask, State next, Scope scope, Object state, Boolean isCompleted)
   at Microsoft.AspNetCore.Mvc.Infrastructure.ResourceInvoker.<InvokeFilterPipelineAsync>g__Awaited|19_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.Routing.EndpointMiddleware.<Invoke>g__AwaitRequestTask|6_0(Endpoint endpoint, Task requestTask, ILogger logger)
   at Microsoft.AspNetCore.Authentication.AuthenticationMiddleware.Invoke(HttpContext context)
   at Jackett.Server.Middleware.CustomExceptionHandler.Invoke(HttpContext httpContext) in /tmp/makepkg/jackett/src/Jackett-0.16.2220/src/Jackett.Server/Middleware/CustomExceptionHandler.cs:line 26

Link to comment
5 hours ago, musicking said:

Is it normal for this Docker Container to be 3GB? It doesn't look like it's a log issue.

nope its not normal but i havent had time to track down whats causing the increase in size, after some further investigation i found out its due to nuget caching, the next image will be smaller.

  • Like 1
Link to comment

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.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.