[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]

bridge relay: "DirPort unreachable"

When I start my bridge relay on a dedicated server at home, I get this:

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.

But after a while:

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.

So I started debugging:

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.

What does this mean?

I'm familiar with NAT and my "m0n0wall" firewall shows up the
connections to port 9001/9030 of the tor-server.

Here comes my '/etc/tor/torrc':

SocksPort 0
Log notice file /var/log/tor/notices.log
DataDirectory /var/lib/tor
Nickname ***
Address ***
HiddenServiceDir /var/lib/tor/hidden_service_www/
HiddenServicePort 80
ORPort 443
DirPort 80
BridgeRelay 1
PublishServerDescriptor bridge
RelayBandwidthRate 100 KB
RelayBandwidthBurst 100 KB
ExitPolicy reject *:*
TunnelDirConns 1
PreferTunneledDirConns 1
Log debug file /var/log/tor/debug.log