I have an openwrt router at home which also acts as my home server. It’s running a bunch of services using docker (Jellyfin, Nextcloud, etc.)

I have set up an SSH tunnel between my openwrt router and VPS and can access jellyfin successfully.

I understand that I need to set up a reverse proxy to access multiple services and have https.

But I’m confused if I should set up this reverse proxy on the VPS or on the router itself. Is nginx the easiest option? Should i add subdomains in cloudflare for every service?

Pease don’t recommend vpns since they are all blocked where i live (wireguard, tailscale openVPN, etc.) I’m limited to using ssh tunneling only.

Thanks

    • mFat@lemdro.idOP
      link
      fedilink
      English
      arrow-up
      5
      ·
      7 months ago

      Caddy was exactly what i needed. It magically solved the problem…

    • Samsy@lemmy.ml
      link
      fedilink
      English
      arrow-up
      2
      ·
      edit-2
      7 months ago

      As someone who used caddy over years, I can’t completely agree.

      Caddy has some downsides (nextcloud needs special setup for example) and not everyone is familiar with writing a Caddyfile. (Json)

      For someone new I would recommend “nginx proxy manager”. Easy to install with docker and self explained through GUI.

      • i actually think NPM is more confusing. 1: there are practically always already finished Files for Caddy V2. Most of the times directly in the Repo of the Project. A lot of Devs use Caddy themselves. 2: NPM exposes a lot of Options additionally. This can confuse newcomers. With Caddy, all these extra options are invisible. you just write and see “reverse_proxy jellyfin” and that’s it.

        • gray@lemmy.ml
          link
          fedilink
          English
          arrow-up
          2
          ·
          7 months ago

          Completely agree. I haven’t used NPM since I started self hosting a few years ago, but I was never able to get it to work right. I ended up using apache2 as it was pretty well documented everywhere. Moved to caddy v1 when I found it as the config is so easy to write and understand. Moved to v2 when it was released and had no issues. Their forum is incredibly helpful if you run into any issues. At this point its a “relatively” mature platform and most projects I’ve setup have an example config (usually just 1 or 2 lines because that’s all you need).

    • bork@sh.itjust.works
      link
      fedilink
      English
      arrow-up
      2
      ·
      7 months ago

      Swag was my nginx introduction, and it was mildly confusing because I ran it on docker and didn’t understand how to edit configs at the time. I’d recommend following a guide instead of winging it like I did 😅