Thinking about port forwarding ports 80 and 443 on my router to my home server, where Nginx Proxy Manager will deal with the incoming request.

I’ve already got a Cloudflare tunnel for some stuff also pointing to NPM, but the tunnel is not working for Jellyfin streaming.

It’s so I can expose a service on a nice looking URL I own.

Anything wrong with this?

  • @breadsmasher@lemmy.world
    link
    fedilink
    English
    910 months ago

    NPM as in nginx and not Node Package Manager?

    When you said Jellyfin streaming isn’t working - are you able to actually get to Jellyfin UI and its the stream failing, or you can’t access Jellyfin at all via nginx?

    • @cozy_agent@lemmy.worldOP
      link
      fedilink
      English
      310 months ago

      Nginx Proxy Manager.

      Yeah I can see the Jellyfin UI, but the streaming fails, or is blocked by Cloudflare.

      • @lal309@lemmy.world
        link
        fedilink
        English
        110 months ago

        It’s not working because it is against Cloudflare’s ToS unfortunately.

        First I would ask, do you really have to make Jellyfin publicly accessible?

        If yes, are you able to setup a VPN (i.e. Wireguard) and access Jellyfin through that instead?

        If you don’t want the VPN route then isolate the NPM and Jellyfin instance from the rest of your server infrastructure and run the setup you described (open ports directly to the NPM instance). That is how most people that don’t want to do Cloudflare are running public access to self hosted services. But first, ask yourself the questions above.