I'm looking for a torrent software to run on my server/VM. I want something that is easy to setup, has a decent web UI, a base set of features like autoadd and... well, you know, actually works.
Been running Deluge for a while but turns out autoadd is broken. Spent too much time trying to fix it.
QBittorrent breaks when I try to add alternative web UI (VueTorrent). I mean, it's still broken after restoring the config file. Also, it can't seem to display error messages in the UI so you have to dig through logs.
Transmission has been unreliable and has performance issues in my experience.
Please, can you recommend something that is actually good?
for me qbitorrent works without any issues on docker, what is the problem with it ?
I'm looking at it daily for .. erm 5 minutes? If you use gui like flood, that will consume more resources for few bells and whistles - it's a waste in my eyes.
Be more specific what does not work, what is your env (OS, etc etc).
I've already mentioned it other comments. It's running in an Arch VM. Purging it and reinstalling does not restore config files. According to one person here the configs are not only stored in ~/.config as the documentation says. On top of that, error messages for torrents are not shown in the UI, but in the log file - with a level of logging that is most undesirable.
Why use a whole ass vm just for a torrent client? You can use pre-built docker containers that works out of the box and with a lot less moving parts (aka things that can break).
FWIW, I run an rtorrent container in a home kube cluster. It mounts my data store as an nfs volume and runs flood in a sidecar container. I just use watch directories on the data store and have a cronjob running flexget to subscribe to torrent rss feeds. Notifications are done with the Pushbullet api.
well, yes, we do.. but we tend to work to fix things so it does what it needs to do.. you are confusing your inability to fix things with "poor design of software"
If you don't want to self host your shit or get it fixed by somebody else, and trying to make that happen by acting like a entitled end-user, pay somebody to do it for you..
but if that all is too hard, start with not being a jerk first.
It took me all of 20 minutes to get qBittorrent, Radarr, Sonarr, and Prowlarr working in docker. And then another 10 minutes to add in the VPN container.
The important thing is that I left the GUI default because they work just fine, there is no need for different GUIs for any of it.
This is exactly what I did for awhile. I switched to qBittorrent just to try it out and I liked it enough I swapped everything from Transmission to qBittorrent. *arr stack still handles everything though.
Transmission for me as I’ve always used it and it’s the only one I could get to update port forwarding through a put request when my vpn reconnects and the tunnelling port changes.
The nightly builds have been fairly stable for me running in a diet-pi vm.
It integrates nicely with flexget but equally as well with the arrs. I havn’t had any major problems. I havn’t heard of many that have.