Skip to content
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

Closed
SaltySP opened this issue Nov 13, 2021 · 9 comments
Closed

Trackers are not contacted after VPN connection loss #15735

SaltySP opened this issue Nov 13, 2021 · 9 comments
Labels
Libtorrent Proxy/VPN Issues related to the use of proxy/VPN

Comments

@SaltySP
Copy link

SaltySP commented Nov 13, 2021

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.
image
image

Steps to reproduce

  1. Run Qbit with a VPN with Wireguard, network interface set in Qbit.
  2. Disconnect the VPN
  3. Reconnect VPN
  4. Monitor torrent status

Additional context

image

Log(s) & preferences file(s)

No response

@thalieht thalieht added the Proxy/VPN Issues related to the use of proxy/VPN label Nov 13, 2021
@gothicserpent
Copy link

gothicserpent commented Dec 9, 2021

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 not contacted yet with general -> transfer -> reannounce in: 68y 20d, while some of the others are marked as Updating and do end up re-connecting and working properly. Whenever I notice a spike in the number of "Error" trackers on the left pane, that's my cue to do the following: I have been solving the issue by pausing all torrents and resuming all torrents, and that always resolves the issue for me.

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 working.

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.

@SaltySP
Copy link
Author

SaltySP commented Jan 11, 2022

In 4.4.0 I spotted the "Re-announce to all tracker when IP or port changed" option.
Unfortunately this also doesn't work and trackers stay in the "Not contacted yet" state.

@DarkVoyage
Copy link

DarkVoyage commented Jan 12, 2022

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.

@SaltySP
Copy link
Author

SaltySP commented Apr 16, 2022

I have been using 4.4.2 for a couple of days now. The re-announce option seems to work now.
I would like everybody else to check if the problem is gone for them too. I would like to close this thread if the problem is solved.

@DarkVoyage
Copy link

The exact problem is resolved, but there are more problems about VPN connection and announcers that still break the unattended operation.

@SaltySP SaltySP closed this as completed Apr 20, 2022
@kpupp
Copy link

kpupp commented May 8, 2022

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).

@SaltySP
Copy link
Author

SaltySP commented May 8, 2022

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.

@kpupp
Copy link

kpupp commented May 8, 2022

@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!

@ghost
Copy link

ghost commented May 12, 2022

This was a libtorrent bug and was fixed recently by arvidn/libtorrent#6626

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Libtorrent Proxy/VPN Issues related to the use of proxy/VPN
Projects
None yet
Development

No branches or pull requests

5 participants