summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorRoger Dingledine <arma@torproject.org>2005-12-08 21:17:33 +0000
committerRoger Dingledine <arma@torproject.org>2005-12-08 21:17:33 +0000
commit1974e6c529c8272dcea95ee11a2c347321e237d6 (patch)
treef75b4113c76d64325fa7747d69e01a9cbd82c901
parent87301909147c8fd8124d0b7bbd6393458298d79b (diff)
downloadtor-1974e6c529c8272dcea95ee11a2c347321e237d6.tar.gz
tor-1974e6c529c8272dcea95ee11a2c347321e237d6.zip
make it clearer in the docs what to expect when testing reachability.
svn:r5539
-rw-r--r--doc/tor-doc-server.html7
1 files changed, 5 insertions, 2 deletions
diff --git a/doc/tor-doc-server.html b/doc/tor-doc-server.html
index d69d2048d3..c6f1ab33b4 100644
--- a/doc/tor-doc-server.html
+++ b/doc/tor-doc-server.html
@@ -165,8 +165,11 @@ where new development releases are announced.
<p>As soon as your server manages to connect to the network, it will
try to determine whether the ports you configured are reachable from
-the outside. This may take several minutes. The log entries will keep
-you informed of its progress.</p>
+the outside. This may take up to 20 minutes. Look for a log entry like
+<tt>Self-testing indicates your ORPort is reachable from the outside. Excellent.</tt>. If you don't see this message, it means that your server is not reachable
+from the outside -- you should re-check your firewalls, check that it's
+testing the IP and port you think it should be testing, etc.
+</p>
<p>When it decides that it's reachable, it will upload a "server
descriptor" to the directories. This will let clients know