qBittorent connection issues
Hello, my qBittorent was previously connecting, but has recently stopped (I believe creating more JSON configs was the trigger, but not necessarily the cause).
The Homarr page/widget is reporting: No supported Torrent clients found!
Add a supported Torrent client to view your current downloads
The log file is reporting: Error communicating with your download client 'qBittorrent' (06460fbd-3bcf-496c-bc6f-623502830340): Error: Cookie not found. Auth Failed.
I have tried clearing all cookies.
All pings are green.
What are my next troubleshooting steps?
Solution:Jump to solution
Problem found, trailing space in app name.
"name": "qBittorent " changed to "name": "qBittorent"
Expected behaviour returns.
...
11 Replies
Calendar and Pihole widgets are also busted, but historically resolving qBit solves the others.
Dash. widget works are expected.
Hi, could you try 2 things? Clear cache in homarr, not in the browser. Second thing, just delete the app tile and add it again. @explosive parrot
Cleared homarr cache, no resolution.
Deleted and re-added app tile, re-cleared cache, no resolution.
Same error, new cookie number: Error communicating with your download client 'qBittorent ' (4b58dfaf-9491-47be-970a-9df2e8b87c0b): Error: Cookie not found. Auth Failed.
Have you also tried to restart each app? Since it was working before I do think it is more of a surface thing that is bugging out
As in delete and replace each app tile?
Deployed a new JSON with only qBit and the torrent widget. Works as intended.
Resolution for others searching.
Will post again when offending app title is located.
No as in restarting the containers.
Seeing as it works in a new config, there might be something else indeed.
Tried that long ago
Okay, so I now have two configs:
A fresh config with only qBit and torrent widget. Works as intended.
Offending config with everything removed except qBit and torrent widget. Still does not work.
That is puzzling. Opening homarr on a private tab doesn't do it I guess?
Unfortunately we're using a premade api for torrent clients so there wouldn't be much we could do, even to debug.
Solution
Problem found, trailing space in app name.
"name": "qBittorent " changed to "name": "qBittorent"
Expected behaviour returns.
Problem not reproducable locally, because of course it isn't 🤦
Wth, I can't even imagine how that would cause the problem. Really glad you got it worked out
It was the only difference I found (just me looking through, not a full comparison) in my working and not working JSONs.
Adding the space back in after did not reproduce the error, so I might not have properly identified it at all.
Regardless, hopefully this step will help others troubleshoot.
The trigger for me to even look for it was that I duplicated a JSON and accidentally added a trailing space (damn you mobile keyboard), breaking the JSON (spaces in the middle are fine)