The actual config uses
Not sure why I decided to “censor” it like that.
I’ll try swapping it to http:// and removing f2b for now.
Comment on getting 522 error Cloudflaired + Jellyfin + fail2ban
calamityjanitor@lemmy.world 10 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.
nagaram@startrek.website 10 months ago
gdog05@lemmy.world 10 months ago
You will want the actual IP address. Localhost can get lost in various circumstances. If Cloudflare tunnel service and Jellyfin are on the same virtual network it should be fine. But I wouldn’t trust it.
nagaram@startrek.website 10 months ago
Didn’t work.
Gonna go to bed and kinda just hope this starts working and then try again after work when reality sets in.