archive (I2PFox, iMule, I2P-Messenger, ... ) and information for I2P</li>
<li><ahref="http://paste.i2p2.i2p">paste.i2p2.i2p</a>: secure and
anonymous paste service.</li>
</ul><br>
There are many more eepsites - just follow the links from the ones you see,
bookmark your favorites, and visit them often!
</li>
<ul>
<liclass="tidylist"><b>browse the web</b> - there is currently an HTTP
"outproxy" in I2P hooked up to your own HTTP proxy on port 4444 - simply
set your browser's proxy to use it (as above) and go to any normal URL
- your requests will be bounced through the I2P network.</li>
<liclass="tidylist"><b>transfer files</b> - there is an integrated <ahref="/i2psnark">port</a>
of the <ahref="http://www.klomp.org/snark/">Snark</a><ahref="http://www.bittorrent.com/">BitTorrent</a>
client.</li>
<liclass="tidylist"><b>use anonymous email</b> - postman has created a
mail system compatible with normal mail clients (POP3 / SMTP) that allows
email within I2P as well as mail from and to the normal internet! get
your account at <ahref="http://hq.postman.i2p/">hq.postman.i2p</a>. We
bundle <ahref="/susimail/susimail">susimail</a>, a web based anonymity-oriented
pop3/smtp client configured to access postman's mail services.<br>Alternatively, you can try out our new serverless, end-to-end encrypted e-mail system <ahref="http://tjgidoycrw6s3guetge3kvrvynppqjmvqsosmtbmgqasa6vmsf6a.b32.i2p/">I2P-Bote</a> (with webinterface), installable as a plugin.<br></li>
<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>
