Hey all! For the longest time I’ve had a server that hosts some things (eg Syncthing), but is only available via SSH tunneling.
I’ve been thinking of self-hosting more things like Nextcloud and Vaultwarden. I can keep my SSH tunneling setup but it might make it difficult to do SSL.
How do you manage the security of having public-facing servers?
Unfortunately no guide, just things I’ve pieced together myself over the years.
Cloudflare is probably the easiest and most intuitive part of the setup though, you can setup dns/proxy/firewall rules very intuitively, and I’m sure there are plenty of guides out there.
Becarefull not everything is allowed true clousflare. I believe officialy only web content is. So having nextcloud behind it for example to upload and download files. Is as far as i am aware against the TOS.
@kylian0087 @hib It used to be but the updated TOS removed the mention of file types and it seems that using media traffic is allowed as per the latest TOS.
Oh that is really nice! Time to make some changes in then!
I was looking into this for Plex the other day. There’s some conflicting information on the internet right now. From what I can tell, large non-HTML content still seems to be against their ToS, unless you’re an Enterprise customer or serving the files/media with CloudFlare’s R2 or Stream services. I hope I’m wrong though, if someone can confirm.
This post from CloudFlare explains the recent changes to their ToS, and the CDN ToS appears to disallow media or large file content.
To clarify, that is only the Cloudflare Tunnel service that has the “only do web traffic” ToS rule. Tunnel is their service that eliminates the need for port forwarding from your home network.
My understanding is that cloudflare DNS can also be a reverse proxy for you and still provide some benefit your security (though, unlike the tunnel service, you do need to expose ports from your home network to the internet).