fail2ban on Synology NAS
I tried to setup fail2ban for my Immich instance on my Synology NAS. In the beginning I thought that I might have issues with fail2ban itself, but having a working template for Vaultwarden, it was easy to create a filter/jail for Immich. My issue is getting the Immich logs.
I hoped for an easy access, like in Vaultwarden, which writes logs to a mapped volume, so it is easily accessible on the host system by other containers. But this is not the way Immich works. Immich writes to stdout and stderr and lets docker handle the rest. According to someone (probably from the dev team) this is supposed to offer a lot of flexibility.
I tried using journald and syslog, but I can’t find the redirected logs! First they are probably in places I am not supposed to mess with - the NAS hides most of the file system from the user. This makes it hard to look for. But even with ssh access, searching /var/log with grep for traces of my Immich logs I was not able to find them.
Has anyone experience with Immich/Docker/fail2ban and can help setting this up?
I hoped for an easy access, like in Vaultwarden, which writes logs to a mapped volume, so it is easily accessible on the host system by other containers. But this is not the way Immich works. Immich writes to stdout and stderr and lets docker handle the rest. According to someone (probably from the dev team) this is supposed to offer a lot of flexibility.
I tried using journald and syslog, but I can’t find the redirected logs! First they are probably in places I am not supposed to mess with - the NAS hides most of the file system from the user. This makes it hard to look for. But even with ssh access, searching /var/log with grep for traces of my Immich logs I was not able to find them.
Has anyone experience with Immich/Docker/fail2ban and can help setting this up?
