nordvpn, openvpn, torrents losing their trackers, unable to seed, constantly changing IP & log is flooded with error

[Kylar514]

Its quite weird. I think its a openvpn issue. I do plan to switch over to nordlynx (nords wireguard protocall), but I need to get linux up on my PC to do that (thats planned for later this week).

All my current torrents use the same single private tracker. I added them, and the files that had already been downloaded. Ran a force check, and they were able to check the data. Then they lose their tracker, and basically just sit there and do nothing. If I examine my connections on my private tracker, I can see that most of my torrents are not seeding, and it some torrents that are downloading have multiple IP's associated... I eventually get blocked for downloading from multiple locations and have to clear ghost IP's.

qbittorrent logs are flooded with this message.

2023-04-01 15:19:00 AEAD Decrypt error: bad packet ID (may be a replay): [ #61217885 ] -- see the man page entry for --no-replay and --replay-window for more info or silence this warning with --mute-replay-warnings

2023-04-01 15:19:00 AEAD Decrypt error: bad packet ID (may be a replay): [ #61217886 ] -- see the man page entry for --no-replay and --replay-window for more info or silence this warning with --mute-replay-warnings

2023-04-01 15:19:00 AEAD Decrypt error: bad packet ID (may be a replay): [ #61217887 ] -- see the man page entry for --no-replay and --replay-window for more info or silence this warning with --mute-replay-warnings

2023-04-01 15:19:00 AEAD Decrypt error: bad packet ID (may be a replay): [ #61217888 ] -- see the man page entry for --no-replay and --replay-window for more info or silence this warning with --mute-replay-warnings

2023-04-01 15:19:00 AEAD Decrypt error: bad packet ID (may be a replay): [ #61217889 ] -- see the man page entry for --no-replay and --replay-window for more info or silence this warning with --mute-replay-warnings

2023-04-01 15:19:00 AEAD Decrypt error: bad packet ID (may be a replay): [ #61217890 ] -- see the man page entry for --no-replay and --replay-window for more info or silence this warning with --mute-replay-warnings

2023-04-01 15:19:00 AEAD Decrypt error: bad packet ID (may be a replay): [ #61217892 ] -- see the man page entry for --no-replay and --replay-window for more info or silence this warning with --mute-replay-warnings

2023-04-01 15:19:00 AEAD Decrypt error: bad packet ID (may be a replay): [ #61217893 ] -- see the man page entry for --no-replay and --replay-window for more info or silence this warning with --mute-replay-warnings

2023-04-01 15:19:00 AEAD Decrypt error: bad packet ID (may be a replay): [ #61217894 ] -- see the man page entry for --no-replay and --replay-window for more info or silence this warning with --mute-replay-warnings

I can't say whether or not the tracker issue is related. However I can say, manually adding all of the trackers has momentarily resolved the issue, we will see if it stays this way....

As for the error in the logs, this is resolved by simply reseting the container. It will work as intended for a while.

[DyonR]

It's hard for me too say what causes this, mainly because I can't reproduce it.
It is definitely caused by OpenVPN, no doubt about that.
The OpenVPN config that I use for my container does havt the mute-replay-warnings added to the .ovpn.
You're also saying that you are seeding with multiple IPs? That sounds practically impossible. One VPN tunnel can only carry traffic for 1 IP, as far as I know. Maybe your tracker remembers the previous IPs and if the connection drops, the container restarts and gets a new IP (that's how VPNs work), if that happens often and that might be why your provider thinks that.

OpenVPN also performs worse than a WireGuard setup. Even though I would like to help or solve this, I believe it's caused by either the tracker, VPN provider, or perhaps your connection, which I can't do a lot about.

[Kylar514]

You're also saying that you are seeding with multiple IPs?

Well the tracker is seeing multiple IP's, and that is just because I believe my VPN is changing IP's so frequently, creating ghost peers.... or atleast it was? The chronic IP switching seems to be resolved. But the logs are still flooded with the error. I suppose disabling the error like you did, or using wireguard would solve it. idk why though tbh. I still intend to run wireguard. Got my main pc running linux now. I know its some other thing I have to figure out about extracting the conf frile from nordlynx.

As for the problem with trackers, all my torrents not seeing the trackers. I believe that was a totally unrelated issue. I went back and manually added the trackers to each of my torrents, and that seemed to resolve this issue. I believe this happened thanks to importing all of the torrents from my appdata folder in windows.