@vkc I thought about that, but I'd still consider hiding my public IP somehow when running my server from a PC in my home - maybe it's irrational fear of exposing the network though.

@daria @vkc I would recommend VPS to start. I used to run my own radio station locally and uptime and opening your local LAN to attack are the main issues.

I think having a lot of open source servers open to attack is a hackers playground and most people aren't needy enough to do the opsec stuff. I know I struggled with it so have VPSes now.

I mean you have to know SOME of it but there is a whole level above of extra firewalls and DMZs etc. I don't have my NAS with a Dyndns anymore cos hacking attempts went through the roof!

@daria there's some good tools for that, Pangolin comes to mind- I run one on a VPS so I can share a few things with folks for testing.

Of course, keeping it behind the firewall and just using a VPN is totally fine too.

@vkc My setup if it helps anyone: An RPi 5 (16GB) with a Pimoroni NVMe Duo with two, 1TB SSDs. (One SSD is reserved for my backup.) Runs Raspbian Lite. Hosts my PiHole, Jellyfin, print server with plenty of room to expand to other services. Only accessible within my home network. Total cost was ~$300.

@vkc running ingress/service swarm nodes through a cloudflare tunnel to a proxmox VM on an isolated VLAN, the way the Lord intended

@vkc Did this. Can confirm, it's awesome.

@vkc While it's occasionally frustrating, I overall love it. Use Immich and Emby and Syncthing and NextCloud every single day.

@vkc

Serious question: why do you say, so? Why now?