starred/qBittorrent

Fork 0

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

Webui Log IP addresses of users who upload torrent #2709

New issue

Open

opened 2026-02-21 16:22:04 -05:00 by deekerman · 6 comments

deekerman commented

2026-02-21 16:22:04 -05:00

Owner

Originally created by @sardonyxserendil on GitHub (Jun 29, 2015).

Please add the ability to log the IP address of users that upload a torrent within the webgui. I've had situations where this feature would have been extremely helpful so I can identify who submitted/uploaded a malicious torrent on my seed box.

Originally created by @sardonyxserendil on GitHub (Jun 29, 2015). Please add the ability to log the IP address of users that upload a torrent within the webgui. I've had situations where this feature would have been extremely helpful so I can identify who submitted/uploaded a malicious torrent on my seed box.

deekerman added the

Feature request

WebUI

labels

2026-02-21 16:22:04 -05:00

deekerman commented

2026-02-21 16:22:07 -05:00

Author

Owner

@ngosang commented on GitHub (Jun 29, 2015):

qBittorrent WebUI has many things to improve. 😄 As you can see we have more than 900 open issues and few developers, will be added but I don't know when.

Change the title to: "Wishlist: WebUI Log IP addresses of users who upload torrent". Put the words "Wishlist: WebUI" in your other issue also.

@ngosang commented on GitHub (Jun 29, 2015): qBittorrent WebUI has many things to improve. :smile: As you can see we have more than 900 open issues and few developers, will be added but I don't know when. Change the title to: "Wishlist: WebUI Log IP addresses of users who upload torrent". Put the words "Wishlist: WebUI" in your other issue also.

deekerman commented

2026-02-21 16:22:08 -05:00

Author

Owner

@sardonyxserendil commented on GitHub (Jun 30, 2015):

In the meantime, is there any logging currently going on for the webui? If it even had a apache like logfile I could grep for the POST action of the "download from urls" "download" button that would be helpful. I have some user uploading "undesirable" torrents and I'd like to figure out who it is.

@sardonyxserendil commented on GitHub (Jun 30, 2015): In the meantime, is there any logging currently going on for the webui? If it even had a apache like logfile I could grep for the POST action of the "download from urls" "download" button that would be helpful. I have some user uploading "undesirable" torrents and I'd like to figure out who it is.

deekerman commented

2026-02-21 16:22:08 -05:00

Author

Owner

@ngosang commented on GitHub (Jun 30, 2015):

#2315

@ngosang commented on GitHub (Jun 30, 2015): #2315

deekerman commented

2026-02-21 16:22:08 -05:00

Author

Owner

@sardonyxserendil commented on GitHub (Jun 30, 2015):

I merged with that code and got the web requests for those logs to work, unfortunately they don't show the IP address.

6/30/15 12:08 PM - 'magnet:?xt=urn:btih=torrent' added to download list.

This is very very close to what I need, if it only had the uploading IP address it would be perfect.

@sardonyxserendil commented on GitHub (Jun 30, 2015): I merged with that code and got the web requests for those logs to work, unfortunately they don't show the IP address. 6/30/15 12:08 PM - 'magnet:?xt=urn:btih=torrent' added to download list. This is very very close to what I need, if it only had the uploading IP address it would be perfect.

deekerman commented

2026-02-21 16:22:08 -05:00

Author

Owner

@chrishirst commented on GitHub (Jul 1, 2015):

If it even had a apache like logfile

Run Apache with the webui in an iFrame.
or
use Apache to get the IP, then redirect to the webUI port.

@chrishirst commented on GitHub (Jul 1, 2015): > If it even had a apache like logfile Run Apache with the webui in an iFrame. or use Apache to get the IP, then redirect to the webUI port.

deekerman commented

2026-02-21 16:22:08 -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.)**