Qbittorrent has been updated to Release 4.6.0 path/to/appdata/tinyproxy/nf:/etc/tinyproxy/nf data:/etc/tinyproxy #./etc/tinyproxy config copied from container to persistent path below before disabling maping and restarting #uncomment ports and comment network_mode for non-vpn access ALLOWED=172.0.0.0/8 192.0.0.0/8 #allows acces from all docker networks and all LAN path/to/appdata/qbittorrent-vpn:/config ADDITIONAL_PORTS=8888 #add tinyproxy port to iptables/killswitch script Here is a snippet from the compose file I use for it, showing a tinyproxy container running in it that I can then use to route anything on my LAN through to get on the VPN. Display MoreĪs gderf said, this can all be done with the qbittorrent-vpn container, and since he has started looking after it, it isn't out of date or out of support. Main benefit of this over qbittorrentvpn is that it is very easy to edit other container's so that they can also use the VPN as their connection too. Works fine and you can be sure that qbittorrent will only be able to use the VPN for its connection. This is what I did after seeing that qbittorrentvpn was a bit out of date and seemed not to be maintained. You can even have them in the same docker-compose file. qbit's web UI port and torrent port bindings get moved into gluetun's). qbittorrent's) to the gluetun container (i.e. It does also require moving the port bind from the original docker's compose file (i.e. You can bring up gluetun and then very easily route other docker containers through its VPN tunnel simply by selecting `container/gluetun' as the docker container's network. Brings up a docker container VPN client that is able to be used with either WireGuard or OpenVPN, and has preset variables for a lot of the popular VPN providers (and can also be used with other settings if your provider isn't on the list).
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |