Setting up a secure blog using hugo, certbot, haproxy, and crowdsec
h0bbl3s.port0.org
A howto guide on setting up a simple and secure blog server using haproxy to serve https, hugo to serve the website, cerbot to generate the tls certificate, and crowdsec for defense

This is my first post on my new site, I hope someone finds it helpful!

    • h0bbl3s@lemmy.worldOP
      4·
      4 months ago

      I know I know. If you wanna install certbot another way feel free. Share it with me I’m sure it’ll take up less space. I only did it that way because it’s the certbot official©®™ instructions. That and I had issues with the other method I tried.

          • keisatsu@infosec.pubEnglish
            1·
            4 months ago

            Yeah it took a while for me to find as well, Debian moved to managing alot of packages you used to install with pip. In many cases you can just prefix pip packages with python3- and find them via apt.

            • h0bbl3s@lemmy.worldOP
              1·
              4 months ago

              I knew that worked for a lot of stuff. That used to be what I’d try first but I honestly just use a venv for pretty much anything that uses pip nowadays. Still helpful to know there is a package though thanks! I intend to test it out.

      • mostlikelyaperson@lemmy.world
        8·
        4 months ago

        Another thing you could check out is Caddy, comes with a lot of stuff onboard and has an optional crowdsec module (though I should point out that I never used that module myself so I can’t make guarantees how well it works) https://caddyserver.com/

        • lemmyvore@feddit.nlEnglish
          31·
          4 months ago

          Or a docker image with Nginx Proxy Manager. You get a working reverse proxy, an automatically renewing certbot, easy to use UI, plus a working nginx install that you can use for serving static files, forward proxy etc.

        • h0bbl3s@lemmy.worldOP
          2·
          4 months ago

          I’ve got plenty of experience with docker and I’ve heard of traefik but never used it. Thanks, I’m gonna look into it.

        • h0bbl3s@lemmy.worldOP
          2·
          4 months ago

          I could have swore I tried it. facepalm I’ll check that out then I might edit that part.

  • matcha_addict@lemy.lolEnglish
    4·
    4 months ago

    Is it just as secure doing this (with crowdsec) vs hosting on a rented server from a cloud provider?

    • h0bbl3s@lemmy.worldOP
      4·
      4 months ago

      My site is on a rented server at digital ocean. Some providers do more or less to protect you themselves though. I don’t think digital ocean does much monitoring or protecting, I’ve had servers on there compromised in the past that would have been caught by my current setup. It can’t hurt in any case.

      I also run crowdsec on my home setup but I don’t have any open ports at home and never get alerts. I had suricata running and plugged into crowdsec as well so it would handle blocking for both, but suricata never got to get any action with crowdsec blocking malicious activity, so I disabled it to save resources.

      • matcha_addict@lemy.lolEnglish
        2·
        4 months ago

        I don’t mean about relying on the protection from these providers. I am talking about the inherent increased security of hosting on a server that’s on a different network than your local network.

        • h0bbl3s@lemmy.worldOP
          1·
          4 months ago

          Oh gotcha. It was late when I replied :p. You absolutely get security with a layer of separation from hosting remotely. I monitor my home network and have a similar setup but I don’t host anything from here. I never get attacked or probed at all compared to my remote server. Just having those open ports makes you a target. Once a few scanners pick up on you hosting content you will absolutely start getting attacked. Another benefit is you don’t have to have any passwords on your remote host, just an ssh key. They can bruteforce all they want, good luck without a zero day. You also keep your personal IP address out of peoples scope by not hosting from the local network.

          I used to run much heavier protection on my home network, but after keeping an eye on all the logs and alerts for a while I realized I was just wasting ram and storage space mostly. Sane firewall settings is enough for a typical home, and something like crowdsec is probably overkill.

          Now if you are hosting stuff it’s a different story. I would actually harden my local network MORE than I did the remote one due to much more of my personal stuff being on my local network. My remote host being compromised would be a mild hassle at most, It does self backups once a week, and I have my entire site in a private git repo I sync to. It would take a few minutes to throw up another server, if my home stuff got compromised a lot more damage could be done.