If you've just started I2P, the Active: number on the left should start to grow over the next few minutes and you'll see some local "destinations" listed on the left (if not, see below). Once those show up, you can:
We've bundled some software to let you run your own eepsite - a
Jetty instance listening on
http://localhost: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. Your eepsite's
destination (which uniquely and securely identifies it) is shown on the I2PTunnel
configuration page - if you want other people to see your eepsite,
you need to give them that really huge string. Just paste it into the
Eepsite announce forum, add it to
ugha's wiki, orion's list, or paste it in the #i2p or #i2p-chat channels on
IRC (be sure to split it into two lines, as its too long for one).
If the left hand side has a warning, telling you to check your NAT or firewall, please see the config page and make sure that you can receive inbound TCP and UDP connections on port 8887 (or another port that you specify). Problems forwarding that port account for the vast majority of issues people run into. When it says "Active: 72/85", the "72" means how many peers you are connected with now, and "85" means how many you have spoken with recently - if that first number is 0, you can bet that there are firewall issues. If the second number is under 5, you should reseed (a link on the left hand side of the page will show up to help you when necessary).
If you are still having problems, you may want to review the information on the I2P website, post up messages to the I2P discussion forum, or swing by #i2p or #i2p-chat on IRC at irc.freenode.net, irc.postman.i2p or irc.freshcoffee.i2p (they're linked together).
As a note, you can change this page by editing the file "docs/readme.html"