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

Selfhosted

62256 readers
719 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:

Detailed Rules Post

  1. Be civil.

  2. No spam.

  3. Posts are to be related to self-hosting.

  4. Don't duplicate the full text of your blog or readme if you're providing a link.

  5. Submission headline should match the article title.

  6. No trolling.

  7. Promotion posts require active participation, with an account that is at least 30 days old. F/LOSS without a paywall has exceptions, with requirements. See the rules link for details. Tags [CBH] or [AIP] are required, see the links in Rule 8 for details.

  8. AI-related discussions and AI-involved promotional posts have additional requirements for tagging, as noted in Rule 7 and the AI & Promotional Post Expanded Rules post, and find example disclosures here.

Resources:

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

Questions? DM the mods!

founded 3 years ago
MODERATORS
ruud@lemmy.world
Loki@lemmy.world
CannaVet@lemmy.world
devve@lemmy.world
ayyy@sh.itjust.works
curbstickle@anarchist.nexus
curbstickle_lw@lemmy.world
26
Help setting up fail2ban for jellyfin both in separate docker containers? (lemmy.world)
submitted 1 year ago* (last edited 1 year ago) by basic_user@lemmy.world to c/selfhosted@lemmy.world
22 comments fedilink hide all child comments
 

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
[–] just_another_person@lemmy.world 7 points 1 year ago (1 children)

Why? Fail2ban is best placed on the host closest to a network entrypoint. Unless you're intentionally avoiding a bridged network, this isn't going to do much for your security unless the containers are directly addressed by an attached interface and an open service.

I won't go into a whole diatribe, but you should be running containers as single-process instances of applications. You only cause issues by cramming other process to run inside a container.

What are you using it to block, exactly?

[–] basic_user@lemmy.world 0 points 1 year ago (2 children)

Oh I can see how my title could be misunderstood - what I meant is that both jellyfin and fail2ban are running in (separate) docker containers. Not both services crammed.into one.

[–] just_another_person@lemmy.world 0 points 1 year ago (1 children)

But what are you trying to use fail2ban for?

[–] basic_user@lemmy.world 2 points 1 year ago (1 children)

To prevent brute force login attempts into my jellyfin service.

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

These people seem...pretty stupid tbh. Maybe they don't understand what fail2ban is, or what it does, but you should absolutely use fail2ban. Security is objectively better by just having it enabled than not for any service, not just jellyfin.

[–] InvertedParallax@lemm.ee 0 points 1 year ago

That's worse.

Fail2ban isn't an application like jellyfin, it's a security framework that should be built in to the gateway router.