ANSWERED Not connecting to several bittorrent trackers

[gevero 3]

I have issues connecting to several bittorrent trackers, using Virginis Server. Some of the trackers are:

 

http://tracker.publichd.eu/announce

udp://tracker.1337x.org:80/announce

http://tracker.openbittorrent.com/announce

http://tracker.publicbt.com/announce

 

and also others...

 

only 

 

http://fr33dom.h33t.com:3310/announce and http://exodus.desync.com/announce seem to be working

 

The error message from transmission is "Connection failed", "Could not connect to tracker"

 

Best Regards

[Staff 10334]

Hello!

 

Thank you for the information.

 

We need to investigate and check. In the meantime enable DHT+PEX, you really don't need trackers.

 

Kind regards

[gevero 3]

DHT and PEX are enable and are a partial solution. 

 

Best Regards

[Staff 10334]

DHT and PEX are enable and are a partial solution. 

 

Best Regards

 

Hi,

 

why "partial"?

 

Kind regards

[gevero 3]

Probably I am mistaken but it was my understanding that I would get more peers with a Tracker+DHT+PEX configuration than with a DHT+PEX only configuration

 

Best Regards

[Staff 10334]

Hello,

 

no, don't worry. Torrent trackers are anyway useful for private services who need to quickly gather statistics and IP addresses (including copyright enforcement agencies - we remind you that such usage is strictly forbidden on our service according to the ToS), restrict the service according to seed/leech ratios, restrict the service to members and similar cases.

 

Kind regards

[gevero 3]

Ok, perfect, please keep me updated when you get some news

 

Best regards

[gevero 3]

Brief update. Now I can connect to no tracker at all...this is a bit annoying.

 

Best Regards

[Staff 10334]

Hello,

 

first of all you should take note that the first three trackers you cite are no more working in http since a long ago, they only work in udp (for a very good reason). Actually, apart from the fact that using a tracker does not make any sense except for very special needs, there is not much sense in running an http tracker, due to efficiency reasons.

 

We have checked the three trackers you reported as non-working in your first message right now (BUT in udp, of course) and we confirm they are perfectly reachable and working from Virginis.

 

About "fr33dom" we don't know if it's still available in http, anyway an udp check was fully successful. It might be that the tracker is temporarily unavailable in http, or maybe it does not support http anymore, we don't know.

 

The problem is therefore non-existent, we mark this thread solved but do not hesitate to contact us for any further information or issue.

 

Kind regards