qbittorrent execution log being spammed with "WebAPI login success." #7608

New issue

Closed

opened 2026-02-21 19:04:15 -05:00 by deekerman · 2 comments

deekerman commented

2026-02-21 19:04:15 -05:00

Owner

Originally created by @JourneyOver on GitHub (Aug 14, 2018).

Please provide the following information

qBittorrent version and Operating System

QBIT V: 4.1.2
OS: Win 10 x64 Pro Latest Updates

What is the problem

Upon upgrading to 4.1.2, qbittorrent logs seems to be getting spammed with WebAPI login success. IP: ::1 at various moments in time. This was not happening in earlier versions.

What is the expected behavior

For it to not spam the logs with WebAPI login success. IP: ::1 constantly.

Steps to reproduce

1 - Download NGINX and qbittorrent 4.1.2 and set them both up with QBT WebUI enabled.
2 - Look at execution log for qbittorrent and you'll see WebAPI login success. being spammed a bit.
3 - Download qbittorrent 4.1.1 and keep the configuration the same as before
3.5 - Look at execution log for qbittorrent 4.1.1 and notice that there is never a WebAPI login success. at all.

Extra info(if any)

Something obviously changed in release 4.1.2 that shows login attempts for the WebUI that was not there before in older versions of qbittorrent, idk what but seems that with the way nginx does things it seems to spam the qbittorrent logs a bit due.

This is my qbittorrent.conf file for nginx

#Qbittorrent
location /qbt/ {
	auth_request /auth-1;
	proxy_pass http://127.0.0.1:9092/; #For server-auth with Organizr, remove unless you use Organizr.
	proxy_set_header X-Forwarded-Host $server_name:$server_port;
	proxy_hide_header Referer;
	proxy_hide_header Origin;
	proxy_set_header Referer '';
	proxy_set_header Origin '';
	add_header X-Frame-Options "SAMEORIGIN";
}

Log to show how much it was spamming (had to combine two logs together due to how much it spammed):
qbittorrent.log
the (N) 2018-08-14T05:52:01 - WebAPI login success. IP: ::ffff:127.0.0.1 was of my own logging in on the webUI, the rest seem to be due to nginx.

Originally created by @JourneyOver on GitHub (Aug 14, 2018). **Please provide the following information** ### qBittorrent version and Operating System QBIT V: 4.1.2 OS: Win 10 x64 Pro Latest Updates ### What is the problem Upon upgrading to 4.1.2, qbittorrent logs seems to be getting spammed with `WebAPI login success. IP: ::1` at various moments in time. This was not happening in earlier versions. ### What is the expected behavior For it to not spam the logs with `WebAPI login success. IP: ::1` constantly. ### Steps to reproduce 1 - Download NGINX and qbittorrent 4.1.2 and set them both up with QBT WebUI enabled. 2 - Look at execution log for qbittorrent and you'll see `WebAPI login success.` being spammed a bit. 3 - Download qbittorrent 4.1.1 and keep the configuration the same as before 3.5 - Look at execution log for qbittorrent 4.1.1 and notice that there is never a `WebAPI login success.` at all. ### Extra info(if any) Something obviously changed in release 4.1.2 that shows login attempts for the WebUI that was not there before in older versions of qbittorrent, idk what but seems that with the way nginx does things it seems to spam the qbittorrent logs a bit due. This is my qbittorrent.conf file for nginx ``` #Qbittorrent location /qbt/ { auth_request /auth-1; proxy_pass http://127.0.0.1:9092/; #For server-auth with Organizr, remove unless you use Organizr. proxy_set_header X-Forwarded-Host $server_name:$server_port; proxy_hide_header Referer; proxy_hide_header Origin; proxy_set_header Referer ''; proxy_set_header Origin ''; add_header X-Frame-Options "SAMEORIGIN"; } ``` Log to show how much it was spamming (had to combine two logs together due to how much it spammed): [qbittorrent.log](https://github.com/qbittorrent/qBittorrent/files/2286794/qbittorrent.log) the `(N) 2018-08-14T05:52:01 - WebAPI login success. IP: ::ffff:127.0.0.1` was of my own logging in on the webUI, the rest seem to be due to nginx.

deekerman closed this issue

2026-02-21 19:04:19 -05:00

deekerman commented

2026-02-21 19:04:21 -05:00

Author

Owner

@lozbrown commented on GitHub (Dec 31, 2018):

@JourneyOver care to share how you resolved this

@lozbrown commented on GitHub (Dec 31, 2018): @JourneyOver care to share how you resolved this

deekerman commented

2026-02-21 19:04:21 -05:00

Author

Owner

@JourneyOver commented on GitHub (Dec 31, 2018):

@lozbrown I didn't resolve it exactly, just somewhere between QBT 4.1.3 and the latest release it stopped spamming the logs. my computer was broken the past couple of months and I just recently got my computer back up and running again, so idk what version exactly it was fixed in all I know was that when I downloaded the latest release I haven't had any spam coming in from the WebAPI like the above when running nginx.

@JourneyOver commented on GitHub (Dec 31, 2018): @lozbrown I didn't resolve it exactly, just somewhere between QBT 4.1.3 and the latest release it stopped spamming the logs. my computer was broken the past couple of months and I just recently got my computer back up and running again, so idk what version exactly it was fixed in all I know was that when I downloaded the latest release I haven't had any spam coming in from the WebAPI like the above when running nginx.