Re: bridge relay: "DirPort unreachable"

[Gitano <0xb8968b9e9190@xxxxxxxxxxxxxx>]

Roger Dingledine wrote:

>> ---><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?

In the meantime I set up a new bridge relay on another computer with the
same configuration except 'DirPort 9030'! No other application is
listening on that port but the result is the same:

---><8
Jun 01 22:06:46.798 [info] connection_dir_client_reached_eof(): Received
server info (size 0) from server '*.*.*.*:9030'
Jun 01 22:06:46.798 [info] connection_dir_client_reached_eof(): Received
http status code 404 ("Not found") from server '*.*.*.*:9030' while
fetching "/tor/server/authority.z". I'll try again soon.
Jun 01 22:06:46.798 [info] _connection_free(): Freeing linked Directory
connection [client finished] with 0 bytes on inbuf, 0 on outbuf.
Jun 01 22:07:27.325 [warn] Your server (*.*.*.*:9030) has not managed to
confirm that its DirPort is reachable. Please check your firewalls,
ports, address, /etc/hosts file, etc.
---><8

Any other hint? What about the missing file "/tor/server/authority.z"?