Web UI becomes unresponsive after network interruptions and requires manual restart #17101

Open
opened 2026-02-22 03:40:26 -05:00 by deekerman · 7 comments
Owner

Originally created by @QuixThe2nd on GitHub (Aug 23, 2025).

qBittorrent & operating system versions

qBittorrent 5.0.5 - MacOS

What is the problem?

After brief network interruptions, the Web UI becomes unresponsive, requiring me to manually toggle the Web UI off then back on.

Multiple services go down (e.g. IRC, remote screen control, etc) including qBittorrents Web UI.
However once my router recovers and my ISP assigns a new IP, everything that failed gracefully recovers except qBittorrents Web UI.

Steps to reproduce

  1. Enable qBittorrent's Web UI
  2. Simulate brief network interruption (e.g. unplug router from modem)
  3. Recover the network
  4. Access qBittorrent's Web UI
  5. Disable/re-enable Web UI and it will become accessible again

Additional context

Specifically, my router faces a PPP failure:

# Timestamp Type Level Message
1 2025-08-24 00:43:23 PPP Error ppp3
2 2025-08-24 00:43:03 PPP Error ppp2
3 2025-08-24 00:43:03 PPP Error ppp2 LCP down
4 2025-08-24 00:43:03 PPP Error ppp2 Peer not responding

Log(s) & preferences file(s)

qBittorrent logs:

// Everythings working
(N) 2025-08-24T00:42:42 - WebAPI login success. IP: ::ffff:192.168.1.2

// IP Changes - see router logs above
(I) 2025-08-24T00:43:36 - Detected external IP. IP: "xxx.xxx.xxx.xxx"

// Manual restart
(N) 2025-08-24T00:45:07 - Options saved.
(N) 2025-08-24T00:45:09 - Options saved.
(N) 2025-08-24T00:45:09 - Using custom WebUI. Location: "/Users/parsa/Library/Application Support/qBittorrent/themes_web/dracula/webui".
(W) 2025-08-24T00:45:09 - Couldn't load WebUI translation for selected locale (en_AU).

// Everything working again
(N) 2025-08-24T00:45:09 - WebUI: Now listening on IP: *, port: 8090
(N) 2025-08-24T00:45:09 - WebAPI login success. IP: ::ffff:127.0.0.1
(N) 2025-08-24T00:45:41 - WebAPI login success. IP: ::ffff:127.0.0.1
(N) 2025-08-24T00:45:42 - WebAPI login success. IP: ::ffff:192.168.1.2
(N) 2025-08-24T00:45:49 - WebAPI login success. IP: ::1
Originally created by @QuixThe2nd on GitHub (Aug 23, 2025). ### qBittorrent & operating system versions qBittorrent 5.0.5 - MacOS ### What is the problem? After brief network interruptions, the Web UI becomes unresponsive, requiring me to manually toggle the Web UI off then back on. Multiple services go down (e.g. IRC, remote screen control, etc) including qBittorrents Web UI. However once my router recovers and my ISP assigns a new IP, everything that failed gracefully recovers except qBittorrents Web UI. ### Steps to reproduce 1. Enable qBittorrent's Web UI 2. Simulate brief network interruption (e.g. unplug router from modem) 3. Recover the network 4. Access qBittorrent's Web UI 5. Disable/re-enable Web UI and it will become accessible again ### Additional context Specifically, my router faces a PPP failure: | # | Timestamp | Type | Level | Message | | -- | -- | -- | -- | -- | | 1 | 2025-08-24 00:43:23 | PPP | Error | ppp3 | | 2 | 2025-08-24 00:43:03 | PPP | Error | ppp2 | | 3 | 2025-08-24 00:43:03 | PPP | Error | ppp2 LCP down | | 4 | 2025-08-24 00:43:03 | PPP | Error | ppp2 Peer not responding | ### Log(s) & preferences file(s) qBittorrent logs: ``` // Everythings working (N) 2025-08-24T00:42:42 - WebAPI login success. IP: ::ffff:192.168.1.2 // IP Changes - see router logs above (I) 2025-08-24T00:43:36 - Detected external IP. IP: "xxx.xxx.xxx.xxx" // Manual restart (N) 2025-08-24T00:45:07 - Options saved. (N) 2025-08-24T00:45:09 - Options saved. (N) 2025-08-24T00:45:09 - Using custom WebUI. Location: "/Users/parsa/Library/Application Support/qBittorrent/themes_web/dracula/webui". (W) 2025-08-24T00:45:09 - Couldn't load WebUI translation for selected locale (en_AU). // Everything working again (N) 2025-08-24T00:45:09 - WebUI: Now listening on IP: *, port: 8090 (N) 2025-08-24T00:45:09 - WebAPI login success. IP: ::ffff:127.0.0.1 (N) 2025-08-24T00:45:41 - WebAPI login success. IP: ::ffff:127.0.0.1 (N) 2025-08-24T00:45:42 - WebAPI login success. IP: ::ffff:192.168.1.2 (N) 2025-08-24T00:45:49 - WebAPI login success. IP: ::1 ```
Author
Owner

@olliegg123 commented on GitHub (Aug 31, 2025):

Seeing this same issue on my instance too - also after a system reboot I have to do the manual toggle off and on.

@olliegg123 commented on GitHub (Aug 31, 2025): Seeing this same issue on my instance too - also after a system reboot I have to do the manual toggle off and on.
Author
Owner

@QuixThe2nd commented on GitHub (Aug 31, 2025):

Seeing this same issue on my instance too - also after a system reboot I have to do the manual toggle off and on.

What OS are you on? I wonder if this is Mac specific.

@QuixThe2nd commented on GitHub (Aug 31, 2025): > Seeing this same issue on my instance too - also after a system reboot I have to do the manual toggle off and on. What OS are you on? I wonder if this is Mac specific.
Author
Owner

@olliegg123 commented on GitHub (Aug 31, 2025):

Also on Mac OS

@olliegg123 commented on GitHub (Aug 31, 2025): Also on Mac OS
Author
Owner

@QuixThe2nd commented on GitHub (Sep 24, 2025):

I ended up migrating to running qBittorrent on Debian (with identical config) and I can confirm I no longer face this issue, qBittorrent still listens even after network failures.

@QuixThe2nd commented on GitHub (Sep 24, 2025): I ended up migrating to running qBittorrent on Debian (with identical config) and I can confirm I no longer face this issue, qBittorrent still listens even after network failures.
Author
Owner

@xavier2k6 commented on GitHub (Sep 24, 2025):

What version of macOS?, What browser/version?

@xavier2k6 commented on GitHub (Sep 24, 2025): What version of macOS?, What browser/version?
Author
Owner

@QuixThe2nd commented on GitHub (Sep 24, 2025):

MacOS 15.0. Browser is irrelevant, qBittorrent simply doesn't listen on the WebUI port.

@QuixThe2nd commented on GitHub (Sep 24, 2025): MacOS 15.0. Browser is irrelevant, qBittorrent simply doesn't listen on the WebUI port.
Author
Owner

@QuixThe2nd commented on GitHub (Dec 5, 2025):

That PR doesn't solve this issue. The problem is that when the network fails, the HTTP server stops listening on port 8080. Changes to the frontend can't address it.

@QuixThe2nd commented on GitHub (Dec 5, 2025): That PR doesn't solve this issue. The problem is that when the network fails, the HTTP server stops listening on port 8080. Changes to the frontend can't address it.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/qBittorrent#17101
No description provided.