I noticed letsencrypt support fail2ban i am looking for some advice how to configure it with my Emby server!
fail2ban inside letsencrypt
-
- OMV 4.x
- Nefertiti
-
-
I'm not sure this is the best place to ask such a broad question that really doesn't have too much to do specifically with OMV.
If you google how to use fail2ban you should come across many posts, tutorials, videos etc.
Here is one that I recently followed. Everything isn't directly applicable to Emby, but its a good starting point.
http://www.chlee.co/how-to-sec…x-on-linux-with-fail2ban/ -
-
Is that log file spelled correctly?
-
How is emby setup? Docker? Reverse Proxy? If I remember correctly a service runnin in docker can not always be handled by fail2ban running in OMV. It depends on the network type you use. My docker letsencrypt connections can only be blocked from fail2ban in that container.
-
Emby is inside a Docker container. I looked for by a "Locate" command the file embyserver.txt, no match
another fail2ban in docker is a solution ?
-
Is emby exposed to the Internet?
-
I am really no fail2ban professional. I just setup a letsencrypt reverse proxy with nextcloud and I had the same problem that my OMV fail2ban seemed unable to handle it. So I tried the included fail2ban installation in the letsencrypt container and that worked for me.
-
Yes, my Emby is open to WAN.
-
And accessed via reverse proxy or direct port forwarding?
-
You need to point a jail at your emby log or reverse proxy log
https://emby.media/community/i…onfiguration-using-linux/
I use Traefik and just point it at the access.log
This should work if you're using Traefik (and could be adapted for other logs relatively easily)
Jetzt mitmachen!
Sie haben noch kein Benutzerkonto auf unserer Seite? Registrieren Sie sich kostenlos und nehmen Sie an unserer Community teil!