I have a small homelab that is not open to the internet. I am considering the following setup. Please let me know if there are any glaring issues or if I am over complicating things.

  • I want to setup a reverse proxy in the cloud that will also act as a certificate authority. (I want to limit who can access the server to a small group of people.)

  • I will setup a vpn from a raspberry pi in my home to the reverse proxy in the cloud.

  • The traffic will pass from the raspberry pi vpn to my homelab.

I am not sure if I need the raspberry pi. I like the cloud as the reverse proxy as I do not have a static IP. I would just get a cheap vps from hetzner or something like that.

  • Joe@discuss.tchncs.deEnglish
    10·
    1 month ago

    How will running a CA limit access? eg. Do you want to do client side cert validation? That sounds like an overcomplication. Also not ideal to run a CA (have signing keys) on the proxy server.

  • grehund@lemmy.worldEnglish
    82·
    1 month ago

    Have you considered other approaches, such as Tailscale or Cloudflare Tunnels? I think you’re complicating things.

    • M600@lemmy.worldOPEnglish
      2·
      1 month ago

      I’m not very familiar with either option. I’ll look into both of them. I think cloudflare tunnels have bandwidth limits though and I’ll be hosting jellyfin, so it might eat through the bandwidth quickly.

    • sugar_in_your_tea@sh.itjust.worksEnglish
      1·
      1 month ago

      Doesn’t work if you’re behind CGNAT (which I am), unfortunately.

      To tell, if your public IP matches what your router/modem reports as its WAN IP, you might be golden. If that’s the case, try messing w/ port forwards on your router to see what the ISP lets through. If it’s not the case, you’re behind CGNAT and either need to pay your ISP ($5-10 usually) or use a VPS. I’m behind CGNAT, so I went for the VPS because it’s the same price and I find more value in that vs a publicly routable address.

      • harsh3466@lemmy.mlEnglish
        1·
        1 month ago

        Ah. Yeah. I think then you’ll want to look into cloudflare tunnels. I believe that should get you through the cgnt and deal with the dynamic IP ll in one go.

        • sugar_in_your_tea@sh.itjust.worksEnglish
          3·
          1 month ago

          Yup, cloudflare should work.

          I personally set up a VPS w/ a WireGuard tunnel, with a reverse proxy at the VPS that sends traffic to connected WireGuard clients. My exact setup is something like this:

          1. VPS w/ HAProxy and WireGuard - routing happens based on SNI
          2. Caddy on homelab to handle TLS trunking
          3. router configured with static DNS routes so I can use public addresses w/o hitting the WAN on my LAN

          This could easily be adjusted to only have HAProxy work over the WireGuard interface so there are no public addresses to worry about.

          But I used Tailscale for a while to solve this problem, and cloudflare tunnels would work as well. Lots of options to work around stupid ISP policies…

  • Mike Wooskey@lemmy.thewooskeys.comEnglish
    2·
    1 month ago

    I have a similar setup. I use d.rymcg.tech (a configuration manager for Docker, as well as a collection of open source web services and config templates) and have Traefik (reverse proxy) on a Digital Ocean dropet connected to a VM in my home lab through wireguard. This framework allows me to put authentication and authoriation in front of any apps/services I’m hosting (HTTP basic auth, oauth2, mTLS). This setup allows me to control what is allowed access from outside of my home, without opening any ports.

  • just_another_person@lemmy.worldEnglish
    31·
    1 month ago

    Well if you don’t have a static IP, then your reverse proxy is going to break when your lease changes anyway. Not sure what your intended goal is for access and to what, but this is certainly a more costly and complex setup than needed for whatever it is.

    • Avid Amoeba@lemmy.caEnglish
      4·
      1 month ago

      The VPN should keep access to the homelab even when the external IP changes. Assuming the VPN connects from the homelab to the cloud. The reverse proxy would use the VPN local IPs to connect to services.

  • Justin@lemmy.jlh.nameEnglish
    2·
    1 month ago

    it might be better to skip the cloud server and use cloudflare for dynamic dns. The standardized way to restrict access to websites is with client certificates or a basic authentication (user/pass) proxy. That would help avoid issues with internet traffic passing through the VPN accidentally.

    • M600@lemmy.worldOPEnglish
      1·
      1 month ago

      Thanks! Last time I checked cloudflare had bandwidth limits. My primary uses for it may use a decent amount of bandwidth as I’ll be hosting jellyfin as well as my backup solution.

      • Justin@lemmy.jlh.nameEnglish
        4·
        1 month ago

        Should work well for that!

        If you use cloudflare for dns only and turn cloudflare proxying off, none of your data or traffic goes to cloudflare’s servers. They just act as your dns server, telling your devices what IP to go to.

  • bezoar@lemm.eeEnglish
    12·
    1 month ago

    If you use tailscale you can omit the raspberry pi and tunnel directly from the reverse proxy to each server (could do this with wireguard but requires a little more setup). Also you can configure your cloud server as an exit node so that all traffic from your device go through it, sort of as a vpn service. It’s not as anonymous as a paid VPN service but at least you bypass the ISP or local wifi provider if you’re out and about.