Hi,

The last google product that is use is gmail, and while searching for a solid alternative, many threads mentionned self hosting, which has been on my mind for a little while but here is what’s stopping me so far: 1/ it sounds like a single point vulnerability 2/ I lack the skills.

As for #2, I’ve been down the privacy rabbithole for a couple years now, I know there are a lot of resources out there and I’m not afraid to learn, I just don’t know where to start.

But I don’t see the point in learning if in the end, I just build a server that could die in a domestic accident, resulting in me loosing a lot of important data.

Any help or advice is greatly appreciated,

  • Jul (they/she)@piefed.blahaj.zone
    link
    fedilink
    English
    arrow-up
    4
    ·
    24 hours ago

    It’s as safe as you make it. Read up and use configurations documented for “production environments” and you have to monitor things yourself. Try to avoid exposing anything to the internet that you don’t have to and use a secure VPN if you can. That limits the exposed attack surface quite a bit.

    Otherwise, use things like crowdsec and/or fail2ban along with ensuring your firewalls are configured to drop all ports not needed. A reverse proxy like Traefik or Caddy in front of all of your web services along with valid TLS/SSL certificates from Let’s Encrypt can help to only need port 443 open most of the time. Crowdsec or fail2ban can then be integrated into the reverse proxy as well to simplify things. It can be difficult to set up the first service, but then things start to fall into place over time.

    Also, be sure to document everything you do, so that you can reproduce it if you need to recover from a disaster as well as to make setting up new services easier.

    • Dop@lemmy.zipOP
      link
      fedilink
      arrow-up
      2
      ·
      1 hour ago

      Thank you for the advice, I always prepare backups before my fuckups and i assume there will be some fuckups whike i learn haha