Well, that's weird. And it only happens with BiglyBT? If you can send me some .torrent files that trigger this error, I'll have a look. I won't use your passkey, I only want to see what's going on at the TCP level.
"I just remembered something that happened a long time ago."
YGG torrents works but with other client emulation. I didn't try without perfect spoof so this might be an issue.
Unfortunately, I can't reproduce this problem either.
I didn't load the torrent as-is in my client to avoid endangering your account, but replacing the passkey with a dummy value resulted in a 404 error, which means connection to the tracker itself is working fine. And they don't use or even support HTTPS, so a bad setup or zero cipher overlap is not a factor either. My guess is that there's bad routing between you and their server, or maybe your ISP blocks them.Code:Nmap scan report for connect.p2p-tracker.net (31.220.2.198) Host is up, received user-set (0.045s latency). rDNS record for 31.220.2.198: discoveryplanets.com PORT STATE SERVICE REASON VERSION 8080/tcp open http syn-ack ttl 57 XBT BitTorrent tracker http interface
"I just remembered something that happened a long time ago."
I doubt that it is blocked, cause with clean qBittorrent or uTorrent Serenity it is ok. It doesn't work with uTorrent Leecher Mod too. I don't really know what to check
Bookmarks