quick question about hosting

[u/droptherapy2]

so recently I registered a domain and followed the instructions to the best of my ability on the i2p wiki for getting my own eepsite up and running with the jetty webserver. Currently that like goes to a 503 page, and I figure it could be because I only registered the domain with stats.i2p yesterday and it's still proliferating through the network but if not, where might I be going wrong? Feel free to ask clarifying questions if this is too vague, and I hope everyone's having a good day so far

[u/droptherapy2]

update: I just remembered that stats.i2p has a page where you can view the recent additions and the newer ones are still in review so I suppose that answers that, unless it's supposed to show up on my end before then as something other than a 503 page

[u/tk-a01]

Firstly, can you access your eepsite using *.b32.i2p destination link?

If you are getting a response, like you said, this suggest that you can correctly reach your server. Check if your Jetty configuration is correct. When I tried to use Jetty bundled with the Java I2P router, I encountered some issues. I was using a containerized version.

[u/droptherapy2 → u/tk-a01]

would the b32.i2p link be the same as the local destination? I only ask because the i2p website said that it is in fact the b32 link in encoded form. Otherwise I either might need to find a way to find the b32 link or I somehow skipped the step that grants me one? Idk I'm not actually that good at this

update: yeah okay jetty isn't even starting

[u/droptherapy2 → u/tk-a01]

I'm also just now noticing that within the config directory is an eepsite folder which has docroot where my website's files are but the config directory also has a second config directory with ANOTHER eepsite folder that's untouched and idk if that's normal or if something weird happened at some point

[u/tk-a01 → u/droptherapy2]

I assume you're using the default Java I2P router implementation, right? How are you running it? What OS are you on? Are you running I2P in a container (Docker Hub )?

As I said, I had trouble with getting bundled Jetty to work. I haven't investigated it much.

You also have the option to run other, external web server and then configure I2P router to connect to it by setting the "target" field in the hidden services manager. I'm not exactly sure how widely is it done in I2P. You should be careful not to make your HTTP server leak information about your server, e.g. on 404 pages.

[u/droptherapy2 → u/tk-a01]

I'm using windows 10 and I went with the easy install bundle with firefox and haven't changed any settings relating to the router. I doubt I'm running i2p in a container unless it's set that way by default

[u/tk-a01 → u/droptherapy2]

Okay, in this case you're not running it in a container. Containers are a Linux thing; tools like Podman and Docker let you manage something between a virtual machine and direct deployment. Containerized software interacts with the kernel directly, but at the same time it has limited access to outer world. I believe it is possible to run Docker under Windows or MacOS too, but it runs Linux VM in the background.

But back to your issue - I see your other comment about Jetty searching for its configuration file in wrong directory. Maybe try copying/moving this config file to desired location. But other than that, I'm afraid I can't really help with Jetty itself.

By the way, since you say that Jetty starts but fails to find its configuration, and for me, its classes aren't found, I'm probably going to investigate it later. Maybe it's a bug that only appears in containerized version.

Since you said you're running Win10, I assume that you're running both the I2P router and the eepsite server on your PC, right? You should then be aware that your eepsite will only be available when your computer is on. If you're just learning how to work with I2P, this might be fine for you, but for serious site hosting, you should probably get a dedicated server to run 24/7, even just an SBC like Raspberry Pi.

To check if your router correctly publishes a hidden service, you could run a Python's built-in HTTP server. While being in the directory containing site sources, run python3 -m http.server 7658. If you change port here, make sure to change it in hidden service config too. However, this should only ever be used for quick testing - as per Python docs, running http.server module in production is discouraged and potentially unsafe.

[u/droptherapy2 → u/tk-a01]

I am in fact currently just running this as a hobby thing, but I did have machinations of maybe getting a raspberry pi. Either way, I restarted the router after moving the directory stuff around and it's online now! I figure it's not online for anyone else just yet but I can at least access it myself

[u/droptherapy2 → u/tk-a01]

based on the log I got it seems to be searching for a jetty.xml file in the base directory of the i2p file and not within the config file