getting 522 error Cloudflaired + Jellyfin + fail2ban
getting 522 error Cloudflaired + Jellyfin + fail2ban
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.
You're viewing a single thread.
It should be noted that you’re not permitted to stream video through Cloudflare unless you use their CDN.
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.
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.
My understanding is that it's technically against their TOS but loosely enforced. They don't specify precise limits since they probably change over time and region. Once you get noticed, they'll block your traffic until you pay. Hence you can find people online that have been using it for years no problem, while other folks have been less lucky.
Basically their business strategy is to offer too-good-to-be-true free services that people start using and relying on, then charging once the bandwidth gets bigger.
It used to be worse, and all of cloudflare's services were technically limited to HTML files, but selectively enforced. They've since changed and clarified their policy a bit. As far as I've ever heard, they don't give a toss about the legality of your content, unless you're a neo Nazi.
unless you're a neo Nazi
I hate being torn between my hatred of tech monopolies and love of seeing Nazis get their shit rocked.
Don't get too excited, it took a fucking long ass time for them to start pulling down neonazi content. For years I heard Patrick Grey (risky.biz) bitch about how Cloudflare refused to take down Nazi content they were hosting.
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.