Problem with QBittorrent communicating with the Torrent and Download Speed widgets
I am using docker qbit on synology. It works fine and I can access the web ui at <syno_ip>:8080. However, I can't get it to work with the torrent or download speed widgets. The homarr log shows " ERROR Error communicating with your download client 'QBittorrent' (924b3f6c-2761-45f8-98cf-d19c60914d25): TimeoutError: Timeout awaiting 'request' for 5000ms". I also noticed that ping fails with qbit showing as red (ping timed out), but I can click on it and it opens just fine. I have used <syno_ip>:8080 as intern and extern to keep things simple. I have read through various posts on Google, but none got me closer to a solution.
Solution:Jump to solution
Just to document the solution. I have used docker inspect <container_name> to get the ip address with container name being qbittorrent for example. I have then put this address as the internal address like http://<container_ip>:<container_port>.
14 Replies
https://mariushosting.com/synology-common-docker-issues-and-fixes/
under "Docker Containers Work on Localhost, but Not Via HTTPS".
Try using "localhost" instead of <syno_ip>
I have just tried it, but on a first look it doesn't work. Do I need to restart the container for this?
@Tag Thank you for getting back to me!
I did notice that I had similar issues with the arr apps talking to qbit, but they all went away when I used qbittorrent as the host. But I think that work around only works with arr apps.
@Tag I spoke too soon. There is a change. The red ping icon no longer gives a timeout error. It now says "ECONNREFUSED: 127.0.01:8080". Maybe I need to add that IP in qbit?
Have you configured the bridge correctly?
It got created during the installation. I haven't changed anything.
Getting the same message for all arr apps in homarr.
With their respective port that is
Then instead of localhost you may need to use each apps IP within that bridge
Frankly we don't know much about synology. I encourage you to search for the term in the search bar here to look at what and how others did
I did and have tried a wagon load of ideas. I appreciate everything you guys can do and understand that you can't resolve every single problem one can encounter.
I am suspicious that it is hanging on dock container to docker container communication. I mean localhost in one container probably rsolves differently for another container.
Since homarr is in its own network bridge, the arr containers are in a separate bridge. Do I need to figure out the actual ip for each docker container? Like 172.x.0.0/y subnet?
I don't know docker very well. Learning along the way! 😉
Let me try that
Can't you change homarr's bridge to use the same as the arr apps?
That gives a timeout message again. Very likely caused by the container not being able ping beyond its container network.
Good idea. Let me try that!
The combination of the docker container ip and moving homarr to the arr bridge did the trick. 🙂
Not very convenient if anything changes on the docker side. I wonder if I should ask someone on the syno channel who knows more about docker about some additional feedback. While it is working, it just doesn't sound like something everybody else is doing. Otherwise somebody would already have pointed it out.
I just tried it for radarr to fix the ping and it worked there as well. 🙂
Nice :)
I think this is a good find that will likely allow other folks to resolve some similar issues as well. I am just not sure if this how it is supposed to work... I think I will check in again tomorrow morning to follow up on the syno channel. Otherwise I might use something that is not intended to work and might break with the next homarr, qbit or syno release,
@Tag Thank you for your help! 🙂
I think it is. The arr apps are available through the synology app store but not homarr, so homarr requires more configuration
Solution
Just to document the solution. I have used docker inspect <container_name> to get the ip address with container name being qbittorrent for example. I have then put this address as the internal address like http://<container_ip>:<container_port>.
Hi, just want to chime in and say thank you very much for this solution (shared network and using container's IP instead of localhost). It resolved my ping and ECONNREFUSED issues. I'm fairly new to Docker, but I was wondering what security issues could arise by allowing containers to share the same network? I know ICC can be disabled (
com.docker.network.bridge.enable_icc=false), but will that break the Torrent widget and Homarr's ability to ping?