diff --git a/installer/resources/readme/readme.html b/installer/resources/readme/readme.html index 61329ca7a..89391f2ee 100644 --- a/installer/resources/readme/readme.html +++ b/installer/resources/readme/readme.html @@ -22,20 +22,21 @@ up, you can:
- tell your browser to use the HTTP proxy at 127.0.0.1 port 4444, then browse to an eepsite:We've bundled some software to let you run your own eepsite - a Jetty - instance listening on http://127.0.0.1:7658/. +
We've bundled some software to let you run your own eepsite - a Jetty
+ instance listening on http://127.0.0.1:7658/.
Simply place your files in the eepsite/docroot/
directory (or place
any standard JSP/Servlet .war
files under eepsite/webapps
,
or standard CGI script under eepsite/cgi-bin
) and they'll show
- up. After starting up an eepsite tunnel pointing at
+ up. After starting up an eepsite tunnel pointing at
it, your eepsite will be visible to others. Detailed instructions for starting
- your eepsite are on your temporary eepsite
+ your eepsite are on your temporary eepsite
page.
Be patient - I2P may be slow to start the first time as it searches for peers. If, after 30 minutes, your Active: connected/recent count has less than 10 connected peers, you should open I2P's port on your firewall for better connectivity. If - you cannot see any eepsites at all (even www.i2p2.i2p), + you cannot see any eepsites at all (even www.i2p2.i2p), be sure your browser proxy is set to 127.0.0.1 port 4444. You may also want - to review the information on the I2P website, - post up messages to the I2P discussion forum, + to review the information on the I2P website, + post up messages to the I2P discussion forum, or swing by #i2p-help, #i2p or #i2p-chat on IRC at irc.freenode.net,