docker-rtorrent-rutorrent VS docker-fail2ban

I'm using the crazy-max/docker-rtorrent-rutorrent container. This image is not pre-packaged with lots of plugins I would normally find when renting a seedbox. I can't even delete torrents from my file system (I'm limited to removing the torrents from the client interface itself).

I am trying to follow this guide, but instead of using qbittorrent, I am attempting to use crazymax's rutorrent container.

The docker image for rutorrent is the one of crazy-max ( crazy-max / docker-rtorrent-rutorrent )

https://github.com/crazy-max/docker-rtorrent-rutorrent seems popular but it does so much it's extremely confusing and I see it uses Traefik and when I tried to configure that last I just failed. I want none of this. Frankly, if I didn't fear for a massive breach on my existing server I wouldn't move because the experience is that everything newer is always worse. I was happiest before systemd existed. Simpler times.

I have setup rutorrent on docker and port forwarded through NPM. Everything's seem to work fine except when I try to add torrents in rutorrent and start downloading , it automatically switches to "pausing" mode. After checking logs in rutorrent container, it repeatedly outputs the following;

I installed this https://github.com/crazy-max/docker-rtorrent-rutorrent By doing the command line from the github, only I replaced the puid and pgid with my own, other than that no changes. For reference:

I have an rTorrent/ruTorrent setup on a VPS, using this docker container. It seems using this container, I cannot access rTorrent CLI directly - just ruTorrent or XMLRPC (which I'm not at all familiar with).

I'm using rutorrent docker container found here: https://github.com/crazy-max/docker-rtorrent-rutorrent

It does, but it defaults to nftables from (I think) Ubuntu 21 and onwards. So when you're running fail2ban in a docker container, it run an iptables command to block the IP. However, it errors out because nftables is default in Ubuntu 19 onwards (only for new installs). See https://github.com/crazy-max/docker-fail2ban down the page. You can replace the defaults, but I do not want to mess with my docker box at this point!

Nginx Reverse Proxy Manager Lets you redirect traffic from a single machine to all of your VMs and servers as well as manage SSL certificates, you can also do things like deploy Fail2Ban

My setup is all docker on the raspberry pi 4 8gb. I can not seem to find a good regex for this log file. All log entries fail when testing. You wish it will put the client entry IP address in iptables. My regex knowledge is zero so I depend on examples (that don't work). I have no problems with the configuration that works fine. The proxy xx access log has a different format, but if someone has a working regex for that file, please let me know. For fail2ban I use https://github.com/crazy-max/docker-fail2ban For NPM I use https://github.com/jc21/nginx-proxy-manager In fail2ban I use the filter.d dir for the conf file. I can see it's loading in the log but the testing from within the docker image gives no result.

My setup right now includes - Rootless Docker (can read and maybe write to journald, syslog seems to require root but maybe I'm wrong) - Fail2ban in a container crazymax/fail2ban

If you are running docker for your stuff, crazy-max dockerized fail2ban works well. Just be sure to export any form of logs out of what you want to protect and into the fail2ban container.

You can use the following docker image to spawn an instance of fail2ban: https://github.com/crazy-max/docker-fail2ban

https://github.com/crazy-max/docker-fail2ban#custom-jails-actions-and-filters