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.
-
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.
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.
-
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.
It should be noted that you’re not permitted to stream video through Cloudflare unless you use their CDN.
-
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.
I'm guessing the cloudflared daemon isn't connecting to jellyfin. You want to use
http://. Also isjellyfinthe hostname of the VM? Usinglocalhostor127.0.0.1might 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.
