Currently, I use dockerproxy + swag and Cloudflare for externally-facing services. I really like that I don’t have to open any ports on my router for this to work, and I don’t need to create any routes for new services. When a new service is started, I simply include a label to call swag and the subdomain & TLS cert are registered with Cloudflare. About the only complaint I have is Cloudflare’s 100MG upload limit, but I can easily work around that, and it’s not a limit I see myself hitting too often.

What’s not clear to me is what I’m missing by not using Traefik or Caddy. Currently, the only thing I don’t have in my setup is central authentication. I’m leaning towards Authentik for that, and I might look at putting it on a VPS, but that’s the only thing I have planned. Other than that, almost everything’s running on a single Beelink S12. If I had to, I could probably stand up a failover pretty quickly, though.

  • hendrik@palaver.p3x.deEnglish
    1·
    3 months ago

    Well, not using Cloudflare would make us all rely a bit less on a single company that already dominates the internet. And it’d make them unable to theoretically mess with your traffic and snoop on your data. Other than that… I don’t think you’re missing out on features.

      • Zelaf@sopuli.xyzEnglish
        0·
        3 months ago

        1984.hosting has a freely available to use DNS service for domains. They’re a good company that does what Njalla say they do but without the bullshit of stealing peoples domains.

          • Zelaf@sopuli.xyzEnglish
            0·
            3 months ago

            No, Njalla is. They have a history of stealing domains and banning users without explaining why and absolutely refuse to look into why a user got banned in the first place. On top of that generally terrible customer support.

            I’ve had the complete opposite experience with 1984.hosting, support has been great and they even support GPG keys to one of their emails if you want to keep your inquires encrypted.

            • keepee@lemmy.worldEnglish
              1·
              3 months ago

              Interesting. I hadn’t even heard of Njalla, but now I know to avoid them, thanks.

  • N0x0n@lemmy.mlEnglish
    0·
    3 months ago

    Except that everything is under your control and not managed by a third party, not much I think.

    If this setup works for you and you’re happy with it, just keep it going.

    If you have time to spare, want to learn new things, tinkerer arround with network security, certificates, DNS, reverse proxy and, and, and… You can give it a try in a virtual machine and docker containers. But keep in mind that’s not an easy way and involves a lot of personal time before you get a GOOD working self-hosted / exposed services.

    I wouldn’t recommend to open any port on your router except for a secured tunnel like wireguard and connect to your services through that tunnel. Opening port 443/80 on your router is bound to some heavy automated scanning and brute force by bots. If you don’t have the necessary knowledge/tool/hardware, this is just going to put you at risk of ddos and remote attacks.

    That’s way something like cloudflare is populare, they most of the time take care of that nuisance and also why something like wireguard is popular among the selfhosting community.

      • BaroqueInMind@lemmy.oneEnglish
        1·
        3 months ago

        Which crowdsec lists did you use? I’m on the free plan and can only subscribe to three of them and most of everything on the free tier looks like is useless since my Suricata can sync its rules with Proofpoint ET Open rulesets which are significantly more robust