Just exposed Immich via a remote and reverse proxy using Caddy and tailscale tunnel. I’m securing Immich using OAuth.

I don’t have very nerdy friends so not many people appreciate this.

  • tritonium@midwest.social
    link
    fedilink
    English
    arrow-up
    2
    arrow-down
    12
    ·
    edit-2
    3 days ago

    Do you serve things to a public? Like a website? Because unless you’re serving a public, that’s dumb to do… and you really don’t understand the purpose of it.

    If all you wanted was the ability to access services remotely, then you should have just created a WireGuard tunnel and set your phone/laptop/whatever to auto connect through it as soon as you drop your home Wifi.

    • walden@sub.wetshaving.social
      link
      fedilink
      arrow-up
      7
      ·
      3 days ago

      A lemmy instance, a wiki, and a couple of other website type things, yes.

      Publicly facing things are pretty limited, but it’s still super handy inside the LAN with Adguard Home doing DNS rewrites to point it to the reverse proxy.

      I appreciate what you’re saying, though. A lot of people get in trouble by having things like Radarr etc. open to the internet through their reverse proxy.

      • Lumun@lemmy.zip
        link
        fedilink
        English
        arrow-up
        3
        ·
        3 days ago

        Am I making a mistake by having my Jellyfin server proxied through nginx? The other service I set up did need to be public so I just copied the same thing when I set up Jellyfin but is that a liability even with a password to access?

        • timbuck2themoon@sh.itjust.works
          link
          fedilink
          English
          arrow-up
          5
          ·
          3 days ago

          Not really. Personally I’d allow the service account running jellyfin only access to read media files to avoid accidental deletion but otherwise no.

          Also, jellyfin docs have a sample proxy config. You should use that. It’s a bit more in depth than a normal proxy config.

    • KairuByte@lemmy.dbzer0.com
      link
      fedilink
      English
      arrow-up
      4
      arrow-down
      1
      ·
      3 days ago

      This is very short sighted. I can think of dozens of things to put on the open internet that aren’t inherently public. The majority are things for sharing with multiple people you want to have logins for. As long as the exposed endpoints are secure, there’s no inherent problem.

        • KairuByte@lemmy.dbzer0.com
          link
          fedilink
          English
          arrow-up
          2
          ·
          2 days ago

          Seriously?

          Plex, Jellyfin, VaultWarden, AdGuard, Home Assistant, GameVault, any flavor of pastebin, any flavor of wiki, and the list goes on.

          If you’re feeling spicy throw whatever the hell you want onto a reverse proxy and put it behind a zero trust login.

          The idea that opening up anything at all through to the open internet is “dumb” is antiquated. Are there likely concerns that need to be addressed? Absolutely. But don’t make blanket statements about virtually nothing belonging on the open internet.