![]() ![]() Also make sure you remove any PreUp, PostUp, PreDown, PostDown stuff that your provider might have added (unless you know what it does). In case you have no need for ipv6 connectivity, make sure that you've got it disabled with .disable_ipv6=1 and your wg0.conf does not contain any ipv6 stuff. This is an example of how your wg0.conf should look like. Why would you need this? Wanting to route traffic from other containers over the vpn is probably the most used scenario. Every port in this list will be blocked on the vpn interface, so that there's no risk that they might be exposed to the world via the vpn (mostly there in case your vpn provider screws up and piece of mind). If you need to expose additional ports you can use VPN_ADDITIONAL_PORTS, for example VPN_ADDITIONAL_PORTS=7878/tcp,9117/tcp. If for any reason there's a failure trying to setup ip6tables rules, you'll probably need to do sudo modprobe ip6table_filter on the host, this will mostly happen on systems that have ipv6 completely disabled. If your vpn provider supports ipv6 and you keep it enabled, you'll have full ipv6 connectivity over the vpn connection (confirmed with Mullvad). The WireGuard configuration should not have any ipv6 related stuff when ipv6 is disabled, otherwise creating the interface will fail. The part with .disable_ipv6=0 is optional or you can set it to 1 if there is no need for ipv6 and you want to disable ipv6, no attempt will be made in that case to set ip6tables rules and can prevent an error if the module ip6table_filter isn't loaded on the host. There needs to be a file wg0.conf located in /config/wireguard and you need to set the variable VPN_ENABLED to true for the VPN to start. This image comes bundled with the alternative Web UI VueTorrent, to enable it you'll have to adjust your settings like pictured below. It should be in the format xxxx/tcp,xxxx/udp, take a look at the default with docker logs (variable is printed at container start) or docker inspect. Under certain circumstances it's required to run the WebUI on a different internal port, you can do that by modifying the environment variable WEBUI_PORTS accordingly. You can click on the tag's name to go to its corresponding branch on GitHub, clicking the commit sha brings you to the git diff of that commit. The docker repository is mainly in sync, unless builds fail or commits are pushed for which no builds are started (usually indicated with in the commit message). Which I like to have now I got used to it.The above table reflects the current state of the Git repository. Now that I have added dark version to be associated with torrent files in firefox options I now have two items in the open with software dropdown when I click a torrent link qbittorrent (default) and qbittorrent.exe that is the dark version. Only issue I had was making firefox open torrent files with the dark version. You can switch between dark and light version too found that by accident when I clicked original icon and found my recent torrents were added in original version. Also it does not replace the existing install of qBittorrent and also carries over you settings in the dark version. I have been using it for a day and seems to work as good as standard version. In windows you may need to run the installer as administrator or you may get an error. Thanks to wenji_gefersa for letting me no in his recent post. Hi wanted to let everyone no there is a dark version now available.
0 Comments
Leave a Reply. |