qBittorrent - Ping timed out
logs:
---------------
Redirect works, web ui works; but ping times out, no supported torrent clients found.
---------------
version: 0.13.2
qbittorrent version: 4.5.2
qbittorrent installation method: apt
os: debian 12 amd64
17 Replies
Hi, did you configure the internal address ending with /#/? It is recommended to not put anything after the port
unfortunately, removing the
/#/ didn't help 😦And you confirm that qbit is running and on that the address should be accessible to homarr?
UPDATE: set internal address from
http://169.254.111.204:9405/ to http://localhost:9405/, now different error: Error communicating with your download client 'qBittorrent' (a1dbd894-ded9-4380-8a37-55b74d570459): RequestError: connect ECONNREFUSED 127.0.0.1:9405. But when I try to connect on the same address using server's browser, the web UI appeared normally🤷♂️.Are homarr and qbit running on the same machine? You can't use localhost otherwise
Are homarr and qbit running on the same machine?Yes
Are you using any reverse proxy services?
169.254.111.204 looks a bit strange for a local dhcp though I gotta admit
it's the ethernet connection
It is the address of your machine within your own network? Not your Ip address I hope
Nvm I doubled check it is indeed a link-local ip range. Never saw it before though
Could you try this? I'm not sure the problem is the same but the resolution might work https://homarr.dev/docs/community/known-issues#resolution-3
🐛 Known Issues | Homarr Docs
Here we keep track of the currently known issues of Homarr, reported by our community or the developers.
@4irefall Time out simply means it mined out. We set the timer at 5 seconds if I recall correctly. You server might just be slow to respond. But I would do what @tagaishi mentionned too, just in case.
Did this(because i encountered "Unauthorized" error) before i noticed this "bug"
Yes
You server might just be slow to respond.No, it can't be. Opening the web ui takes less than a second.
Maybe homarr is slow then
I am not certain why this issue would occur on a particular service, but I've noticed sometimes it's quite flakey (especially for pings)
omg maybe it's the ufw that makes this error
because i haven't allowed connections from docker interface yet
Tell us if that fixes it
I'm trying allowing from docker0 but I don't know to use ufw properly😭😭😭
Unfortunately this is as far as I can help, I don't use docker, the others may be of more assistance