![]() ![]() For reference purposes, I kept these port mappings in qBittorrent's docker-compose, but commented the line out. This meant that the docker-compose for Gluetun needed 'port: 8080:8080' specified to be able to access the web UI for qBittorrent, as well as the port I wanted to use for incoming connections. specified in its docker-compose file), not in the originating apps' docker-compose. For any app that is told to use Gluetun for networking, all port mapping needs to be done on Gluetun's end (i.e.Issue: qBittorrent web UI couldn't be accessed ![]() As it's not included as one of the pre-configured providers in Gluetun, I had to follow the instructions for setting up a custom provider ( ). The Gluetun container has been set up to use a Wireguard connection (not OpenVPN) with my VPN provider (Cryptostorm). qBittorrent and Gluetun seems to be a popular setup however from searching some of the errors I encountered, it doesn't seem I'm alone and the fixes weren't always straightforward.įor reference, I am running the linuxserver.io qBittorrent image using docker-compose within a Ubuntu 22.04 LTS VM running on TrueNAS Core. After having spent a good few days configuring and troubleshooting a Docker-baser media management setup, with qBittorrent traffic being passed through a Gluetun container configured for Wireguard, I wanted to document some of the issues I encountered and the steps I took to fixing them.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |