You have to add the uid/gid to the docker-compose yaml file to specify which user/group you want to run as. They go in the “environment:” section as “PUID” and “PGID”. I have a post here that explains how to set it up with Glutun:
1 Like
I’ve since gotten this working, but I’m trying to set up the qBittorrent container so it can be accessed via qbittorrent.nas.mydomain.com now.† When I go through that domain, I get an “Unauthorized” message.
I did some poking around and found out that, in a standard qBittorrent image, you can set ports: - '8080:8080' and it should work, but this causes a conflict with network_mode: container:gluetun according to my logs.
Container qbittorrent Creating\nError response from daemon: conflicting options: port publishing and the container type network mode
Is there any way to resolve this? I’m trying to access it just via an Nginx reverse proxy that points that domain to port 8080 on my network.
† I’m not exposing it to the Internet, I’m just doing this as an experiment to get internal traffic on HTTPS as well as external.
The yaml compose from the guide already has the web GUI port in it:
That error suggests that you have a conflict, so either the yaml has two port settings or you have something else on that port conflicting. - or you set the network mode incorrectly
Network mode should only be for routing external traffic so just needs:
network_mode: container:gluetun
Did a bit more poking around and found out it’s an issue related to the config generated by qBittorrent, not the Docker image. Just had to add this line to the Preferences section: WebUI\HostHeaderValidation=false
Actually, I just found out it has nothing to do with that. For some reason I can get in just fine when I type the domain into the search bar, but not when I click on the Nginx proxy host. This happens regardless of whether the config is edited.
It’s outside the scope of this thread, but wanted to write it down in case someone else is interested.