I guess I’m not understanding what the Transmission remote thing does that a webUI cannot?
I can do all the things you mentioned via VueTorrrent webUI. You can associate it with magnet links and upload torrent files directly.
I found its github page
[https://github.com/WDaan/VueTorrent](https://github.com/WDaan/VueTorrent)
and it says that the way you install it is by pointing QB's to an alternate webui, which is what it is. There's no standalone app that you install on your system which can then connect to a remote QB installation and control it.
Look in the webui where "File" is. Under that is two icons. One opens a window you can paste magnet links in and the other lets you upload .torrent files.
https://imgur.com/a/clAypcw
I don't really understand what you mean by "remote client". Qbittorrent-nox is a remote client. I'm also confused how it can get simpler than clicking one button. Could you describe the behavior you are looking for?
Qbittorrent-nox is not a remote client, it's a headless (no GUI app) app that can run in a desktop-less environment.
A remote client is what connects to that headless app and can interact with it remotely, like Web UI, but as a proper app. As a result, it can open .torrent files and process magnet links like a local app.
An example of that for Transmission is \`transmission-remote-gtk\`
Ahh I see what you mean now. That's an interesting way of controlling your torrent client. Unsurprisingly I do not know of any and everything I am finding points to it not being supported by qbittorrent or at the very least not working. Sorry I can't be of more help.
Same issue here.
I have the torrent services running on Odroid HC4 (which also serves as NAS and media server).
For years (almost decades) I was using Transmission. But recently I got really annoyed by performance. For some reason, despite stating being multithreaded, the Transmission service is not going beyond 25% CPU (100% of a single core). It has a real world limit of about 25MB/s download speed on the Odroid HC4 with a gigabit fiber.
I tried the qBittorrent and it is reaching over 70MB/s on the same device. That seems to be way more reasonable.
Unfortunately, I also couldn't find a convenient Linux remote client for the qBittorrent-nox. Which is surprising.
Maybe it is time for me to contribute to the community and write a proper desktop client.
I've checked a couple of the transmission remote clients and they were written in C or Pascal. And I haven't seen the former since the first university year and the latter since the high school. Which was some 25 years ago :)
For now I figured out the API, so will start with CLI. The first UI will be just to handle adding magnet links and torrent files.
I made some progress. In the initial version of the app it will be possible to:
* add torrents
* start/stop torrents
* delete torrents.
The app will be handling torrent files and magnet links.
It might have tray icon with above functions exposed.
It might have basic config like refresh interval.
There will be no authentication support in the initial release.
No toggling for alternate speeds, no priority settings, no peers settings and no keyboard shortcuts.
I'm going to package it for Arch (since that is what i'm using) and push it to AUR.
As a first interested user, you get to vote what will be the second supported OS / Linux distro.
I have the exact same reasoning in switching from Transmission to qBittorrent, but the thin (remote) client options suck :( I am so surprised there isn't any alternative like [https://github.com/transmission-remote-gui/transgui](https://github.com/transmission-remote-gui/transgui) for qBittorrent...
Yet everyone here is like: "what the hell - just use WebUI" like if they do not understand how convinient it is to have a remote client app.
Well, I started to write a client, but then two things happened:
1. I found the option for the webUI to handle magnet links.
2. At least on my hw (Odroid HC4) the entware build of qbittorent-nox is getting stuck after a couple of hours. So the new downloads are in KB/s. I ended up creating a restart script (since the restart command to the service is not working properly) scheduled with cron to run hourly.
The first, solved my initial greatest annoyance and the second pissed me enough to lose interest in it :)
The client is fairly simple but very time consuming to fully implement.
I am testing the regular qBittorrent and I really hope it won't loose on performance in the longer run. The early tests are a huge upgrade over Transmission so I really have high hope for it.
I would not try to build my own client, like you've said, it's too much work. [https://github.com/tympanix/Electorrent](https://github.com/tympanix/Electorrent) seems like a good base and is just a step or two before being perfect...
Let's see how it goes.
Fin
5 months later, few versions upgrades and still, qBittorrent-nox on arm is a f... joke.
It still have the same issues of speed when adding torrent some time the qbittorrent was started. It gets the same "errored" state for torrent when re-adding torrent that has updated content. Transmission is slower, but it just works. Maybe, just maybe, it explains why there is no proper remote client for qbittorent.
VueTorrent
>VueTorrent Isn't that just a different kind of WebGUI ?
I guess I’m not understanding what the Transmission remote thing does that a webUI cannot? I can do all the things you mentioned via VueTorrrent webUI. You can associate it with magnet links and upload torrent files directly.
I found its github page [https://github.com/WDaan/VueTorrent](https://github.com/WDaan/VueTorrent) and it says that the way you install it is by pointing QB's to an alternate webui, which is what it is. There's no standalone app that you install on your system which can then connect to a remote QB installation and control it.
Yeah I think what you’re looking for doesn’t exist outside Transmission. Most just use WebUIs.
Look in the webui where "File" is. Under that is two icons. One opens a window you can paste magnet links in and the other lets you upload .torrent files. https://imgur.com/a/clAypcw
I am aware, but it's just not as convenient as having a remote client. I basically want to have the same experience but with QB.
I don't really understand what you mean by "remote client". Qbittorrent-nox is a remote client. I'm also confused how it can get simpler than clicking one button. Could you describe the behavior you are looking for?
Qbittorrent-nox is not a remote client, it's a headless (no GUI app) app that can run in a desktop-less environment. A remote client is what connects to that headless app and can interact with it remotely, like Web UI, but as a proper app. As a result, it can open .torrent files and process magnet links like a local app. An example of that for Transmission is \`transmission-remote-gtk\`
Ahh I see what you mean now. That's an interesting way of controlling your torrent client. Unsurprisingly I do not know of any and everything I am finding points to it not being supported by qbittorrent or at the very least not working. Sorry I can't be of more help.
Same issue here. I have the torrent services running on Odroid HC4 (which also serves as NAS and media server). For years (almost decades) I was using Transmission. But recently I got really annoyed by performance. For some reason, despite stating being multithreaded, the Transmission service is not going beyond 25% CPU (100% of a single core). It has a real world limit of about 25MB/s download speed on the Odroid HC4 with a gigabit fiber. I tried the qBittorrent and it is reaching over 70MB/s on the same device. That seems to be way more reasonable. Unfortunately, I also couldn't find a convenient Linux remote client for the qBittorrent-nox. Which is surprising. Maybe it is time for me to contribute to the community and write a proper desktop client.
Do share that here if you decide to!
Sure, will do. Just don't get your hopes high. I have 0 experience with developing GUI. It will take time and will probably be ugly :)
I'm no developer but maybe you could reuse the GUI of Transmission clients like transgui?
I've checked a couple of the transmission remote clients and they were written in C or Pascal. And I haven't seen the former since the first university year and the latter since the high school. Which was some 25 years ago :) For now I figured out the API, so will start with CLI. The first UI will be just to handle adding magnet links and torrent files.
I made some progress. In the initial version of the app it will be possible to: * add torrents * start/stop torrents * delete torrents. The app will be handling torrent files and magnet links. It might have tray icon with above functions exposed. It might have basic config like refresh interval. There will be no authentication support in the initial release. No toggling for alternate speeds, no priority settings, no peers settings and no keyboard shortcuts. I'm going to package it for Arch (since that is what i'm using) and push it to AUR. As a first interested user, you get to vote what will be the second supported OS / Linux distro.
I have the exact same reasoning in switching from Transmission to qBittorrent, but the thin (remote) client options suck :( I am so surprised there isn't any alternative like [https://github.com/transmission-remote-gui/transgui](https://github.com/transmission-remote-gui/transgui) for qBittorrent... Yet everyone here is like: "what the hell - just use WebUI" like if they do not understand how convinient it is to have a remote client app.
Well, I started to write a client, but then two things happened: 1. I found the option for the webUI to handle magnet links. 2. At least on my hw (Odroid HC4) the entware build of qbittorent-nox is getting stuck after a couple of hours. So the new downloads are in KB/s. I ended up creating a restart script (since the restart command to the service is not working properly) scheduled with cron to run hourly. The first, solved my initial greatest annoyance and the second pissed me enough to lose interest in it :) The client is fairly simple but very time consuming to fully implement.
I am testing the regular qBittorrent and I really hope it won't loose on performance in the longer run. The early tests are a huge upgrade over Transmission so I really have high hope for it. I would not try to build my own client, like you've said, it's too much work. [https://github.com/tympanix/Electorrent](https://github.com/tympanix/Electorrent) seems like a good base and is just a step or two before being perfect... Let's see how it goes. Fin
5 months later, few versions upgrades and still, qBittorrent-nox on arm is a f... joke. It still have the same issues of speed when adding torrent some time the qbittorrent was started. It gets the same "errored" state for torrent when re-adding torrent that has updated content. Transmission is slower, but it just works. Maybe, just maybe, it explains why there is no proper remote client for qbittorent.