[Support] binhex - Jackett

[schuu]

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

[zbron]

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

[Nuke]

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, 2021 by Nuke

[bally12345]

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. 

[Virus]

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

[vashviper]

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

[binhex]

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.

[Virus]

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.

[tential]

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 by tential

[SkidMarks71]

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?

[binhex]

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.

[SkidMarks71]

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!
 

[Danuel]

immortalseed.me not working for a while

 

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

[Strubdog]

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?

[francrouge]

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

[ebecker]

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 by ebecker
somewhat solved my problem