Tracker errors on current version

[scott1x]

Since trying to upgrade from 1.8.5, I have been getting tracker errors in the logger screen. I have bt.enable_tracker set to true, and have some torrents that reference my computer. This is what seems to be causing the error. If I do NOT include my computer in the announce list, there are no tracker errors. If I do, there are.

Version 1.8.5 generates no errors. Do I need to change something to make this work in versions beyond 1.8.5?

TIA

[Firon]

What sort of error?

[scott1x]

The errors are:

[2010-04-27 16:58:39] Tracker reports an invalid external IP

[2010-04-27 16:58:39] Tracker reports an invalid external IP

[2010-04-27 16:58:39] Tracker reports an invalid external IP

[2010-04-27 16:58:39] Tracker reports an invalid external IP

[2010-04-27 16:58:44] Tracker reports an invalid external IP

[2010-04-27 16:58:44] Tracker reports an invalid external IP

[2010-04-27 16:58:44] Tracker reports an invalid external IP

[2010-04-27 16:58:44] Tracker reports an invalid external IP

[2010-04-27 16:58:49] Tracker reports an invalid external IP

[2010-04-27 16:58:49] Tracker reports an invalid external IP

[scott1x]

I just tried 2.0.1 build 19248 with the same results.

Any suggestions on resolving this problem would be appreciated, though 1.8.5 does seem to be working just fine.

[scott1x]

So far, the only resolution to this problem that I've found is to use 1.8.5.

Is this the only solution?

[Firon]

What do you have set in the 'ip to report to tracker' option? Is it an IP, or a hostname?

[scott1x]

I'm not sure I understand the question. When I make the torrent, I include my machine in the announce list. It is a host name. I have enable tracker set to true.

http://mydomain.net:36969/announce

The set up I'm using produces no errors in 1.8.5. Even in the later versions, which procuce errors, all seems to be function, but I can't be sure.

~~~~~~~~~~

I found the field you mentioned. I set it to my ip and logger is still showing errors. I tried my domain name with the same results.

[2010-05-03 08:29:55] *** Starting Diagnostic thread ***

[2010-05-03 08:30:05] Tracker reports an invalid external IP

[2010-05-03 08:30:05] Tracker reports an invalid external IP

[2010-05-03 08:30:05] Tracker reports an invalid external IP

[2010-05-03 08:30:05] Tracker reports an invalid external IP

[scott1x]

I have still been unable to resolve the tracker errors that I've been getting with versions above 1.8.5

I have set IP/Host name to report to tracker: to my IP number, but I notice that uTorrent is showing 0.0.0.0 on the tracker listening port. While in version 1.8.5 seem to have no problems with this, and functions fine, higher versions throw track errors.

Anyone have any suggestions???

TIA

[scott1x]

I just upgraded to 2.0.2 and am still getting the same tracker errors. So far, I've not one suggestion on a resolution to this problem, which has been on the forum since 4/27. Is there any help here?

[Switeck]

Sounds like a pretty bad bug to me, moving to the Found Bugs forum!

[scott1x]

Ok, I appreciate that. I was hoping it was something that I was doing wrong.

[Greg Hazel]

"Tracker reports an invalid external IP" does not have anything to do with the 'ip to report to tracker' option. The error message means that the response the tracker gave in the "external ip" key is invalid ( http://www.bittorrent.org/beps/bep_0024.html ).

Can you wireshark the connection to the tracker, or give us a torrent on this tracker so we can look at the traffic?

[Firon]

Greg, if you read the thread earlier, he's using the internal tracker in µTorrent (bt.enable_tracker).

[Greg Hazel]

Oh, whoops!

Well, wireshark capture of the traffic would still be useful.

[scott1x]

Sadly, I'm afraid that wireshark is something I've never used. However, I have put a small torrent that I'm now hosting on 2.0.2 if that will help....

http://catfangz.com/comics.torrent

I am hosting this small data set on my pc running 2.0.2 I'm able to receive it on my netbook with no problem. The errors that it's throwing seem to be harmless, as the file does send, but does clutter the logger. In the transmit, it has thrown some interesting errors... reproduced below.

[2010-05-14 20:03:25] *** Starting Diagnostic thread ***

[2010-05-14 20:03:39] Tracker reports an invalid external IP

[2010-05-14 20:06:12] Tracker reports an invalid external IP

[2010-05-14 20:07:47] Tracker reports an invalid external IP

[2010-05-14 20:07:55] Reporting hang diagnostic information.

[2010-05-14 20:07:55] http://www.utorrent.com/report_problem.php?v=67456192&h=joq6XdCC7XVJE-Hx&w=A280105&p=hung&s=0&li=n:1:0:main:main:0&wm=m:275:3210828:0:268906,5637850:512:0:2818442:268890,5637850:512:0:2687373:268890,5637850:512:0:2556304:268875,5637850:512:0:2490770:268875,5637850:512:0:2425235:268859,5637850:512:0:2425237:268859,5637850:512:0:2425238:268843,5637850:512:0:2359702:268843,5637850:512:0:2359703:268828,5637850:512:0:2294168:268812,5048218:275:1:0:268812,9504114:32772:0:0:268546,10422106:15:0:0:268531,4785886:15:0:0:268515,8390598:15:0:0:268515,4458262:15:0:0:268515,5637850:15:0:0:268515,7800684:15:0:0:268515,5637850:512:0:2294169:268515

[2010-05-14 20:07:57] Hang reported successfully:

[2010-05-14 20:07:57] http://www.utorrent.com/report_problem.php?v=67456192&h=joq6XdCC7XVJE-Hx&w=A280105&p=hung&s=0&li=n:1:0:main:main:0&wm=m:275:3210828:0:268906,5637850:512:0:2818442:268890,5637850:512:0:2687373:268890,5637850:512:0:2556304:268875,5637850:512:0:2490770:268875,5637850:512:0:2425235:268859,5637850:512:0:2425237:268859,5637850:512:0:2425238:268843,5637850:512:0:2359702:268843,5637850:512:0:2359703:268828,5637850:512:0:2294168:268812,5048218:275:1:0:268812,9504114:32772:0:0:268546,10422106:15:0:0:268531,4785886:15:0:0:268515,8390598:15:0:0:268515,4458262:15:0:0:268515,5637850:15:0:0:268515,7800684:15:0:0:268515,5637850:512:0:2294169:268515

[2010-05-14 20:08:05] http://www.utorrent.com/report_problem.php?v=67456192&h=joq6XdCC7XVJE-Hx&w=A280105&p=unhung

[2010-05-14 20:08:05] Hang reported successfully:

[2010-05-14 20:08:05] http://www.utorrent.com/report_problem.php?v=67456192&h=joq6XdCC7XVJE-Hx&w=A280105&p=unhung

[2010-05-14 20:08:35] Tracker reports an invalid external IP

[2010-05-14 20:11:39] Tracker reports an invalid external IP

[2010-05-14 20:12:27] Tracker reports an invalid external IP

[2010-05-14 20:13:44] Tracker reports an invalid external IP

[2010-05-14 20:22:28] Tracker reports an invalid external IP

Hope that helps.....

~~~~~~~~~~~~~~~~~~~~~~

Next Day:

I left the the seeding torrent up on 2.0.2, and I notice that it is generating an error every 10 minutes.

[Greg Hazel]

Aha! Thanks for the torrent, that pointed out the problem. Our tracker was returning IPs in regular dot notation instead of packed format.

This is fixed - thanks!

[scott1x]

Thank you for a very prompt fix! I'm impressed!

Where do I find the latest build??

[Firon]

There is no build released with this fixed. The next 2.1 will have it, and whatever the next stable-candidate release is. I don't actually know what version that will be.

[jEaseUs_]

I've the same thing on utorrent 2.0.3 Beta 20558

Does version 3 have this fixed by any chance? or any version? Or when will 2.1 be released?

Why doesn't the next build have this fixed? and why do I have to ask so many apparently annoying questions?! probably because I've no life and the ego's got me haha

First time I use the embedded tracker and added myself (as hostname) to a torrent, and on each tracker update there I get the "Tracker reports an invalid external IP" on logs, I'm not sure what damage does this do or what are the implications, maybe no peers can see me seed since the IP is returned in a different format? guessing...