-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ERROR Can not unmarshal JSON for preferences #34
Comments
Hello ! |
Hey, that would be great. Thanks for looking into it. Here is the API response:
|
Mmmh, that API endpoint is not the issue, the log message was wrong, I fixed it with #35. Can you re-try with docker tag |
just pulled |
Mmmh, I thought the error message was going to change |
What's the API response for |
Hey, the response is Which according to the qbit website is the current webAPI for all versions above 4.1. |
Ok great, so that's not the problem. Did you edit the first API response you posted (the API response for |
Yes, I edited some entries to anonymize it e.g. ports, username. I exchange the charaters with |
Yes, that's what I thought, but |
Sorry, small issue with the CD, it should be fixed now, you can re-pull the image |
Sure, no problem. Now the logs became more verbose:
|
Oh interesting, what's the API response for |
OK, so if understood correctly I change
I also stumbled upon this entry in the API changelog LINK. I don't know if its of interest, just stated change string to integer, which reminded me of the DEBUG error with something about int. I am a noob, so ignore my comments if they do not help :D
|
I added more logs, you can re-pull the image |
Yes, here is the new log (I anonymized the url entry with
|
Ok, I see what's the issue, I'll correct it this evening. Thank you for your reactivity ! |
@martabal thank you for the support! |
To explain what's going on : The qBittorrent API had an issue where it sent an empty string instead of an integer which causes this error (qbittorrent/qBittorrent#15545 and qbittorrent/qBittorrent#13302). I fixed it, it should work again, @peterpiglet can you confirm it 😄 ? (you have to pull again |
Awesome! I can confirm, it is working again. And consequently my Grafana dashboard is working too. satisfaction 😄 Thank you very much for the support! |
Nice ! I released |
Hi, I was using the exporter without problems using qbit 4.5.2 and 4.6.2. However, I just downgraded a client to 4.3.9 and the exporter does not work with this client.
With qbit 4.3.9 I just see the following error in the logs:
Is there anything I can do to make it work with 4.3.9?
The text was updated successfully, but these errors were encountered: