Widget Problems with QBittorrent

I have followed the homarr docs to configure my qbit app using a working URL as my external URL (<name>.synology.me:<my_reverse_proxy_port> as defined on my Synology) and another working URL as my internal URL (http://<synology_local_network_ip>:<homarr_docker_port>). I can open both from my local desktop successfully. Then I have added the torrent widget and the current download speed widget. The torrent widget shows "No supported torrent clients found" and the download speed widget is just blank. So, I have checked the homarr log for errors. It says "ERROR Error communicating with your download client 'QBittorrent' (581f43d2-5eb4-4501-9fd3-1c64983a1ba7): TimeoutError: Timeout awaiting 'request' for 5000ms". I am not sure what else I can do? Can somebody help me to get this to work?
Solution:
I think this ended up as a duplicate of https://discord.com/channels/972958686051962910/1171576350310682735 @CrankyPunisher can you confirm this issue is also resolved?...
Jump to solution
6 Replies
explosive parrot
explosive parrot13mo ago
While you await the real team, here's a few things that have worked for me in the past in no particular order: Check your JSON file for accuracy, sometimes things don't save correctly. Enable authentication free access for qBit for homarr's IP. Check to make sure there is no trailing space in the qBit app name inside Homarr (that one killed me for week) Clear all caches inside homarr Make sure there is no trailing "/" (or anything else) for the internal IP of qBit. You can also reduce the authentication failure timeout in qBit setting while you troubleshooting.
Manicraft1001
Manicraft100113mo ago
The error you're getting is very likely due to an invalid network configuration. It means that the container is not able to reach the application. This may be because your container stack does not allow network communication from this container or your firewall night be blocking access. You can use tools like wget, curl, ping and others inside the container to test.
CrankyPunisher
CrankyPunisher12mo ago
Well, I have tried a couple of things and followed the suggestions from @explosive parrot and @Manicraft1001 , but nothing has solved the issue yet.
Manicraft1001
Manicraft100112mo ago
What is "couple of things"? Please be specific. I can't help you if you don't provide what steps you took and what the results were. https://xyproblem.info/
The XY Problem
Asking about your attempted solution rather than your actual problem
Solution
Tag
Tag12mo ago
I think this ended up as a duplicate of https://discord.com/channels/972958686051962910/1171576350310682735 @CrankyPunisher can you confirm this issue is also resolved?
CrankyPunisher
CrankyPunisher12mo ago
I have tried the following couple of things unsuccessfully: 1. Check your JSON file for accuracy, sometimes things don't save correctly. (manually checked; no issue) 2. Enable authentication free access for qBit for homarr's IP. (done; didn't solve the problem) 3. Check to make sure there is no trailing space in the qBit app name inside Homarr (that one killed me for week) (I saw your old post while doing research, but no, I didn't have the same issue) 4. Clear all caches inside homarr (done; no change) 5. Make sure there is no trailing "/" (or anything else) for the internal IP of qBit. (see above) 6. This may be because your container stack does not allow network communication from this container or your firewall night be blocking access. (I turned my fw off for testing; no change) @Tag If my solution is the way it is supposed to work, then 'yes'.
Want results from more Discord servers?
Add your server