starred/qBittorrent

Fork 0

mirror of https://github.com/qbittorrent/qBittorrent.git synced 2026-03-02 22:57:32 -05:00

Remote session/thin client #4230

New issue

Open

opened 2026-02-21 17:12:27 -05:00 by deekerman · 24 comments

deekerman commented

2026-02-21 17:12:27 -05:00

Owner

Originally created by @Misiek304 on GitHub (Apr 26, 2016).

Hi,

I was wondering if a remote session feature could be implemented into qBittorrent. I believe this is available in Transmission. The reason behind this function is that the WebUI is not even half as configurable as the actual client. It's just a lot easier to use the program window but it's impossible when the program is running on a remote machine like a server.

If this couldn't be implemented into the actual app maybe a standalone program for this like Transmission Remote GUI?

Thanks.

Originally created by @Misiek304 on GitHub (Apr 26, 2016). Hi, I was wondering if a remote session feature could be implemented into qBittorrent. I believe this is available in Transmission. The reason behind this function is that the WebUI is not even half as configurable as the actual client. It's just a lot easier to use the program window but it's impossible when the program is running on a remote machine like a server. If this couldn't be implemented into the actual app maybe a standalone program for this like Transmission Remote GUI? Thanks.

deekerman added the

Feature request

label

2026-02-21 17:12:27 -05:00

deekerman commented

2026-02-21 17:12:29 -05:00

Author

Owner

@barhom commented on GitHub (Apr 27, 2016):

What are you suggesting exactly?
It seems that you're suggesting to gain access to the remote computer to be able to use the "normal" qBittorrent window.

This is in my opinion way out of scope of qBittorrent. Instead, more work should be put into the webui.

@barhom commented on GitHub (Apr 27, 2016): What are you suggesting exactly? It seems that you're suggesting to gain access to the remote computer to be able to use the "normal" qBittorrent window. This is in my opinion way out of scope of qBittorrent. Instead, more work should be put into the webui.

deekerman commented

2026-02-21 17:12:30 -05:00

Author

Owner

@rezad1393 commented on GitHub (Apr 28, 2016):

what he is suggesting and I agree with ,is that a native app be developed that can access qbittorrent on a remote qbittorrent.
transmission already has this and it is almost exactly like a local instance of transmission running.

about webui, webui is not very good right now. the sorting in file tab and tracker editing isn't implemented. content tab is very slow for high number of files in a torrent and selecting a folder in it is not possible without selecting all the files in it one by one.
and tracker section on the left side on native app is not shown on webui.

@rezad1393 commented on GitHub (Apr 28, 2016): what he is suggesting and I agree with ,is that a native app be developed that can access qbittorrent on a remote qbittorrent. transmission already has this and it is almost exactly like a local instance of transmission running. about webui, webui is not very good right now. the sorting in file tab and tracker editing isn't implemented. content tab is very slow for high number of files in a torrent and selecting a folder in it is not possible without selecting all the files in it one by one. and tracker section on the left side on native app is not shown on webui.

deekerman commented

2026-02-21 17:12:30 -05:00

Author

Owner

@Misiek304 commented on GitHub (Apr 28, 2016):

@rezad1393 - Yes, That's exactly what I'm suggesting. Native app that can access qBittorrent session remotely. Something similar to Transmission Remote GUI. Sorry if I wasn't clear enough.

Instead, more work should be put into the webui.

This is also an option but WebUI would need a lot of work. Right now, for example it's very slow. Definitely enough for basic using but it's not enough for more advanced users. rTorrent is using WebUI quite successfully but to be honest I think that the native app would be a better solution. WebUI could stay as it is for less demanding users and a native app could be an answer for demands of power users.

@Misiek304 commented on GitHub (Apr 28, 2016): @rezad1393 - Yes, That's exactly what I'm suggesting. Native app that can access qBittorrent session remotely. Something similar to Transmission Remote GUI. Sorry if I wasn't clear enough. > Instead, more work should be put into the webui. This is also an option but WebUI would need a lot of work. Right now, for example it's very slow. Definitely enough for basic using but it's not enough for more advanced users. rTorrent is using WebUI quite successfully but to be honest I think that the native app would be a better solution. WebUI could stay as it is for less demanding users and a native app could be an answer for demands of power users.

deekerman commented

2026-02-21 17:12:30 -05:00

Author

Owner

@barhom commented on GitHub (Apr 28, 2016):

I now also agree that this could be useful.

I'm imagining a desktop client that asks you for "Remote session: IP:port + password" when you launch qbittorrent-remote-app.

I would imagine this is A LOT of work though depending on how qbittorrent is coded.

@barhom commented on GitHub (Apr 28, 2016): I now also agree that this could be useful. I'm imagining a desktop client that asks you for "Remote session: IP:port + password" when you launch qbittorrent-remote-app. I would imagine this is A LOT of work though depending on how qbittorrent is coded.

deekerman commented

2026-02-21 17:12:30 -05:00

Author

Owner

@Misiek304 commented on GitHub (Apr 28, 2016):

It would require some work for sure but no one is asking for a fully working solution right now. We could start small and add more functions on the way. That way we could keep more control over a project and help with potential bug fixing.

@Misiek304 commented on GitHub (Apr 28, 2016): It would require some work for sure but no one is asking for a fully working solution right now. We could start small and add more functions on the way. That way we could keep more control over a project and help with potential bug fixing.

deekerman commented

2026-02-21 17:12:30 -05:00

Author

Owner

@deadfreak commented on GitHub (Aug 20, 2016):

After having used transmssion on a NAS and being able to control it with the remote session function, i totally miss this in qBittorrent (which i prefer as a client since it's not banned on many private sites). I hope that qBittorrent adds the ability to connect to a remote session (daemon with web ui).

@deadfreak commented on GitHub (Aug 20, 2016): After having used transmssion on a NAS and being able to control it with the remote session function, i totally miss this in qBittorrent (which i prefer as a client since it's not banned on many private sites). I hope that qBittorrent adds the ability to connect to a remote session (daemon with web ui).

deekerman commented

2026-02-21 17:12:30 -05:00

Author

Owner

@NHellFire commented on GitHub (Apr 2, 2017):

The WebUI API could be used for this. If it's not practical to add support to the main app, it'd be fairly easy to make a separate one as it's just JSON.
With large amounts of torrents loaded, the WebUI is quite slow to use.

@NHellFire commented on GitHub (Apr 2, 2017): The [WebUI API](https://github.com/qbittorrent/qBittorrent/wiki/WebUI-API-Documentation) could be used for this. If it's not practical to add support to the main app, it'd be fairly easy to make a separate one as it's just JSON. With large amounts of torrents loaded, the WebUI is quite slow to use.

deekerman commented

2026-02-21 17:12:30 -05:00

Author

Owner

@Misiek304 commented on GitHub (Apr 3, 2017):

The new WebUI in 3.3.11 is a LOT slower then the one in 3.3.10.
I would really liked to have this feature.

@Misiek304 commented on GitHub (Apr 3, 2017): The new WebUI in 3.3.11 is a LOT slower then the one in 3.3.10. I would really liked to have this feature.

deekerman commented

2026-02-21 17:12:30 -05:00

Author

Owner

@thalieht commented on GitHub (Apr 3, 2017):

@Misiek304 #6447 maybe fixed the slowness but it's not in 3.3.11.

@thalieht commented on GitHub (Apr 3, 2017): @Misiek304 #6447 maybe fixed the slowness but it's not in 3.3.11.

deekerman commented

2026-02-21 17:12:30 -05:00

Author

Owner

@Misiek304 commented on GitHub (Apr 4, 2017):

Let's hope then we will see this soon in the next release.

@Misiek304 commented on GitHub (Apr 4, 2017): Let's hope then we will see this soon in the next release.

deekerman commented

2026-02-21 17:12:31 -05:00

Author

Owner

@sadeqAlbana commented on GitHub (Feb 13, 2018):

the web UI can't handle a lot of torrents (like >1k), it'll get laggy and unresponsive, with high cpu usage on the server side.
remote session is the best solution
currently I'm using VNC to access the server to use qbittorrent gui, and it's the only reason I've installed the desktop version of ubuntu instead of the server version.
what the web UI really lacks is the search function and the category tree view.

@sadeqAlbana commented on GitHub (Feb 13, 2018): the web UI can't handle a lot of torrents (like >1k), it'll get laggy and unresponsive, with high cpu usage on the server side. remote session is the best solution currently I'm using VNC to access the server to use qbittorrent gui, and it's the only reason I've installed the desktop version of ubuntu instead of the server version. what the web UI really lacks is the search function and the category tree view.

deekerman commented

2026-02-21 17:12:31 -05:00

Author

Owner

@http403 commented on GitHub (Mar 28, 2020):

Any update on this topic? It is been over 2 years since the last reply.

@http403 commented on GitHub (Mar 28, 2020): Any update on this topic? It is been over 2 years since the last reply.

deekerman commented

2026-02-21 17:12:31 -05:00

Author

Owner

@FranciscoPombal commented on GitHub (Mar 28, 2020):

the web UI can't handle a lot of torrents (like >1k), it'll get laggy and unresponsive, with high cpu usage on the server side.
remote session is the best solution
currently I'm using VNC to access the server to use qbittorrent gui, and it's the only reason I've installed the desktop version of ubuntu instead of the server version.
what the web UI really lacks is the search function and the category tree view.

There have been many updates since this comment was posted. Some problems were fixed so that the webUI can now handle about 1k torrents on very weak machines, and a few thousands on more capable machines. greater orders of magnitudes than that are still a problem though.
There is now search functionality as well.

@FranciscoPombal commented on GitHub (Mar 28, 2020): > the web UI can't handle a lot of torrents (like >1k), it'll get laggy and unresponsive, with high cpu usage on the server side. > remote session is the best solution > currently I'm using VNC to access the server to use qbittorrent gui, and it's the only reason I've installed the desktop version of ubuntu instead of the server version. > what the web UI really lacks is the search function and the category tree view. There have been many updates since this comment was posted. Some problems were fixed so that the webUI can now handle about 1k torrents on very weak machines, and a few thousands on more capable machines. greater orders of magnitudes than that are still a problem though. There is now search functionality as well.

deekerman commented

2026-02-21 17:12:31 -05:00

Author

Owner

@Roganik commented on GitHub (Nov 15, 2020):

Personally, In web UI I miss the ability to configure it as the default option for opening .torrent files and magnet links. (in my case qbittorrent is running on a NAS device). So I'd love to use qbittorrent as a thin client for that use case.

@Roganik commented on GitHub (Nov 15, 2020): Personally, In web UI I miss the ability to configure it as the default option for opening .torrent files and magnet links. (in my case qbittorrent is running on a NAS device). So I'd love to use qbittorrent as a thin client for that use case.

deekerman commented

2026-02-21 17:12:31 -05:00

Author

Owner

@nick75e commented on GitHub (Dec 26, 2020):

Hi!
The feature I miss is the ability to edit a torrent before upload.
In the webUI I can't pick which files I want, edit their name or priority.

@nick75e commented on GitHub (Dec 26, 2020): Hi! The feature I miss is the ability to edit a torrent before upload. In the webUI I can't pick which files I want, edit their name or priority.

deekerman commented

2026-02-21 17:12:31 -05:00

Author

Owner

@guiltlab commented on GitHub (Jul 28, 2021):

Adding my vote to this suggestion, I love this feature in Deluge where it is much better than Deluge WebUI in terms of responsiveness (and functionality, tbh).

Considering qbit's WebUI is horribly slow for me (>5k torrents seeding) despite qbit app running perfectly fine and my internet being very good, perhaps thin client would make remote connection work smoothly in the same manner that it does on Deluge?

Of course, improving Web UI's stability and speed could be a solution as well, but it would have to be a very major change considering how slow it is currently, so I'm wondering if it's even possible to improve it that much.

Thank you for your time and effort in developing this software :) Cheers

@guiltlab commented on GitHub (Jul 28, 2021): Adding my vote to this suggestion, I love this feature in Deluge where it is _much_ better than Deluge WebUI in terms of responsiveness (and functionality, tbh). Considering qbit's WebUI is horribly slow for me (>5k torrents seeding) despite qbit app running perfectly fine and my internet being very good, perhaps thin client would make remote connection work smoothly in the same manner that it does on Deluge? Of course, improving Web UI's stability and speed could be a solution as well, but it would have to be a very major change considering how slow it is currently, so I'm wondering if it's even possible to improve it that much. Thank you for your time and effort in developing this software :) Cheers

deekerman commented

2026-02-21 17:12:31 -05:00

Author

Owner

@JrManPT commented on GitHub (Aug 15, 2021):

I would really love this feature, it would allow me to save power by changing my qbittorrent instalation to a low powered pc on my network.

@JrManPT commented on GitHub (Aug 15, 2021): I would really love this feature, it would allow me to save power by changing my qbittorrent instalation to a low powered pc on my network.

deekerman commented

2026-02-21 17:12:31 -05:00

Author

Owner

@bnzbnz commented on GitHub (Dec 7, 2021):

I'm working on a thin client. Please, what features would you like to be implemented (except for those of the WEB UI): qNOXify : https://github.com/bnzbnz/qNOXify

@bnzbnz commented on GitHub (Dec 7, 2021): I'm working on a thin client. Please, what features would you like to be implemented (except for those of the WEB UI): qNOXify : https://github.com/bnzbnz/qNOXify

deekerman commented

2026-02-21 17:12:31 -05:00

Author

Owner

@JustJoostNL commented on GitHub (Aug 3, 2022):

Add my vote to this feature, the remote function that transmission has should be implemented in qbittorrent, really appreciate it.

@JustJoostNL commented on GitHub (Aug 3, 2022): Add my vote to this feature, the remote function that transmission has should be implemented in qbittorrent, really appreciate it.

deekerman commented

2026-02-21 17:12:31 -05:00

Author

Owner

@nick75e commented on GitHub (Sep 27, 2022):

Also the ability to create a torrent would be great since it's not possible through the WebUI.

@nick75e commented on GitHub (Sep 27, 2022): Also the ability to create a torrent would be great since it's not possible through the WebUI.

deekerman commented

2026-02-21 17:12:31 -05:00

Author

Owner

@southskies commented on GitHub (Jan 29, 2023):

I'm using Electorrent as a qBitorrent thin client with good results.

@southskies commented on GitHub (Jan 29, 2023): +1 I'm using [Electorrent](https://github.com/tympanix/Electorrent) as a qBitorrent thin client with good results.

deekerman commented

2026-02-21 17:12:31 -05:00

Author

Owner

@enchained commented on GitHub (Mar 30, 2025):

Lizard looks very nice, but it's for mac os only
https://nagornyi.su/lizard/

There is also Reflection - bridge between Transmission RPC and qBittorrent WebUI API. In theory it should work with clients like transgui and TrguiNG. But it is not maintained and quite old. I wonder if someone experienced in both protocols and golang could continue working on it.

@enchained commented on GitHub (Mar 30, 2025): Lizard looks very nice, but it's for mac os only https://nagornyi.su/lizard/ There is also [Reflection](https://github.com/h31/Reflection) - bridge between Transmission RPC and qBittorrent WebUI API. In theory it should work with clients like [transgui](https://github.com/lighterowl/transgui) and [TrguiNG](https://github.com/openscopeproject/TrguiNG). But it is not maintained and quite old. I wonder if someone experienced in both protocols and golang could continue working on it.

deekerman commented

2026-02-21 17:12:31 -05:00

Author

Owner

@bnzbnz commented on GitHub (Mar 30, 2025):

for windows: qNoxifyV2

@bnzbnz commented on GitHub (Mar 30, 2025): for windows: [qNoxifyV2](https://github.com/bnzbnz/qBit4DelphiV2-qNOXifyV2)

deekerman commented

2026-02-21 17:12:31 -05:00

Author

Owner

@xavier2k6 commented on GitHub (May 23, 2025):

ANNOUNCEMENT!

For anybody coming across this "Feature Request" & would like/love to see a potential implementation in the future!
Here are some options available to you:

Please select/click the 👍 &/or ❤ reactions in the original/opening post of this ticket.
Please feel free (If you have the "skillset") to create a "Pull Request" implementing what's being requested in this ticket.
(new/existing contributors/developers are always welcome)

DO:

Provide constructive feedback.
Display how other projects implemented same/similar etc.

DO NOT:

Add a "Bump", "me too", "2nd/3rd" etc. or "criticizing" comment(s).
(These will be disregarded/hidden as "spam/abuse/off-topic" etc. as they don't provide anything constructive.)

@xavier2k6 commented on GitHub (May 23, 2025): ## ANNOUNCEMENT! For anybody coming across this **_"Feature Request"_** & would like/love to see a potential implementation in the future! **Here are some options available to you:** 1. Please select/click the 👍 **&/or** ❤ `reactions` in the original/opening post of this ticket. 2. Please feel free _(If you have the "skillset")_ to create a **_"Pull Request"_** implementing what's being requested in this ticket. **_(new/existing contributors/developers are always welcome)_** ____ **DO:** * Provide constructive feedback. * Display how other projects implemented same/similar etc. **DO NOT:** * Add a "Bump", "me too", "2nd/3rd" etc. or "criticizing" comment(s). **(These will be disregarded/hidden as "spam/abuse/off-topic" etc. as they don't provide anything constructive.)**

deekerman referenced this issue

2026-02-21 20:41:33 -05:00

[Tool] Batch close old issues #10312