Opened 14 years ago

Last modified 7 years ago

#166 closed defect (Not a bug)

Tor apparently not publishing itself in directory

Reported by: itaintworkin Owned by:
Priority: Low Milestone:
Component: Core Tor/Tor Version:
Severity: Keywords:
Cc: itaintworkin Actual Points:
Parent ID: Points:
Reviewer: Sponsor:

Description

So in 0.1.0.11 I'm running a server on OS X 10.3.9 and curiously, this server never seems to show up in the current directory although it apparently is being found and used.

The only time this box showed up was for the hour or so that it was booted into Ubuntu Linux and I'd installed a much older version of Tor to see how it would run. THAT one published. But the one that's been running the other 23 or so hours on either side of it on OS X....not a peep.

So I'm wondering if there is some way to inadvertently disable that via mucking about in torrc that I should fix. Any ideas? Does it matter? Seems to me that it would matter.

(The server nickname that did publish was "maidenhair" as you can still find in the directory. But when it was going by that nick on OS X nothing and now that I've changed the nick to "denali" (partly to see if there was a directory problem)...nothing. No denali in the directory. :-(

[Automatically added by flyspray2trac: Operating System: OSX 10.4 Tiger]

Child Tickets

Change History (4)

comment:1 Changed 14 years ago by arma

Look in your logs. Does it give any hints?

My guess is that your server is trying to verify its reachability, and it is concluding your ports
are not reachable (e.g. you've got a firewall up). Your logs will provide details of what IP:port
your server thinks it is.

comment:2 Changed 14 years ago by arma

denali is now up and running on the outside of its firewall, so I'm going to call this one closed.

comment:3 Changed 14 years ago by arma

flyspray2trac: bug closed.

comment:4 Changed 7 years ago by nickm

Component: Tor RelayTor
Note: See TracTickets for help on using tickets.