what is this path used for, what were would be an ideal location?

7 minutes ago, schuu said:

what is this path used for, what were would be an ideal location?

That’s where you’re downloads folder is. Not useful for Sonarr and Radarr functionality, but useful if you want to manually trigger downloads via Jackett

How can I apply this jackett frontend project for simple search without admin settings? https://github.com/sudozid/jackett-metasearch

Actually this just a four files for Jackett.Common/Content/ folder

How to apply/mount it for docker?

Edited September 16, 20214 yr by Nuke

Can anyone help with this 

An error occurred while testing this indexer
Exception (kicka######): FlareSolverr was unable to process the request, please check FlareSolverr logs. Message: Cloudflare Error: No challenge selectors found, unable to proceed.: FlareSolverr was unable to process the request, please check FlareSolverr logs. Message: Cloudflare Error: No challenge selectors found, unable to proceed.
Click here to open an issue on GitHub for FlareSolverr.

 

removed the url from error, all other indexers working with privoxy accept this one. 

After latest update a day ago,  jackett gives me the following error. I can’t reach the webui anymore either.

2022-11-16 10:35:56,464 DEBG fd 8 closed, stopped monitoring <POutputDispatcher at 22652530812592 for <Subprocess at 22652530814608 with name jackett in state STARTING> (stdout)>
2022-11-16 10:35:56,464 DEBG fd 10 closed, stopped monitoring <POutputDispatcher at 22652531245696 for <Subprocess at 22652530814608 with name jackett in state STARTING> (stderr)>
2022-11-16 10:35:56,464 INFO exited: jackett (exit status 137; not expected)
2022-11-16 10:35:56,464 DEBG received SIGCHLD indicating a child quit
2022-11-16 10:35:59,470 INFO spawned: 'jackett' with pid 74
2022-11-16 10:35:59,494 DEBG 'jackett' stderr output:
Failed to create CoreCLR, HRESULT: 0x80070008

 

 I tried pulling a prior image but didn’t help - binhex/arch-jackett:0.20.2220-1-01

17 hours ago, Virus said:

After latest update a day ago,  jackett gives me the following error. I can’t reach the webui anymore either.

2022-11-16 10:35:56,464 DEBG fd 8 closed, stopped monitoring <POutputDispatcher at 22652530812592 for <Subprocess at 22652530814608 with name jackett in state STARTING> (stdout)>
2022-11-16 10:35:56,464 DEBG fd 10 closed, stopped monitoring <POutputDispatcher at 22652531245696 for <Subprocess at 22652530814608 with name jackett in state STARTING> (stderr)>
2022-11-16 10:35:56,464 INFO exited: jackett (exit status 137; not expected)
2022-11-16 10:35:56,464 DEBG received SIGCHLD indicating a child quit
2022-11-16 10:35:59,470 INFO spawned: 'jackett' with pid 74
2022-11-16 10:35:59,494 DEBG 'jackett' stderr output:
Failed to create CoreCLR, HRESULT: 0x80070008

 

 I tried pulling a prior image but didn’t help - binhex/arch-jackett:0.20.2220-1-01

I have the same issue with jackett. im using unraid v6.9.1

21 hours ago, Virus said:

After latest update a day ago,  jackett gives me the following error. I can’t reach the webui anymore either.

2022-11-16 10:35:56,464 DEBG fd 8 closed, stopped monitoring <POutputDispatcher at 22652530812592 for <Subprocess at 22652530814608 with name jackett in state STARTING> (stdout)>
2022-11-16 10:35:56,464 DEBG fd 10 closed, stopped monitoring <POutputDispatcher at 22652531245696 for <Subprocess at 22652530814608 with name jackett in state STARTING> (stderr)>
2022-11-16 10:35:56,464 INFO exited: jackett (exit status 137; not expected)
2022-11-16 10:35:56,464 DEBG received SIGCHLD indicating a child quit
2022-11-16 10:35:59,470 INFO spawned: 'jackett' with pid 74
2022-11-16 10:35:59,494 DEBG 'jackett' stderr output:
Failed to create CoreCLR, HRESULT: 0x80070008

 

 I tried pulling a prior image but didn’t help - binhex/arch-jackett:0.20.2220-1-01

 

3 hours ago, vashviper said:

I have the same issue with jackett. im using unraid v6.9.1

im not seeing this issue myself - running latest unraid to date, found a match for this error:- 'Failed to create CoreCLR, HRESULT: 0x80070008'

 

https://docs.linuxserver.io/faq#jammy

 

the doc seems to suggest that its due to an older version of the docker engine, so try option 1 (upgrade unraid) or option 2 if you cant/dont want to upgrade.

6 hours ago, vashviper said:

I have the same issue with jackett. im using unraid v6.9.1

 

 

2 hours ago, binhex said:

 

im not seeing this issue myself - running latest unraid to date, found a match for this error:- 'Failed to create CoreCLR, HRESULT: 0x80070008'

 

https://docs.linuxserver.io/faq#jammy

 

the doc seems to suggest that its due to an older version of the docker engine, so try option 1 (upgrade unraid) or option 2 if you cant/dont want to upgrade.

 

 

tnanks for the info. I was also running 6.9.1. 
 

updating to latest unraid fixed issue.

I was searching for torrents today, and midway using this, it stopped working for me.  Any tips to fix it? Can't get to the Web UI, not seeing any errors in the logs.

Edit: It's working again.  Weird.  Maybe server was too overloaded.

Edited January 9, 20233 yr by tential

I can't figure out how to ensure that Jackett is using privoxy in binhex-delugevpn when I set it to use the privoxy ip and port.  When I launch a console window for binhex-Jackett, and then enter in "curl ifconfig.io", the result is my public facing IP, and not the VPN IP.

 

When I do that in the binhex-delugevpn console window, it does return the vpn ip.  

 

Also, just for giggles, I set my Windows PC to use the privoxy ip / port for a proxy server, and when I visit http://ifconfig.io in a browser, it shows my VPN IP.

 

So, I am pretty sure that privoxy is working, but not sure that binhex-Jackett is actually using it.

 

Thoughts?

5 hours ago, SkidMarks71 said:

When I launch a console window for binhex-Jackett, and then enter in "curl ifconfig.io", the result is my public facing IP, and not the VPN IP.

completely expected, proxy's work at the application layer not the OS layer, so unless you configured ping to use the proxy (you cant) then it will always ping out over your normal internet connection.

 

if you want to test to see if jackett is using the proxy then simply set jackett to use the proxy and then stop the privoxy container, then do a search in jackett, if it returns data then its not using the proxy (misconfiguration probably), if it errors and returns nothing then its using the proxy correctly.

Ok, tried as you said (stopped privoxy in delugevpn) and tested Jackett, and it did not search.  So it must be using the proxy values correctly.  

 

Thanks!
 

immortalseed.me not working for a while

 

binhex-jackett-2023-01-17T17-36-14.log

Not sure if this has been mentioned before. I have noticed I seem to get notifications to update Jackett often. Everytime I update it seems to be the same update each time. Update sizes are the same each time. Am I seeing things?

hi guys

 

I'm able to add rss feed to qbitorrent binhex for the past 3 weeks 

 

If i look into the qbitorrent logs it says  the connection to the remote timed out

 

I tried other rss feed from jackett in my seedboxe and it worked to there something with unraid and qbitorrent and jackett binhex

Edited: Rebooting the unraid server then hit the update button for the docker another two times fixed it. 

 

Not really sure what's going on. Docker says it has an update. I update it, goes through it's thing. I go back to the docker page and it says "apply update" I press apply update again, it updates and shows "apply update" again. I've cleared my browser cache, cookies, temp files, etc. No change. 

Edited June 1, 20233 yr by ebecker
somewhat solved my problem

Hello,

I am having a new issue with this docker in the last few days. The container will show as started but I can not access the UI and the arrs cannot access the indexers.

The log indicates the "inotify limit has been reached" I don't know anything about this and couldn't find that term in a search of this thread at all.

I first found the problem yesterday, tried several things including deleting and reinstalling the container to no avail. Eventually I rebooted ther server and that resolved the issue but it has now returned again after less than 24hrs.

Can anyone help?

 

Here is the ful log from the container:

2023-07-10 16:58:44,346 DEBG 'jackett' stderr output:
Unhandled exception. 
2023-07-10 16:58:44,346 DEBG 'jackett' stderr output:
System.IO.IOException: The configured user limit (128) on the number of inotify instances has been reached, or the per-process limit on the number of open file descriptors has been reached.
   at System.IO.FileSystemWatcher.StartRaisingEvents()
   at System.IO.FileSystemWatcher.StartRaisingEventsIfNotDisposed()
   at System.IO.FileSystemWatcher.set_EnableRaisingEvents(Boolean value)
   at Microsoft.Extensions.FileProviders.Physical.PhysicalFilesWatcher.TryEnableFileSystemWatcher()
   at Microsoft.Extensions.FileProviders.Physical.PhysicalFilesWatcher.CreateFileChangeToken(String filter)
   at Microsoft.Extensions.FileProviders.PhysicalFileProvider.Watch(String filter)
   at Microsoft.Extensions.Configuration.FileConfigurationProvider.<.ctor>b__1_0()
   at Microsoft.Extensions.Primitives.ChangeToken.OnChange(Func`1 changeTokenProducer, Action changeTokenConsumer)
   at Microsoft.Extensions.Configuration.FileConfigurationProvider..ctor(FileConfigurationSource source)
   at Microsoft.Extensions.Configuration.Json.JsonConfigurationSource.Build(IConfigurationBuilder builder)
   at Microsoft.Extensions.Configuration.ConfigurationBuilder.Build()
   at Microsoft.AspNetCore.Hosting.WebHostBuilder.BuildCommonServices(AggregateException& hostingStartupErrors)
   at Microsoft.AspNetCore.Hosting.WebHostBuilder.Build()
   at Jackett.Server.Program.Main(String[] args)

2023-07-10 16:58:44,350 DEBG 'jackett' stderr output:
/home/nobody/start.sh: line 4:    90 Aborted                 /usr/lib/jackett/jackett --NoRestart --NoUpdates --DataFolder /config/Jackett

2023-07-10 16:58:44,350 DEBG fd 8 closed, stopped monitoring <POutputDispatcher at 22718703981712 for <Subprocess at 22718704013456 with name jackett in state STARTING> (stdout)>
2023-07-10 16:58:44,351 DEBG fd 10 closed, stopped monitoring <POutputDispatcher at 22718702056336 for <Subprocess at 22718704013456 with name jackett in state STARTING> (stderr)>
2023-07-10 16:58:44,351 WARN exited: jackett (exit status 134; not expected)
2023-07-10 16:58:44,351 DEBG received SIGCHLD indicating a child quit
2023-07-10 16:58:47,354 INFO spawned: 'jackett' with pid 98
2023-07-10 16:58:47,652 DEBG 'jackett' stdout output:
07-10 16:58:47 Info Starting Jackett v0.21.446 

2023-07-10 16:58:47,656 DEBG 'jackett' stdout output:
07-10 16:58:47 Info Jackett Data will be stored in: /config/Jackett 

2023-07-10 16:58:47,791 DEBG 'jackett' stdout output:
07-10 16:58:47 Error System.IO.IOException: The configured user limit (128) on the number of inotify instances has been reached, or the per-process limit on the number of open file descriptors has been reached. 

[v0.21.446.0] System.IO.IOException: The configured user limit (128) on the number of inotify instances has been reached, or the per-process limit on the number of open file descriptors has been reached.
2023-07-10 16:58:47,791 DEBG 'jackett' stdout output:

   at System.IO.FileSystemWatcher.StartRaisingEvents()
   at System.IO.FileSystemWatcher.StartRaisingEventsIfNotDisposed()
   at System.IO.FileSystemWatcher.set_EnableRaisingEvents(Boolean value)
   at Microsoft.Extensions.FileProviders.Physical.PhysicalFilesWatcher.TryEnableFileSystemWatcher()
   at Microsoft.Extensions.FileProviders.Physical.PhysicalFilesWatcher.CreateFileChangeToken(String filter)
   at Microsoft.Extensions.FileProviders.PhysicalFileProvider.Watch(String filter)
   at Microsoft.Extensions.Configuration.FileConfigurationProvider.<.ctor>b__1_0()
   at Microsoft.Extensions.Primitives.ChangeToken.OnChange(Func`1 changeTokenProducer, Action changeTokenConsumer)
   at Microsoft.Extensions.Configuration.FileConfigurationProvider..ctor(FileConfigurationSource source)
   at Microsoft.Extensions.Configuration.Json.JsonConfigurationSource.Build(IConfigurationBuilder builder)
   at Microsoft.Extensions.Configuration.ConfigurationBuilder.Build()
   at Microsoft.AspNetCore.Hosting.WebHostBuilder.BuildCommonServices(AggregateException& hostingStartupErrors)
   at Microsoft.AspNetCore.Hosting.WebHostBuilder.Build()
   at Jackett.Server.Program.Main(String[] args)



2023-07-10 16:58:47,792 DEBG 'jackett' stderr output:
Unhandled exception. 
2023-07-10 16:58:47,792 DEBG 'jackett' stderr output:
System.IO.IOException: The configured user limit (128) on the number of inotify instances has been reached, or the per-process limit on the number of open file descriptors has been reached.
   at System.IO.FileSystemWatcher.StartRaisingEvents()
   at System.IO.FileSystemWatcher.StartRaisingEventsIfNotDisposed()
   at System.IO.FileSystemWatcher.set_EnableRaisingEvents(Boolean value)
   at Microsoft.Extensions.FileProviders.Physical.PhysicalFilesWatcher.TryEnableFileSystemWatcher()
   at Microsoft.Extensions.FileProviders.Physical.PhysicalFilesWatcher.CreateFileChangeToken(String filter)
   at Microsoft.Extensions.FileProviders.PhysicalFileProvider.Watch(String filter)
   at Microsoft.Extensions.Configuration.FileConfigurationProvider.<.ctor>b__1_0()
   at Microsoft.Extensions.Primitives.ChangeToken.OnChange(Func`1 changeTokenProducer, Action changeTokenConsumer)
   at Microsoft.Extensions.Configuration.FileConfigurationProvider..ctor(FileConfigurationSource source)
   at Microsoft.Extensions.Configuration.Json.JsonConfigurationSource.Build(IConfigurationBuilder builder)
   at Microsoft.Extensions.Configuration.ConfigurationBuilder.Build()
   at Microsoft.AspNetCore.Hosting.WebHostBuilder.BuildCommonServices(AggregateException& hostingStartupErrors)
   at Microsoft.AspNetCore.Hosting.WebHostBuilder.Build()
   at Jackett.Server.Program.Main(String[] args)

2023-07-10 16:58:47,797 DEBG 'jackett' stderr output:
/home/nobody/start.sh: line 4:   100 Aborted                 /usr/lib/jackett/jackett --NoRestart --NoUpdates --DataFolder /config/Jackett

2023-07-10 16:58:47,797 DEBG fd 8 closed, stopped monitoring <POutputDispatcher at 22718716840784 for <Subprocess at 22718704013456 with name jackett in state STARTING> (stdout)>
2023-07-10 16:58:47,797 DEBG fd 10 closed, stopped monitoring <POutputDispatcher at 22718702002960 for <Subprocess at 22718704013456 with name jackett in state STARTING> (stderr)>
2023-07-10 16:58:47,798 WARN exited: jackett (exit status 134; not expected)
2023-07-10 16:58:47,798 DEBG received SIGCHLD indicating a child quit
2023-07-10 16:58:48,799 INFO gave up: jackett entered FATAL state, too many start retries too quickly

 

jacket doesnt start

attached the error .

can anyone say why?

 

unraid : 6.12.4

jacket latest reinstalled 

error log jackett.rtf

On 6/1/2021 at 4:29 AM, jebusfreek666 said:

Is there a tutorial somewhere on how to setup jackett to route through a VPN? I have PIA, and Deluge goes through it. But one of the sites jackett searches for me is Nyaa for anime. For the past 3 days I am getting an error 429 too many requests. Not sure what triggered this as I haven't downloaded anything except a couple of episodes in the time frame. I can still access the site through the browser when I turn on the VPN client. So I was hoping to just set up jackett to use the VPN so I can still get my anime. 

Did you ever find this ? i am currently trying to do the same and the instructions found at Q25 of documentation are not clear to me.

Edited November 19, 20232 yr by Sinister
.

Did you ever find this ? i am currently trying to do the same and the instructions found at Q25 of documentation are not clear to me.

If you can tell me which bits are not clear then I can improve the faq

Sent from my 22021211RG using Tapatalk

On 11/10/2023 at 11:43 AM, dadarara said:

jacket doesnt start

attached the error .

can anyone say why?

 

unraid : 6.12.4

jacket latest reinstalled 

error log jackett.rtf 7.58 kB · 2 downloads

ANYONE ? 

10 hours ago, binhex said:

If you can tell me which bits are not clear then I can improve the faq

Sent from my 22021211RG using Tapatalk
 

Good afternoon binhex and thank you for taking the time to respond.

I managed to work out most of my issues except one, now but what was not obvious to me in Faq is exactly what the torznab feed should look like when making this change, i think if there was an example i would have been able to understand much better.

 

I also wasnt aware and correct me if im wrong that inside of jacket server settings you need to enable proxy type to HTTP, change your proxy type to "http://localhost" and your proxy port 8118 otherwise jackett does not talk to indexers, at least not for me.

 

I dont know if i have any of this correct but its mostly what i want and it works, all my containers are routed through delugevpn, the final issue is that i use usenet and now that sonarr is inside of a vpn its not pulling results from them anymore, I am not sure what changes if any i can make to get it working or with this configuration there is a way around the vpn just for the usenet indexer

21 hours ago, dadarara said:

ANYONE ? 

from your logs it looks like you have hit the servers defined inotify instances limit, from your log:-

 

On 7/10/2023 at 10:08 PM, Meatball Flag said:

System.IO.IOException: The configured user limit (128) on the number of inotify instances has been reached, or the per-process limit on the number of open file descriptors has been reached.

and a quick google reveals this unraid post, instances matches watches btw:-

alternatively simply restart your server (not container) and i suspect the issue will go away, but it may come back if you hit your inotifiy watches limit again.

Good day!

 

I'm having an issue where jackett can't successfully test any of my configured indexers.  I noticed that it appears to have started to fail when I updated to Unraid 7.0.0 (based on when my most recent sonarr/radarr files stopped).

 

2025-02-21 20:14:41,869 DEBG 'jackett' stdout output:
02-21 20:14:41 Warn Request to SubsPlease failed with exception 'The request was canceled due to the configured HttpClient.Timeout of 100 seconds elapsing.'. Retrying in 1.317882s.

 

Jackett is going through delugevpn as a proxy as are sonarr and radarr.  I can use sonarr and radarr to look up shows and movies so I'm pretty confident my proxy is OK.

 

 

Any help would be appreciated.

 

 

 

Edited February 22, 20251 yr by ToxicBill
more images

Bump for great justice.