2024-06-19, 09:24 PM
Problem solved. Guidance seems to be that fail2ban should be on the most edge server in the network so your thinking was correct. Using this guide (https://betterstack.com/community/guides...og-server/) I set up an rsyslog server/client setup. On the client, I then streamed the JF logs into rsyslog, then forwarded the logs from .106 to .108. I migrated my f2b implementation to .108 as well and boom, it works.
Here's my custom config file for rsyslog:
# Forward logs to rsyslog server
*.* @@192.168.1.108:514
module(load="imfile" PollingInterval="10") #needs to be done just once
input(type="imfile"
File="/home/<username>/jellyfin/config/log/log*.log"
Tag="jellyfin")
jellyfin.* /home/<username>/jellyfin/config/log/log*.log
Here's my custom config file for rsyslog:
# Forward logs to rsyslog server
*.* @@192.168.1.108:514
module(load="imfile" PollingInterval="10") #needs to be done just once
input(type="imfile"
File="/home/<username>/jellyfin/config/log/log*.log"
Tag="jellyfin")
jellyfin.* /home/<username>/jellyfin/config/log/log*.log