All trackers stuck at Not Contacted Yet

[B00ze64]

qBittorrent & operating system versions

qBT: 4.4 x64
Win7 64 bits

What is the problem?

Any torrent I try to download never starts, all the trackers are stuck at "Not Contacted Yet" and there is no obvious error in the log.

Steps to reproduce

I download a .torrent and start it, simple as that, tried https://ubuntu.com/download/alternative-downloads

Additional context

No response

Log(s) & preferences file(s)

2022-01-16 02:40 - qBittorrent v4.4.0 started
2022-01-16 02:40 - 'ubuntu-21.10-desktop-amd64.iso' restored.
2022-01-16 02:40 - Failed to listen on IP: 169.254.189.140, port: TCP/30570. Reason: The requested address is not valid in its context
2022-01-16 02:40 - IP geolocation database loaded. Type: DBIP-Country-Lite. Build time: Fri Dec 31 20:11:53 2021.
2022-01-16 02:40 - Encryption support [FORCED]
2022-01-16 02:40 - Anonymous mode [ON]
2022-01-16 02:40 - PeX support [ON]
2022-01-16 02:40 - Local Peer Discovery support [OFF]
2022-01-16 02:40 - DHT support [ON]
2022-01-16 02:40 - HTTP User-Agent is 'qBittorrent/4.4.0'
2022-01-16 02:40 - Peer ID: -qB4400-
2022-01-16 02:40 - Trying to listen on: {B3602CD4-30E3-4310-BE53-CE80ED7C2C5C}:30570
2022-01-16 02:40 - Using config directory: C:/Users/B00ze/AppData/Roaming/qBittorrent

qBittorrent.ini.zip

[ghost]

You have selected an invalid network interface. Change it from settings.

[glassez]

Encryption support [FORCED]

This can be the cause. Try to disable encryption or at least don't force it.

[B00ze64]

You have selected an invalid network interface. Change it from settings.

Ah! That's it! I did not remember selecting the VPN adapter in the Advanced Settings, so when I looked for a cause I just did not notice this. I have indeed changed the network adapter for the VPN. Thank you much!

Regards,

[DarkVoyage]

The problem with Not Contacted Yet was opened several times and it is an issue. When you lose connection to VPN, after reconnect many torrents can't automatically update and need additional kick to resume. Encryption setting doesn't affect this problem and should not. Encryption should always be set to forced.
The last one open is #15735

"Failed to listen on IP: ...: - this error is caused, because qB tries to reach VPN at exact IP, if you set Advanced > Optional IP address to bind to > All addresses - the error doesn't appear. I doubt this solves the problem, just removes the error, because in fact you can't listen on VPN IP, if it is disconnected.

[ghost]

The problem with Not Contacted Yet was opened several times and it is an issue. When you lose connection to VPN, after reconnect many torrents can't automatically update and need additional kick to resume.

This has been fixed in latest libtorrent. So the next qBt update should fix it.

[B00ze64]

Arguably there is this "Failed to listen on IP: 169.254.189.140" in the log (APIPA) but I ignored it because I block listening anyway, as the VPN has no port forwarding. And since there was no outbound error, I was perplexed. I now see that when things are working correctly, there is a "Detected external IP" line in the log, which was missing from my log. I'll pay more attention next time. Thanks again.