Rhonda Sandtits

Glad to see you got it working. One thing to add that you might find useful:

it shows 20054:8080 for a very short period when I start the stack and then disappeared

This is an indication that the container has stopped. Because you have restart: unless-stopped set, the container is stuck in a bootloop so portainer will always show a state of either starting or running. Docker container automatically stop when the application inside the container has exited or completed… Often because the application has encountered an error.

Some more information that may or may not be useful:

A good example of a container stopped because the application has finished is the Cross-seed container that people use to cross reference their torrents seeding in their bittorrent client with torrents available on other torrent trackers. In this case, the application runs a search on each tracker, downloads the files and once the search is done the application exits and then the docker container will stop.

So there’s… Uhh… Quite a bit wrong with this

That’s because it’s garbage that was shit out by a LLM. The constant “I have heard…” for every statement is a thing deepseek does, and it’s bloody annoying.

The reality is that we need more resources to continue putting forth the best personal media experience

How stupid do they think we are?

Wow, that’s crazy. Could really get creative with your config using that!

If it was Windows, it would simply be a matter of configuring the Split-tunneling options in the mullvad app and it would work the way you want, but on to use the split tunneling feature in mullvad on linux is a bit clunky and doesn’t remember your settings so it annoyingly needs you to manually whitelist each app everytime you load it up.

What I do is I run mullvad in a gluetun docker container on my nas and have the environment variable “HTTPPROXY=on” set.

Then, I connect apps on my desktop computer to gluetun by going into the network settings of whatever app I want to route through mullvad and set the proxy settings to “HTTP proxy” <nas ip>:8888. I use these proxy settings for things like FreeTube and one of the web browsers i have installed that I want to use only with a vpn.

This will work if you set the http proxy setting in qbit, but if you are going to the trouble of setting up docker, you may as well have qbit running in a docker container too.

Maybe the best option for you is to install docker (even if you don’t have a server or nas, you can run it on your desktop), and run gluetun and qbit in docker containers, this will auto start on boot running headless in the background and the vpn wont interfere with the rest on you computer.

There are 2 methods:

First method is to open preferences in qbit, under Advanced > Network interface, select “wg0-mullvad” from the drop-down menu. The interface might be named something different for you, but it should stand out as pretty obvious which one to select.

Other method is in qbit > Preferences > Connection, under “Proxy Server” select “SOCKS5” from the drop-down, input 10.64.0.1 as the host and 1080 as the port.

You could even do both these options at the same time if you like, there is absolutely no downside. It’s like wearing 2 condoms except it feels the same as wearing nothing at all.