Selfhosted

Openvpn to connect to the network, 80 and 443 for static websites, that's it.

Email gets delivered by a VPS via a different port, ssh acces via vps as well. No initial connections from an ip not from the my country as well.

None. If anything, I'd probably set up a VPN. But there's nothing so deathly important on my home network that I would need it while away from home. If I wanted to expose services, I'd use a reverse proxy and increase separation between services.

For services that need to be public facing (Mastodon, Lemmy, Gitea...) I'm renting a VPS. Services that are only for personal use run on my home server and are only accessible through Wireguard, with the VPS acting as a "bridge" whenever I'm outside of my home network.

I'll put a recommendation out for if you're going to open ports: use abnormal ports. Someone is likely to try to hit your port 22 for ssh, but not your port 49231.

Edit: It's definitely some security by obscurity. Still use a strong password or keys.

I don't technically open any ports to the public. I have a site-to-site wireguard tunnel to a hosted server. The hosted server is running a hypervisor with two virtual switches. One switch is my external switch and only my Wireguard server is using it. The other is an internal switch where I place other VMs for separate things. A container host, a terminal server with xrdp, a monitoring server with netdata, stuff like that. All technically, but unnecessarily, accessed through nginx proxy manager.

Because it's site2site with my home equipment on the Wireguard server, i can still connect to my home network where i host a number of separate services like HomeAssistant from outside the home network.

I don't use tailscale, but Wireguard vanilla is super easy to work with. I also have fail2ban pretty much everywhere I can install it because it takes up practically zero resources.

I use Remote Desktop, BitTorrent, and play games, so I need some things open for that. I used to be super paranoid about hackers and viruses and shit like that, but it's not like those things are looking for regular, everyday users and even if they did get in my system, I don't keep anything important on my computer so I can just wipe it all out and reinstall everything.

Heaps

I run a few services that require ports to be open. Everything that can go behind a reverse proxy does so. But there's some that can't and that's OK.

80, 443 for HTTP/S, and 587 for a VPN service. Reason being that I travel frequently, and often have to connect through a bunch of different networks, Airport WiFi, mobile roaming, hotel WiFi, etc. and you never know the kinds of network restrictions they impose on their pipes.

80 and 443 is least likely to be dropped, while 587 is a common SMTP port that could make it through most networks.

I'd if I could, but CGNAT.

ipv6 and reverse proxied. yes.

32400