2025-01-23, 01:48 AM
(This post was last modified: 2025-01-23, 01:53 PM by TheDreadPirate. Edited 2 times in total.)
(2025-01-22, 11:25 PM)TheDreadPirate Wrote: Regardless, it sounds like you've gotten things mostly figured out. Except the VPN thing.
Yep; pretty much! Everything (for now) works exactly how I'd like it to, but I have no idea how to have stuff in Docker not become inaccessible via domain name the moment the VPN turns on and then instantly work again when I click the button to turn it off.
I had 2 solutions I thought of: bind {app we don't talk about - TDP} to the network adapter, but to do that, the VPN would need to be on anyway and ProtonVPN on Linux only does IP-based split tunneling, not program-based.
Other solution was move {app we don't talk about - TDP} to Docker as well as my VPN and just have the qBitt container on same network as VPN one, but then I'm afraid that'll mess up my entire setup with {app we don't talk about - TDP} Client since {app we don't talk about - TDP} works with {app we don't talk about - TDP}. So I don't know if I could access {app we don't talk about - TDP} from outside Docker to have {app we don't talk about - TDP} still download stuff to my external hard drive.
Besides those 2 solutions, I'm really not sure how else I could make it work to have my domain name not being able to access my Docker programs the moment it turns on.