Comment

Comment on Options for protecting home IP on my self hosted home srver

thetrekkersparky@startrek.website ⁨1⁩ ⁨day⁩ ago

So, I already pay for Proton VPN, mostly for the E-Mail, but I do use the vpn currently on my main PC to torrent, which I then manually transfer to my server over the network, but I would like to eliminate the middleman and torrent directly to the server, while still being able to easily remote in. I run CasaOS on my Homelab and I was planning on installing qbittorrent in a container, probably through Portainer. I’m already running Soulseek on the server the same way (originally I was running slskd, but it was overly complicated to set up and once it was set up and working there were lots of upload errors and I didn’t like the UI, so I changed to a Nicontine+ docker), but that’s just open to the web.

source

Sort:hotnew top

towerful@programming.dev ⁨1⁩ ⁨day⁩ ago
Imo, only services that require a VPN exit node should use a VPN exit node.

github.com/qdm12/gluetun
Is a well known VPN container that people use, and works with ProtonVPN.

I don’t know anything about how to do this, but a cursory search for “gluetun qbitorrent docker” suggests that gluetun gets network: “host”. Any container that has to use a VPN exit node gets network_mode: “service:gluetun”. A depends_on: {gluetun details} style option will ensure that any service that should use a VPN exit node will not run unless gluetun is running.

Then it’s getting the data out of the qbittorent container into whatever you are using as a media server.

source
- thetrekkersparky@startrek.website ⁨1⁩ ⁨day⁩ ago
  Thanks I’ll look into this tonight. I’m still trying to wrap my head around dockers and containers etc. I think I’ve a pretty good handle on it now, but it still hurts my brain after a while.
  
  source
  - towerful@programming.dev ⁨1⁩ ⁨day⁩ ago
    In that case, maybe look into proxmox and VMs.
    Then run docker inside a VM. Have multiple VMs of docker for different environments (eg a VM for containers that should only use a VPN, another for media server stuff, another for experimenting… Whatever)
    
    Learning proxmox (or another hypervisor) is well worthwhile, because the base installer sets things up to just work for virtualization. And VMs are great for learning to run services.
    Then you can spin up VMs for isolating environments, and have the benefit of oversight and management tools as well as snapshots. Snapshots means you can take a snapshot, tinker and break things, then roll back to a known good snapshot and try again.
    
    I use proxmox on any bare metal before I start setting up VMs for services. Even if it’s just a single VM with the majority of resources allocated to it.
    
    Is proxmox overkill for running a server for some docker containers? Yes.
    Does it make things easier? IMO, yes. At least operationally safer/easier.
    
    source
SolarpunkSoul@slrpnk.net ⁨14⁩ ⁨hours⁩ ago
I went through the same thought process as you a while ago, also with CasaOS. I ended up using the *arr suite, Jellyseer and then this container via Portainer haugene.github.io/docker-transmission-openvpn/. All the instructions are on there for whichever provider you go with, and all it took was making sure the env variables and permissions were in the right place.

source