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.
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.
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.