-
Notifications
You must be signed in to change notification settings - Fork 5
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Client IP banned but docker still accessible #11
Comments
I had the same issue. The IP is added to iptables but it's not respected and 192.168.1.25 can still access jellyfin. I fixed it by: Changing the jellyfin container's network to: network_mode: host
This meant updating 'action' in /data/jail.d/jellyfin.local to:
My configs for anyone interested: /data/jail.d/jellyfin.local
jellyfin docker compose:
fail2ban docker compose:
iptables with a successful ban:
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I installed fail2ban on my synology in a docker, the IP detection works correctly however despite the banning rules being created on my synology I still have access to my docker which should be blocked
[jellyfin]
enabled = true
port = 80,443
protocol = tcp
filter = jellyfin
maxretry = 3
bantime = 180
findtime = 43200
logpath = /config/log/jellyfin/*.log
#action = iptables-allports[name=jellyfin, chain=INPUT] => blocks access to NAS but not to docker
action = iptables-allports[name=jellyfin, chain=DOCKER-USER]
The text was updated successfully, but these errors were encountered: