Selfhosted

59897 readers

656 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.
Posts here are to be centered around self-hosting. Please ensure it is clear in your post how it relates to self-hosting.
Don't duplicate the full text of your blog or git here. Just post the link for folks to click.
Submission headline should match the article title.
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 3 years ago

MODERATORS

curbstickle@anarchist.nexus

curbstickle_lw@lemmy.world

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

submitted 1 year ago by nagaram@startrek.website to c/selfhosted@lemmy.world

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

[–] nagaram@startrek.website 2 points 1 year 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.

[–] Xanza@lemm.ee 3 points 1 year ago (1 children)

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

[–] nagaram@startrek.website 1 points 1 year ago (2 children)

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

[–] MangoPenguin@lemmy.blahaj.zone 1 points 1 year ago (1 children)

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

[–] nagaram@startrek.website 1 points 1 year ago

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

[–] Xanza@lemm.ee 1 points 1 year ago

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

[–] entropicdrift@lemmy.sdf.org 2 points 1 year ago

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