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

 

 

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 September 1, 20205 yr by DDock

1 minute ago, DDock said:

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

 

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:-

 

try running 'check for updates'.

Yep! must have been a bug. Thanks. Had me a bit worried that you might have discontinued the project or something. Cheers and thanks for all the hard work!

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:-

 

 

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)

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.

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?

On 9/3/2020 at 2:46 PM, 4554551n said:

Is there any way I can DM you that information?

sure

On 9/5/2020 at 1:13 AM, binhex said:

sure

Oh.
It works now.
I changed nothing.
It's set to auto update, maybe you fixed something in the last couple of days?
But now it works...
The space invader video was missing the "additional_ports" variable. But now it works. Thank you!

Hi @binhex, thanks for another docker. I've only just installed this one. Doesn't seem to have loaded correctly when accessed via lets encrypt, not a massive problem just thought I'd report it.

Hello @binhex, can you please update this docker? They got some issue with indexers, they fixed it in Jackett 0.16.1757

5 hours ago, J05u said:

Hello @binhex, can you please update this docker? They got some issue with indexers, they fixed it in Jackett 0.16.1757

done, check for an updated image in an hour from this post.

3 hours ago, binhex said:

done, check for an updated image in an hour from this post.

Thanks a lot! It's back on track

Hello, everytime i reboot the unraid , all the indexers disappear.  Maybe i´m doing something wrong on the instalation?

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.

Edited November 2, 20205 yr by Byrd

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?

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 November 2, 20205 yr by theshabobo

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.  

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.

delete

Edited November 9, 20205 yr by nekromantik

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

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. 

 

 

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

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

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.

Has the magdl.com indexer disappeared for anyone else? Had this set up but seems to have gone after a recent update, I think. Trying to track back to find out exactly when but no joy so far

Some news about Jackett 0.17.50 ?

Need to use Flaresolverr with Jackett