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.

  • Encrypt-Keeper@lemmy.worldEnglish
    21·
    7 hours ago

    but you can use CF as a reverse proxy via Cloudflared to deliver video so long as you aren’t on the CDN

    I think this is a common misinterpretation, but based on the limits of free tier CDN. It explains that in order to use the CDN for serving video, you have to use their back end for the video storage, but it doesn’t say that you can stream through their nodes all you want as long as you’re not using their CDN. People have been pressing them for clarification on this but they refuse to comment on it.

    Currently the only method to fully adhere to their terms of service is to use their CDN and to do so via the methods laid out here:

    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.

    You are free to gamble on them not enforcing restrictions on your account however. I only bring this up because many of us have just opted to not use Cloudflare for this.