Dirserver believes your ORPort is unreachable

[Eugene Armstead]

Hey,

What do I do about this???  I was using Tor 0.1.0.14 and moved to 0.1.1.6 and am still having the same problem...

Here's the logs:

Sep 12 11:24:54.444 [notice] Tor 0.1.0.14 opening log file.
Sep 12 11:24:54.445 [notice] Initialized libevent version 1.1a using method poll
Sep 12 11:24:54.467 [warn] connection_create_listener(): Could not bind to port 9001: Address already in use
Sep 12 11:24:54.467 [err] options_act(): Failed to bind one of the listener ports.
Sep 12 11:24:54.468 [err] init_from_config(): Acting on config options left us in a broken state. Dying.
Sep 12 11:25:02.046 [err] Catching signal TERM, exiting cleanly.
Sep 12 11:25:32.309 [notice] Tor 0.1.0.14 opening log file.
Sep 12 11:25:32.310 [notice] Initialized libevent version 1.1a using method poll
Sep 12 11:25:42.594 [notice] Tor has successfully opened a circuit. Looks like it's working.
Sep 12 11:25:42.594 [notice] Now checking whether ORPort and DirPort are reachable... (this may take several minutes)
Sep 12 11:25:44.047 [notice] directory_handle_command_get(): Client asked for the mirrored directory, but we don't have a good one yet. Sending 503 Dir not available.
Sep 12 11:26:02.601 [notice] Your ORPort is reachable from the outside. Excellent. Publishing server descriptor.
Sep 12 11:26:03.032 [warn] connection_dir_client_reached_eof(): http status 400 ("Dirserver believes your ORPort is unreachable") response from dirserver '86.59.5.130'. Malformed server descriptor?
Sep 12 11:26:39.707 [notice] Your DirPort is reachable from the outside. Excellent.
Sep 12 11:28:39.326 [warn] connection_dir_client_reached_eof(): http status 400 ("Dirserver believes your ORPort is unreachable") response from dirserver '86.59.5.130'. Malformed server descriptor?


Log for 0.1.1.6-alpha:

Sep 12 13:09:57.888 [notice] Tor 0.1.1.6-alpha opening log file.
Sep 12 13:09:57.926 [notice] Initialized libevent version 1.1a using method poll. Good.
Sep 12 13:09:57.949 [notice] connection_create_listener(): Opening OR listener on 216.161.59.50:9001
Sep 12 13:09:57.951 [notice] connection_create_listener(): Opening Directory listener on 0.0.0.0:9030
Sep 12 13:09:57.951 [notice] connection_create_listener(): Opening Socks listener on 127.0.0.1:9050
Sep 12 13:10:08.655 [notice] Tor has successfully opened a circuit. Looks like it's working.
Sep 12 13:10:08.655 [notice] Now checking whether ORPort 216.161.59.50:9001 and DirPort 216.161.59.50:9030 are reachable... (this may take several minutes)
Sep 12 13:10:09.814 [notice] Your ORPort is reachable from the outside. Excellent. Publishing server descriptor.
Sep 12 13:10:09.925 [notice] directory_handle_command_get(): Client asked for the mirrored directory, but we don't have a good one yet. Sending 503 Dir not available.
Sep 12 13:10:15.740 [warn] connection_dir_client_reached_eof(): http status 400 ("Dirserver believes your ORPort is unreachable") response from dirserver '86.59.5.130:80'. Malformed server descriptor?
Sep 12 13:10:30.912 [notice] Your DirPort is reachable from the outside. Excellent.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.torproject.org/pipermail/tor-talk/attachments/20050912/23b4c7c1/attachment.htm>