If you've just started I2P, the Active: numbers on the left should start to grow over the next few minutes and you'll see a "shared clients" local destination listed at the bottom of the sidepanel on the left (if not, see below). Once green stars are indicated next to your local destinations, there are a range of services you can access including:
127.0.0.1 port 6668
. This points at
one of two IRC servers hosted by I2P stalwarts Postman and Badger on I2P, but neither you nor they know
where the other is.127.0.0.1 port 4444
, then
browse to an eepsite (anonymous, encrypted webserver run over I2P) or a normal http://
address. Some useful resources are listed below: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
it, your eepsite will be visible to others. Detailed instructions for starting
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), 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, or swing by #i2p-help, #i2p or #i2p-chat on IRC at irc.freenode.net, irc.postman.i2p or irc.freshcoffee.i2p (they're linked together).