qBittorrent can break automation behind Authentik login
Putting Authentik in front of a can break the link between and download . In this Docker and Ubuntu setup, nginx protects browser access to through Authentik, while autobrr, Sonarr, and Radarr connect directly inside Docker at http://:8080.
has bypass turned on for localhost and allowed Docker subnets, with 172.18.0.0/16 on the allow list. Even with that setup, autobrr logs PUSH_ERROR and release rejected on every grab, along with a re-login failure and a 401 error.
Browser access and internal app traffic are following different paths, so the internal tools still have to satisfy ’s own login rules. The practical question is whether should keep its own login instead of being fully placed behind Authentik.
Key points
- Authentik was added in front of a media stack, but automation stopped working.
- autobrr, Sonarr, and Radarr connect to directly through the Docker network, not through nginx and Authentik.
- had bypass enabled for the Docker subnet, but requests still returned a 401 error.
- autobrr logged PUSH_ERROR, release rejected, and re-login failure on every grab.
- Keeping ’s own login may be simpler than forcing every path through Authentik.