mirror of
https://github.com/qbittorrent/qBittorrent.git
synced 2026-03-02 22:57:32 -05:00
Web UI becomes unresponsive after network interruptions and requires manual restart #17101
Labels
No labels
Accessibility
AppImage
Bounty
Build system
CI
Can't reproduce
Code cleanup
Confirmed bug
Confirmed bug
Core
Crash
Data loss
Discussion
Docker
Documentation
Duplicate
Feature
Feature request
Feature request
Feature request
Filters
Flatpak
GUI
Has workaround
I2P
Invalid
Libtorrent
Look and feel
Meta
NSIS
Network
Not an issue
OS: *BSD
OS: Linux
OS: Windows
OS: macOS
PPA
Performance
Project management
Proxy/VPN
Qt bugs
Qt6 compat
RSS
Search engine
Security
Temp folder
Themes
Translations
Triggers
Waiting diagnosis
Waiting info
Waiting upstream
Waiting web implementation
Watched folders
WebAPI
WebUI
autoCloseOldIssue
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/qBittorrent#17101
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
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
Additional context
Specifically, my router faces a PPP failure:
Log(s) & preferences file(s)
qBittorrent logs:
@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.
@QuixThe2nd commented on GitHub (Aug 31, 2025):
What OS are you on? I wonder if this is Mac specific.
@olliegg123 commented on GitHub (Aug 31, 2025):
Also on Mac OS
@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.
@xavier2k6 commented on GitHub (Sep 24, 2025):
What version of macOS?, What browser/version?
@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 (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.