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?

  • hib@lemmy.sdf.orgEnglish
    1·
    2 years ago

    Here is my setup:

    Cloudflare fronts all of my webserver traffic, and I have firewall rules in Cloudflare.

    Then I have an OPNsense firewall that blocks a list of suspicious ips that updates automatically, and only allows port 80/443 connections from Cloudflare’s servers. The only other port I have open is for Wireguard to access all of my internal services. This does not go through Cloudflare obviously, and I use a different domain for my actual IP. I keep Vaultwarden internal for extra safety.

    Next I run every internet facing service in k3s in a separate namespace. This namespace has its own traefik reverse proxy separate from my internal services. This is what port 80/443 forwards to. The namespace has network policies that prevent any egress traffic to my local network. Every container in the WAN facing namespace runs as a user with no login permission to the host. I am also picky about what storage I mount in them.

    If you can get through that you deserve my data I think.

      • hib@lemmy.sdf.orgEnglish
        2·
        2 years ago

        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.

        • kylian0087@lemmy.worldEnglish
          0·
          2 years ago

          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.

          • chonk@sh.itjust.worksEnglish
            1·
            2 years ago

            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).

            • donnnnnb@lemm.ee
              1·
              2 years ago

              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.