16
Options for protecting home IP on my self hosted home srver (startrek.website)
submitted 1 year ago by to c/selfhosting@slrpnk.net
13 comments fedilink hide all child comments
 

I've been running a home server at home running CasaOS for a few months now. I use a wireguard vpn to remote in to use Jellyfin on my phone etc. Basically i want to know if there's a way i can both hide my public IP (such as using a conventional vpn for torrenting) while still being able to remote in to my server?

I've been thinking of running running all my network traffic through my server and setting up some sort of firewall too, but I'm fairly new to this as this was originally just a project I did out of spite after getting rid of Spotify. I'm fairly green when it comes to networking and servers, but I'm otherwise pretty good with computers and can muddle my way through most things.

Any suggestions are greatly appreciated.

you are viewing a single comment's thread
view the rest of the comments
[–] 4 points 1 year ago (2 children)

Imo, only services that require a VPN exit node should use a VPN exit node.

https://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.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •
  • [–] [S] 2 points 1 year ago (1 child)

    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.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 1 child comment
    •
  • [–] 1 point 1 year 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.

  • permalink
  • fedilink
  • source
  • parent