Jackett: [rarbg] Error parsing Infinity value. Path '', line 1, position 2. (Config)

[MrHollowPS]

Please use the search bar at the top of the page and make sure you are not creating an already submitted issue. Duplicating issues makes it more difficult for everyone to follow. Your issue may have already been solved in the past as well.

Provide a description of the feature request or bug, the more details the better.
If you are experiencing an issue with a tracker, a full log must be included. Instructions for obtaining logs are here: https://github.com/Jackett/Jackett#troubleshooting

Jackett version:
Mono version (if not using Windows):

---

[emorytaylor]

log.txt
Here's my log for it

[garfield69]

the logs provided so far are the normal logs. But with the enhanced log mode enabled I can see the following:
in response to

Mar 21, 2018 12:39:12 PM | Debug | WebClient(HttpWebClient).GetString(Url:https://torrentapi.org/pubapi_v2.php?get_token=get_token)

we are now getting

Mar 21, 2018 12:39:13 PM | Debug | WebClient(HttpWebClient): Returning OK => Invalid API parameters!

reading the API docs at http://torrentapi.org/apidocs_v2.txt I noted the first paragraph:

When querying the api please use the app_id parameter with your app name so we can generate statistics for it.

so I tested the following direclty from my browser:

https://torrentapi.org/pubapi_v2.php?app_id=Jackett&get_token=get_token

and got a valid token back

{"token":"qbcit5snfl"}

so the fix will be to add the app_id to all queries that Jackett makes on the RarBG API.
I'll code and test a solution shortly.

[helio4k]

How to provide the correct Error Log / where to find it?
Windows Machine
Thank you

[garfield69]

if you are using Jackett in service mode, then simply tick the enhanced logging checkbox near the bottom of your Jackett Dashboard and then click on the apply server settings button further up.
The enhanced logging replaces your regular log, up to and until you reset the service.
if running Jackett from the tray instead of as a service, then enable enhanced logging by adding the command line switches -t -l
The logs are stored at %ProgramData%\Jackett on Windows as log*.txt

[helio4k]

Greatly appreciated,
Thank You

[garfield69]

fix f4a0dfb will be included in the next (pre)release of Jackett, whenever that is published.

[goku-son]

Any idea when this will be fixed ? Thanks.

[garfield69]

@goku-son if you are not using Jackett v0.8.779 ... v0.8.898 then upgrade to fix this problem.
if you are already on any of the above and are still seeing this problem, then there is a different cause which can produce the same error message.
In which case you need to please provide the full enhanced log file so we can take a look and see what RarBG returned to you instead of the expected search results.
You will find the instructions for enabling enhanced logging and the locations of the log file at https://github.com/Jackett/Jackett#troubleshooting.

[goku-son]

@garfield69 thanks so much.....failed to realize I was running Jacket v0.8.105 (yikes!)....upgraded and it's working like a charm!