UDP torrent trackers not working

[marcmv1 1]

Hi,

 

I'm on Fedora 25 and using qbittorrent. 

 

I have access to AirVPN and IPVanish. When I download torrents from rarbg, the trackers are trackerfix.com:80 udp:rarbg.to:2710 and udp:rarbg.me:2710

 

The UDP torrent trackers are working fine when connected to IPV however when connected to AirVPN qbittorrent says "Not Working". In addition, trackerfix.com is unreachable from AirVPN but reachable when I'm not connected.

 

The same behavior is present in Dallas and Chicago AirVPN servers.

 

 

From AirVPN

 

nc -v -z -u 9.rarbg.to 2710         

Ncat: Version 7.40 ( https://nmap.org/ncat )

Ncat: Connected to 151.80.120.115:2710.

Ncat: UDP packet sent successfully

Ncat: 1 bytes sent, 0 bytes received in 2.03 seconds

 

nc -v -z -u 9.rarbg.me 2710

Ncat: Version 7.40 ( https://nmap.org/ncat )

Ncat: Connected to 151.80.120.113:2710.

Ncat: UDP packet sent successfully

Ncat: 1 bytes sent, 0 bytes received in 2.32 seconds.

 

[root@tigger ~/rdp]# nc -v -z tracker.trackerfix.com 80   

Ncat: Version 7.40 ( https://nmap.org/ncat )

Ncat: Connection to 5.39.105.100 failed: Connection timed out.

Ncat: Trying next address...

Ncat: Connection to 5.39.105.102 failed: Connection timed out.

Ncat: Trying next address...

Ncat: Connection timed out.

 

From not AirVPN

 

nc -v -z tracker.trackerfix.com 80

Ncat: Version 7.40 ( https://nmap.org/ncat )

Ncat: Connected to 5.39.105.101:80.

Ncat: 0 bytes sent, 0 bytes received in 0.32 seconds.

 

nc -v -z -u 9.rarbg.to 2710

Ncat: Version 7.40 ( https://nmap.org/ncat )

Ncat: Connected to 151.80.120.113:2710.

Ncat: UDP packet sent successfully

Ncat: 1 bytes sent, 0 bytes received in 2.35 seconds.

 

nc -v -z -u 9.rarbg.me 2710

Ncat: Version 7.40 ( https://nmap.org/ncat )

Ncat: Connected to 151.80.120.113:2710.

Ncat: UDP packet sent successfully

Ncat: 1 bytes sent, 0 bytes received in 2.10 seconds.

 

[nick75 25]

Hi,

 

The likeliest answer is that the administrators have decided to ban those servers.

[go558a83nk 364]

Hi,

 

The likeliest answer is that the administrators have decided to ban those servers.

 

you may need to clarify your statement.

 

Air doesn't block or ban anything.  What happens is the trackers block the VPN servers.  Some Air servers have access, some don't.  So, it's the trackers blocking selectively. 

[Whisperer 2]

Apologize for awakening an old topic, but the alternative is to start a duplicate one. I have the exact same issue. Of the (currently) 23 servers on NewTrackon, only the http-trackers are able to be queried. All UDP trackers report "Could not connect to tracker"

Without the VPN tunnel, all but 2 of them work just fine.

Many of these trackers respond to ICMP (ping), so the AirVPN server-IP is not blocked, at least not unconditionally.

[123456seven 0]

Seeing the same issue: udp trackers blocked.  Any solution?

[OlDirty 0]

I'm seeing the exact same problem since about a week... Is anyone else having this issue as well?

I've tried with 2 Dutch server and a random Roemenian server. If someone is not having this issue, can you please say which server you're using?

Thanks!

[OpenSourcerer 1441]

For everyone in the future: Open your own thread, give as much info as you can, possibly the same way as OP in this thread. Don't forget logs of OpenVPN/Eddie, of your torrent client, etc.

Also note that many public trackers outright ban IPs, networks, and even whole AS numbers of VPN servers and known VPN server ISPs/datacenters from accessing them. Could be another factor.