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.

  • Xanza@lemm.eeEnglish
    4·
    2 months ago

    https://jellyfin:8096/

    Port 8096 is the default HTTP protocol port, and you’re trying to access it via HTTPS. Do you have certificates installed and available for your jellyfin instance? If not, it’s very likely Cloudflare won’t route it correctly.

    I’m not saying this is your specific issue, but it’ll be the one after you fix this one at least. You may need to mess with the cloudflare “current encryption mode” to get this to work.

    • nagaram@startrek.websiteOPEnglish
      1·
      2 months ago

      I believe this is incorrect. I can’t find the forum post from Cloudflare but you cannot use the CDN to deliver video without paying for it, but you can use CF as a reverse proxy via Cloudflared to deliver video so long as you aren’t on the CDN

      They even have blog posts on using Cloudflared for hobby video streaming projects like a RPi pet cam. Unless it’s assumed I have an enterprise account.

      https://www.cloudflare.com/service-specific-terms-application-services/#content-delivery-network-terms

      Unless you are an Enterprise customer, Cloudflare offers specific Paid Services (e.g., the Developer Platform, Images, and Stream) that you must use in order to serve video and other large files via the CDN. Cloudflare reserves the right to disable or limit your access to or use of the CDN, or to limit your End Users’ access to certain of your resources through the CDN, if you use or are suspected of using the CDN without such Paid Services to serve video or a disproportionate percentage of pictures, audio files, or other large files. We will use reasonable efforts to provide you with notice of such action.

  • calamityjanitor@lemmy.worldEnglish
    1·
    2 months 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.