<p>In I2P, hidden services are addressed using a Base32 address ending in ".b32.i2p", or a Destination represented as a long Base64 string.
The Base32 address may be used as a hostname, until you assign a register a name following the instructions below.
The Destination is somewhat like an IP address, and is shown on the <ahref="http://127.0.0.1:7657/i2ptunnel/edit?tunnel=3">Hidden Service Configuration page</a>.
It can only be accessed with the long Destination or with the shorter Base32 address (.b32.i2p), which is a hash of the Destination.
You could just tell people the Destnation or the Base32 address, but thankfully I2P has an address book and several easy ways to tell people about your website.
<li>Pick a name for your website (<i>something</i>.i2p), using lower-case.
You may wish to check first in your own router's <ahref="http://127.0.0.1:7657/susidns/addressbook?book=router&filter=none">address book</a> to see if your name is already taken.
Enter the new name for your website on the <ahref="http://127.0.0.1:7657/i2ptunnel/edit?tunnel=3">Hidden Service Configuration page</a> where it says "Website name".
This will replace the default "mysite.i2p".
Also, if you would like your I2P Webserver tunnel to be automatically started when you start I2P, check the "Auto Start" box.
Your website will now start every time you start your router.
<li>Highlight and copy the entire Local destination on the <ahref="http://127.0.0.1:7657/i2ptunnel/edit?tunnel=3">Hidden Service Configuration page</a>.
Make sure you copy the whole thing, it is over 500 characters.
<li>Enter the name and paste the destination into your <ahref="http://127.0.0.1:7657/susidns/addressbook?book=router&filter=none">address book</a>.
<p>Now it is time to add your website to an I2P address book hosted by a site such as <ahref="http://stats.i2p/ "target="_blank">stats.i2p</a> or <ahref="http://no.i2p/"target="_blank">no.i2p</a>.
You must enter your website name and Destination (or Registration Authentication string) on one or more of these sites.
</p><p>Some registration sites require the Destination.
If so, highlight and copy the entire Local destination on the <ahref="http://127.0.0.1:7657/i2ptunnel/edit?tunnel=3">Hidden Service Configuration page</a>.
Make sure you copy the whole thing, it is over 500 characters.
</p><p>Some registration sites, including <ahref="http://stats.i2p/i2p/addkey.html"target="_blank">stats.i2p</a>, require the Registration Authentication string.
It is found on the <ahref="http://127.0.0.1:7657/i2ptunnel/register?tunnel=3">Registration Authentication page</a> linked from the <ahref="http://127.0.0.1:7657/i2ptunnel/edit?tunnel=3">Hidden Service configuration page</a>.
Copy the entire authentication string and paste it on the registration page.
Make sure you copy the whole thing, it is over 500 characters.
Describe your site briefly if the site requests this information.
If your site is a HTTP service, leave the checkbox selected; if not, unselect it.
</p><p>For all registration sites, read through the Terms of Service carefully.
Since many routers periodically get address book updates from these sites, within several hours others will be able to find your website by simply entering your hostname in their browser.</p>
<p>Speaking of address book updates, this would be a good time to add some more addressbooks to your own subscription list.
Go to your <ahref="http://127.0.0.1:7657/susidns/subscriptions">Subscriptions Configuration page</a> and add one or more for an automatically updated list of new hosts:
<p>Some people check website lists such as <ahref="http://identiguy.i2p/"target="_blank">Identiguy's eepsite status list</a> or <ahref="http://no.i2p/browse/"target="_blank">no.i2p's active host list</a> for new eepsites, so your site may start getting some traffic.
There are plenty of other ways to tell people. Here are a few ideas:
<p>Note that some sites recommend pasting in that really long destination.
You can if you want, but if you have successfully registered your hostname on a registration service, tested it using a jump service, and waited 24 hours for the address book update to propagate to others, that shouldn't be necessary.</p>
<p>This site (and the I2P router console) is running on the <ahref="https://en.wikipedia.org/wiki/Jetty_(web_server)"target="_blank">Jetty webserver</a>, but you may wish to use a different webserver to host your content.
To maintain anonymity, be sure that your webserver is configured to only allow connections from localhost (127.0.0.1), and check the documentation to ensure your webserver isn't advertising details that may compromise your anonymity.
<p>To configure your webserver for use on I2P, you may either use the existing webserver tunnel and <ahref="http://127.0.0.1:7657/configclients">disable the default webserver</a> from running, or create a new HTTP Server tunnel in the <ahref="http://127.0.0.1:7657/i2ptunnelmgr">Hidden Services Manager</a>.
For example, if your webserver is listening by default on address 127.0.0.1 port 80, you'd need to also ensure that the Target port in the Hidden Service Manager settings page for the service is also configured to port 80.
There are plenty of guides online, for example if you search for "nginx security hardening guide" you will find a number of guides that have good recommendations.
This page, the project website and the router console need translations!
Please help the project grow by <ahref="http://i2p-projekt.i2p/getinvolved.html"target="_blank"> getting involved</a> or <ahref="http://i2p-projekt.i2p/en/get-involved/guides/new-translators"target="_blank">translating</a>.
