Selfhosted

46685 readers

799 users here now

A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.

Rules:

Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.
No spam posting.
Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.
Don't duplicate the full text of your blog or github here. Just post the link for folks to click.
Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).
No trolling.

Resources:

selfh.st Newsletter and index of selfhosted software and apps
awesome-selfhosted software
awesome-sysadmin resources
Self-Hosted Podcast from Jupiter Broadcasting

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

founded 2 years ago

MODERATORS

[email protected]

getting 522 error Cloudflaired + Jellyfin + fail2ban (startrek.website)

submitted 2 days ago by [email protected] to c/[email protected]

21 comments fedilink hide all child comments

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 are viewing a single comment's thread
view the rest of the comments

[–] [email protected] 6 points 2 days ago (1 children)

https://jellyfin:8096/

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.

[–] [email protected] 2 points 2 days ago (2 children)

I'll try swapping it to http unless you think I should run nginx or something to certify it. I don't know if that will help.

[–] [email protected] 3 points 2 days ago (1 children)

I always advocate for HTTPS. I run a caddy proxy and sidestep cloudflare all-together.

[–] [email protected] 1 points 2 days ago (2 children)

I assume a Caddy set up would get me a URL? I might look into that.

[–] [email protected] 1 points 1 day ago

Correct. Mine is 'jelly.domain.com' which bidirectionally forwards traffic between my domain and my home server.

[–] [email protected] 1 points 2 days ago (1 children)

You don't need caddy if you're running cloudflare tunnels.

[–] [email protected] 1 points 1 day ago

Fair, but if I'm technically violating TOS and CF tunnels aren't working anyways, I might as well try it.

[–] [email protected] 2 points 2 days ago

I run caddy to handle https certs. Works great and it's incredibly easy to setup