Maybe I’m using the wrong terms, but what I’m wondering is if people are running services at home that they’ve made accessible from the internet. I.e. not open to the public, only so that they can use their own services from anywhere.
I’m paranoid a f when it comes to our home server, and even as a fairly experienced Linux user and programmer I don’t trust myself when it comes to computer security. However, it would be very convenient if my wife and I could access our self-hosted services when away from home. Or perhaps even make an album public and share a link with a few friends (e.g. Nextcloud, but I haven’t set that up yet).
Currently all our services run in docker containers, with separate user accounts, but I wouldn’t trust that to be 100% safe. Is there some kind of idiot proof way to expose one of the services to the internet without risking the integrity of the whole server in case it somehow gets compromised?
How are the rest of you reasoning about security? Renting a VPS for anything exposed? Using some kind of VPN to connect your phones to home network? Would you trust something like Nextcloud over HTTPS to never get hacked?
This year I started using DynDNS with only my IPv6 address since IPv4 is behind CGNAT and it actually works quite well nowadays
What do you mean works? Like you could access from everywhere some services like Plex or Nextcloud?
yes just like with a static IPv4
Ok, I’m not sure of how exactly this works, but I’m gonna check it out since I have IPv6 addresses.
Just to be clear, even from IPv4 only can access my exposed services?
If you expose ports on IPv4 or IPv6 (port forwarding) anyone can access the service behind these ports if they know your address but so do you too