I’m using BiglyBT extreme mod. The extreme mod settings I use is this:
Attachment 21045
These GhostLeech settings always worked on YGGtorrent that’s a Semi-Private tracker
Printable View
I’m using BiglyBT extreme mod. The extreme mod settings I use is this:
Attachment 21045
These GhostLeech settings always worked on YGGtorrent that’s a Semi-Private tracker
Is it still working for you on YGG ?
My torrent doesn't even start
Why not? What's the error message from/for the tracker in the Sources tab?Quote:
Originally Posted by repulse
Error connection timeoutQuote:
Originally Posted by anon
Only with YGGtorrent
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.
It happens with uTorrent 3.x tooQuote:
Originally Posted by anon
There you go for the .torrent : removed
YGG torrents works but with other client emulation. I didn't try without perfect spoof so this might be an issue.
What client did you set for emulation ?
tested uTorrent, qbittorrent & deluge. Multiple versions tried.Quote:
Originally Posted by repulse
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 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
Moved this discussion to a separate thread and cleaned it up a little.
Me neither. Does their client whitelist (if any) allow the ones you're having this problem with?Quote:
Originally Posted by repulse
For me it’s still working with my previous posted settings with current BiglyBT Extreme Mod 2.7.0.2. Successfully tested with both perfect spoof disabled and enabled.
Attachment 21048
Attachment 21049
Attachment 21050