Re: bridge relay: "DirPort unreachable"

[Roger Dingledine <arma@xxxxxxx>]

On Sat, May 31, 2008 at 12:57:44PM +0200, Gitano wrote:
> When I start my bridge relay on a dedicated server at home, I get this:
> 
> ---><8
> May 31 11:34:28.207 [notice] Self-testing indicates your ORPort is
> reachable from the outside. Excellent. Publishing server descriptor.
> May 31 11:35:37.485 [notice] Performing bandwidth self-test...done.
> ---><8

Great.

> But after a while:
> 
> ---><8
> May 31 11:53:47.477 [warn] Your server (*.*.*.*:80) has not managed to
> confirm that its DirPort is reachable. Please check your firewalls,
> ports, address, /etc/hosts file, etc.
> ---><8

Are you running something else on port 80? Like, say, a webserver?

> So I started debugging:
> 
> ---><8
> May 31 11:53:23.284 [debug] connection_dir_client_reached_eof():
> Received response from directory server '*.*.*.*:80': 404 "Not found"
> May 31 11:53:23.285 [info] connection_dir_client_reached_eof(): Received
> server info (size 0) from server '*.*.*.*:80'
> May 31 11:53:23.285 [info] connection_dir_client_reached_eof(): Received
> http status code 404 ("Not found") from server '*.*.*.*:80' while
> fetching "/tor/server/authority.z". I'll try again soon.
> ---><8
> 
> What does this mean?

It means your Tor client tried to do a self-test on its advertised DirPort
(port 80 of whatever Address you're advertising), and it didn't get an
answer it expected. Perhaps something else is listening there instead?

--Roger