this post was submitted on 21 Apr 2025
26 points (90.6% liked)

Selfhosted

46265 readers
220 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:

  1. Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.

  2. No spam posting.

  3. 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.

  4. Don't duplicate the full text of your blog or github here. Just post the link for folks to click.

  5. Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).

  6. No trolling.

Resources:

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

Questions? DM the mods!

founded 2 years ago
MODERATORS
 

Hi,

I've been trying to set up fail2ban for jellyfin both running in docker from compose and I'm doing something wrong.

Can someone tell me what path in the docker compose file you use for jellyfin logs and what path you use in the jail.d and the filter in filter.d?

Thanks

PS. Sorry for low detail, but I'm on phone and don't have my current conf readily available. Will provide if necessary.

you are viewing a single comment's thread
view the rest of the comments
[–] Zeoic@lemmy.world 3 points 2 days ago (1 children)

Wow, I tested out jellyfin every 6 months for the last few years to see if it was ready to replace plex yet, and I had no idea about such huge security issues. There should really be a big ass warning about making jellyfin publicly accessible in the app and in setup guides..

[–] MaggiWuerze@feddit.org 5 points 2 days ago* (last edited 2 days ago)

The main issue for me is the way they react to it. Not only is there no warning about this, but they also refuse to fix it because it would break client support and they prefer backwards compatibility over security