mirror of
https://github.com/qbittorrent/qBittorrent.git
synced 2026-03-02 22:57:32 -05:00
permanent connection loss after network reconnection #14946
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#14946
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 @snakeeater98 on GitHub (Sep 7, 2023).
qBittorrent & operating system versions
qBittorrent: 4.5.5
Operating system: QTS 5.1.1.2491
Qt: 6.5.2
Libtorrent: 2.0.9.0
What is the problem?
Whenever my ISP reconnects and VPN therefore as well, qBittorrent does not pick up the new connection.
As Network interface I set my VPN nic and for addresses to bind i used all ipv4 addresses
Steps to reproduce
setup a VPN
configure qbittorrent to use the vpn interface
disconnect from network
connect to network
result -> connection in qbittorrent is permanetly lost
Additional context
No response
Log(s) & preferences file(s)
Edit: i took the logs before enabling the option "Reannounce to all trackers when IP or port changed", it changed nothing.
Also manual "force reannounce" does nothing as well.
@DarkVoyage commented on GitHub (Sep 12, 2023):
Maybe has connection to #16901, #16947, #18488
@DarkVoyage commented on GitHub (Sep 12, 2023):
There should be some kind of timeout and cyclical retouch of connection in case it was dead at time of first probe. In fact I've had a problem with Windows VPN (ikev2), but have no problem with SoftEther, qB connects right away, when connection on adapter is alive.
@DeathStalker77 commented on GitHub (Sep 12, 2023):
I have noticed this as well, after upgrading to v4.5x and now to v4.6.0RC2 - if you lose VPN connection, qB does NOT reconnect or re-announce upon re-connection - NOR does manually re-announcing. I have had to close the program and relaunch it.
--- DS
@snakeeater98 commented on GitHub (Sep 29, 2023):
so, what can i do to help with the issue ? what does needs diagnosis mean ?
@luzpaz commented on GitHub (Oct 15, 2023):
@snakeeater98 help debug the issue, or convince someone who has those skills to debug it?
@snakeeater98 commented on GitHub (Nov 9, 2023):
After following multiple paths to possible solutions i finally think i found out what works for me.
Its more like a workaround than a clean solution.
I just made a script that restarted the qBittorrent service and execute it via crontab every 20 min.
If anyone is interested, for qnap qts os the command is "nohup qpkg_service restart qbittorrent 1>>/dev/null 2>>/dev/null".
(not sure if nohup is required but if yes it comes with the entware-std app from the appstore repository myqnap)
EDIT: THIS IS NOT A SOLUTION, because when restarting the service qbittorrent does not save the downloaded progress...
EDIT2: ... set "Save resume data interval" in qbittorrent to a low value.
@luzpaz commented on GitHub (Nov 13, 2023):
This is another ticket that is a good candidate for increasing log level for network info