<liclass="tidylist"><b>chat anonymously</b> - fire up your own IRC client
and connect to the server at <b>127.0.0.1 port 6668</b>. This points at
one of two anonymously hosted IRC servers, but neither you nor they know
where the other is.</li>
<liclass="tidylist"><b>blog anonymously</b> - check out <ahref="http://syndie.i2p2.de/">Syndie</a></li>
<liclass="tidylist">and lots more</li>
</ul>
</ul>
<h2>Want your own eepsite?</h2>
<p>We've bundled some software to let you run your own eepsite - a <ahref="http://jetty.mortbay.org/">Jetty</a>
instance listening on <ahref="http://127.0.0.1:7658/">http://127.0.0.1:7658/</a>.
Simply place your files in the <code>eepsite/docroot/</code> directory (or place
any standard JSP/Servlet <code>.war</code> files under <code>eepsite/webapps</code>,
or standard CGI script under <code>eepsite/cgi-bin</code>) and they'll show
up. After starting up an <ahref="/i2ptunnel/">eepsite tunnel</a> pointing at
it, your eepsite will be visible to others. Detailed instructions for starting
your eepsite are on <ahref="http://127.0.0.1:7658/">your temporary eepsite
page</a>. </p>
<h2><aname="trouble">Troubleshooting</a></h2>
<p>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 <ahref="http://www.i2p2.i2p/">www.i2p2.i2p</a>),
be sure your browser proxy is set to 127.0.0.1 port 4444. You may also want
to review the information on the <ahref="http://www.i2p2.i2p/">I2P website</a>,
post up messages to the <ahref="http://forum.i2p2.de/">I2P discussion forum</a>,
or swing by
<ahref="irc://127.0.0.1:6668/i2p-help">#i2p-help</a>, <ahref="irc://127.0.0.1:6668/i2p">#i2p</a> or <ahref="irc://127.0.0.1:6668/i2p-chat">#i2p-chat</a>
on IRC at <ahref="irc://irc.freenode.net/#i2p">irc.freenode.net</a>,
irc.postman.i2p or irc.freshcoffee.i2p (they're linked together).</p>