docker-rtorrent-rutorrent VS AnonAddy-docker

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

anonaddy provides a docker image for their email forwarding service, you can create and manage as much addresses as you want and have all emails forwarded to your main addy: https://github.com/anonaddy/docker

Please see https://github.com/anonaddy/docker/issues/150 you need to add that domain and port "http://XXXXXXXXXXX:4080" to SANCTUM_STATEFUL_DOMAINS.

Check this issue out on GitHub. Are you using Docker?

Please can you check out this issue on GitHub - https://github.com/anonaddy/docker/issues/163 and let me know if you are still having issues.

Are you able to open an issue on the Docker repo.

I looked into this, but found anonaddy to be an easier docker setup if you're not married to SL

For self-hosting, the two biggest contenders are [SimpleLogin](https://github.com/simple-login/app) and [AnonAddy](https://github.com/anonaddy/docker). I'm not too sure of the pros/cons of them if you self-host, but if you use the hosted version, I personally prefer SimpleLogin's pricing.

This issue should be fixed in the latest Docker release.