So I’m trying to get Jellyfin accessible on the open web through a cloudflared tunnel

I have a default install of Jellyfin running that is still accessible locally.

I’m able to ping TV.myblogdomain.com

And the Cloudflared dashboard says the connection is up.

I have implemented page rules and caching rules to turn CDN off.

I have set the DNS server on the Jellyfin VM to be the Cloudflared DNS server.

It’s pointed to https://jellyfin:8096/

And it wasn’t working with or without a CIDR in the tunnel configuration.

Should I try uninstalling fail2ban and see if that helps? I thought I configured it right pointing it to the 8096 port but maybe I need to do 80/443?

Any tips or guides would be appreciated.

  • calamityjanitor@lemmy.worldEnglish
    1·
    15 hours ago

    I’m guessing the cloudflared daemon isn’t connecting to jellyfin. You want to use http://. Also is jellyfin the hostname of the VM? Using localhost or 127.0.0.1 might be better ways to specify the same VM without relying on DNS for anything.

    Personal opinion, but I wouldn’t bother with fail2ban, it’s a bit of effort to get it to work with cloudflare tunnel and easy to lock yourself out. Cloudflare’s own zero trust feature would be more secure and only need fiddling around cloudflare’s dashboard.

    • nagaram@startrek.websiteOPEnglish
      2·
      12 hours ago

      Didn’t work.

      Gonna go to bed and kinda just hope this starts working and then try again after work when reality sets in.

      • gdog05@lemmy.worldEnglish
        1·
        4 hours ago

        You will want the actual IP address. Localhost can get lost in various circumstances. If Cloudflare tunnel service and Jellyfin are on the same virtual network it should be fine. But I wouldn’t trust it.

        But yes, your Cloudflare tunnel should only connect to http:// not https. It will serve https on the public side of things.