Eepsite problem - only getting 503 ...
I am trying to use the Jetty server build into I2P to host a site. This site, actually ;) However, I currently cannot even get the pre-configured help-pages to show up. Now I am trying to find out, what gives.
In the routerconsole the tunnel is shown as up. Pressing the Preview button only gives me
503 Service Unavailable
This I2P website is unavailable. It may be down or undergoing maintenance.
Jetty seems to get loaded, though:
Looking into the router log shows an error then:
So it tries to connect to local port 7658, but doesn’t succeed. Why? The website should be reachable using 127.0.0.1:7658. But wait, is it?
No, nothing is listening on Port 7658. What gives?
The Configuration
All this is using:
Java 1.7 should be ok, I assume. The configuration of the tunnel I configured in the
web-console of I2P is in /var/lib/i2p/i2p-config/i2ptunnel.config
configuration-file-wise. That looks ok. But the tunnel is shown as up, so maybe that’s not
the problem here. The settings for the Jetty server are in
/var/lib/i2p/i2p-config/eepsite/jetty.xml
. Looks ok, too, or something.
I just don’t get it :(
Update
Should have been easy, it turns out. The eepsite basically is the
combination of a jetty web-server as a process listening on a local
port PLUS the tunnel to make that port available under a specific
name (that of the eepsite). I looked through all (probably) configuration
pages while trying to find out what’s wrong, but everything looked
alright to me. Turns out I was simply missing the service. Like the
router console didn’t know about jetty at all. And so jetty got not
started, becaues that is done by the I2P router. Digging around I found
those are defined in /var/lib/i2p/i2p-config/clients.config
. And mine had
only 3. It was really short.
So I remote I2P competely with apt-get purge i2p
followed by apt-get autoremove
to also remove all packages only depending on i2p. I then re-installed,
re-configured, and voila, everything good again. How did that happen?
I don’t like re-installing to fix things usually and I am not used to
that from Linux stuff.
I had migrated the OS of the machine to a newer version including an
update of the package sources. I suspect something could have went wrong therein.
But not sure. Usually in the end it turns out I have done something stupid ;)
But if you keep getting 503 pages instead of your pages (the help pages by default), remember to check both:
- the service I2P webserver must be listed as started (click on
I2P SERVICES on the router-console leading you to
/configclients
) - the according hidden service (by default named I2P webserver again)
must be listed as started in the HIDDEN SERVICE MANAGER reachable from the
router console and leading to
/i2ptunnelmgr
The hint to look for the other and where to find it came from user hummingbird in the thread@zzz.i2p where I asked for help. Thx buddy!
Tagged: i2p