Closed heisenberg2980 closed 1 year ago
hi Heisenberg,
I think that is because I have not implemented login for qbittorrent.
I have on my qBit the setting "Bypass authentication for clients on localhost" enabled; the response you are getting looks to me like it fails logging in.
Does it work if you turn on that setting (of course, provided you feel comfortable with that)?
I was getting the same error until I added the "Bypass authentication for clients on localhost" and "Bypass authentication for clients in whitelisted IP subnets".
I also added "network_mode: host" to my docker compose to ensure it was a part of my whitelisted IPs.
Ok, the option "Bypass authentication for clients on localhost" didn´t work for me but I think that is because I am routing the traffic from radarr/sonarr/qbittorrent through a VPN (with gluetun), but using the option "Bypass authentication for clients in whitelisted IP subnets" and adding the IP address of the container with subnet /32 did work, and I think this is the most secure way to do it as only that IP address will bypass authentication instead of the whole subnet
@heisenberg2980 , @Andystew94 I added the possibility to authenticate with username&password to qbittorrent. Hope that solves the issue also for future users.
I am getting this error when trying to start the container using docker-compose:
This is my docker-compose.yaml file: