-
-
Notifications
You must be signed in to change notification settings - Fork 4.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Trackers are not contacted after VPN connection loss #15735
Comments
A case where I do experience this issue is when my VPN loses connection for a few minutes and reconnects to a different server overnight after an isp maintenance reboot of my modem. My outcome is that some of the trackers I have are listed as After doing some digging, I believe this may be related to arvidn/libtorrent#4412 as it's related to a VPN reconnect and tracker connection error afterwards. I also want to note that I tried to manually disconnect and reconnect my VPN to a new server, and it doesn't seem to happen. Looks like the DHT goes up in count in a few seconds again, as tested on 12/9/2021 and the trackers are listed as The issue happens when my internet modem is restarted / my ISP has a temporary outage for maintenance which in turn triggers a new VPN server connection attempt, as opposed to just changing servers on my VPN which doesn't seem to cause the issue for me anymore. In summary, I recommend other people try to test this to see if they experience it also during modem restart / ISP shutdown vs. VPN reconnection. |
In 4.4.0 I spotted the "Re-announce to all tracker when IP or port changed" option. |
Confirm the issue as above. Also I see that same issue was submitted many times before and was closed as "not an issue", but this is exactly an issue. Manual reannounce doesn't help. Pause-start helps, but if VPN disconnects/reconnects several times many torrents might stuck in this condition and it doesn't allow to keep unattended 24/7 operation. |
I have been using 4.4.2 for a couple of days now. The re-announce option seems to work now. |
The exact problem is resolved, but there are more problems about VPN connection and announcers that still break the unattended operation. |
To be clear, is the resolution to upgrade manually to 4.4.2, then? I experience this exact same issue, and can't just pause/resume everything all the time. I also see, like @DarkVoyage says, that it's been reported many times but inexplicably closed and locked with "just pause/resume" seemingly as the resolution. I'm not sure these kinds of issues should be self-closed, as the root problem seems to persist with stable releases (my server runs -nox 4.3.9, and it doesn't seem Ubuntu's repos have 4.4.x yet). |
Yes, tick the "Re-announce to all trackers when IP or port changed" option under the advanced section. I'm not a linux expert but there is an AppImage download on the qbittorrent homepage, created on ubuntu 20.04. |
@SaltySP Updating my server to Impish (21.10) and qbit to 4.4.x seemed to fix it. I should've looked a little closer at the zipped files available, but it seems like the last version 20.04 got (via package managers) was 4.3.9. qbittorrent-nox itself it a little different, too. .Thanks! |
This was a libtorrent bug and was fixed recently by arvidn/libtorrent#6626 |
qBittorrent & operating system versions
qBittorrent 4.3.9 x64
Windows 10 Pro 21H1/19043.1348
What is the problem?
When VPN loses connection the torrents display: "Reannounce in 68y 32d". The individual trackers display: "Not contacted yet".
This also happens when system goes into sleep mode.
Steps to reproduce
Additional context
Log(s) & preferences file(s)
No response
The text was updated successfully, but these errors were encountered: