[ Jackett ] [ 0.20.3546 ] Use just about any tracker with Sonarr or Couchpotato

[QNAP_Stephane]

actually i have no clue on how to fix it

[gmatranga86]

actually i have no clue on how to fix it

oh

i will wait for good news, hopefully.

thank you for your reply!

[gmatranga86]

just un update:

i've found a "fix".
Step 1: ping the hostname from the machine to retrieve the IP
Step 2: insert the record IP + hostname in file /etc/hosts
Step 3: profit!

it's something...

bye!

[ade05fr]

Hello everyone
I would like to have the latest version of jackett (which is currently 0.10.597) how can do that? In the qnap store its still the .97 version.

Thanks for your support

Sent from my LEX820 using Tapatalk

[dulcifium]

I can't even see it in the QNAP store...

[shawnhendriks]

I've been running jackett with Sonarr on my qnap for months now successfully. I've purchased a second qnap and I am trying to setup everything there. Now with every indexer, I run the test and I get errors like this

"Exception (eztv): Connection reset by peer: Unable to read data from the transport connection: Connection reset by peer."

I feel like I have duplicated the setup that is still running on my other qnap but must be missing something. Does anyone have any ideas?

Jackett 0.10.599
Mono version 5.14.0.177
QTS firmware 4.4.0.0820
QNAP TVS-872xt

[flonou]

Hi, if you are using this jackett package, be advised that since a new update was released, jackett might try to download the update continuously and failing to update. This fills the tmp folder which can cause various issues (like bad fan speed reporting).
If this happen, just disable auto update in jackett (at least until a new update of the package comes)

[QNAP_Stephane]

updated

[ensignvorik]

Is there any chance of changing this to the version that no longer requires Mono?

Capture.PNG

[QNAP_Stephane]

it is been some month already available on qnapclub

https://www.qnapclub.eu/fr/qpkg/743

[ensignvorik]

Ah, cool. Thanks.

[erik@qnap]

Hi, uninstalled Jackett requiring Mono and installed the standalone version from qnapclub. After that I wanted to revert back to the old setting by copying the Indexers folder and the ServerConfig.json file from my original Jackett install to the /share/CACHEDEV1_DATA/.qpkg/JackettdotNET/Jackett/Jackett folder. But after every stop/start of Jackett, the ServerConfig.json file is overwritten with default (?) settings.

For instance the port number of my original Jackett install was 9117, the new install uses 25633. When I change the port number by setting the port via the web interface, then the port number is changed accordingly. However, again, when I stop and start Jackett, the port is 25633 again.

When I take a look at /share/CACHEDEV1_DATA/.qpkg/JackettdotNET/JackettdotNET.sh then I see, that Jackett is started with './jackett --IgnoreSslErrors true --Port 25633 &'. So looks like it is ignoring the port setting in the ServerConfig.json file and using the port in the JackettdotNET.sh file at start. Any idea why this is executed this way and what is happening? And of course how to fix this?

Checked the log file, but no errors.

[ensignvorik]

As the non mono version has the same name, doesn’t it just install over the top of the old one?

I haven’t got round to doing it myself yet but I assumed that’s what would happen? Thus keeping settings.

Seems my putting this off for now may have paid off.

Look forward to responses.

[erik@qnap]

As the non mono version has the same name, doesn’t it just install over the top of the old one?

I haven’t got round to doing it myself yet but I assumed that’s what would happen? Thus keeping settings.

Seems my putting this off for now may have paid off.

Look forward to responses.

Hello ensignvorik,
It does not install over the old Jackett. It is installed in a new folder JackettdotNET. So if desired, you can run them both at the same time.

[peelos]

tried to remove and reinstall JackettDotnet by deleting from app store and also removing the .qpkg/JackettDotNet folder and reinstalling

but keep getting "refused to connect" error message - any ideas how to fix please?

EDIT: for those with same issue this was fixed by killing the running jackett processes that had blocked the port that Jackett runs on.. a reboot after deinstallation would have probably solved it aswell