Selfhosted

46685 readers

798 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] 3 points 2 days ago (1 children)

The actual config uses

https://localhost:8096/

Not sure why I decided to "censor" it like that.

I'll try swapping it to http:// and removing f2b for now.

[–] [email protected] 1 points 2 days ago* (last edited 2 days 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.

But yes, your Cloudflare tunnel should only connect to http:// not https. It will serve https on the public side of things.