Is your I2P router running in a container like Docker or systemd-nspawn
? I had some issues with this error back when I ran my router in a systemd-nspawn
container with VirtualEthernet=yes
.
But id shutting down the I2P router and running something different on the same port like an HTTP server, and trying to access it from a vpn or tor or something and make sure your ISP isnt doing anything weird on this specific port.
And if you are using i2pd, you can goto the webconsole and go inside "Router Commands" and click "Run peer test" to have it test again. Im not sure how to do this in Java I2P tho.
I'm not very familliar with Java I2P, but I took a look at the documentation for Docker, and I didnt see anything about this issue, but I did have the same issue with i2pd in a container. I would try installing it manually and running it outside of the container.
If you need the bind mount feature from Docker, and you are on a systemd system, I recommand using systemd's PrivateMounts feature. It can be added in a dropin file that can be created with the command
systemctl edit i2p.service
, thei2p.service
may be different depending on your distro, but for Java I2P's package on Arch its justi2p.service
, but you can add the following in a dropin file to get the same private mounts just for your I2P router:You might have to mess around with file permissions depending on who you run your I2P router as.
Sorry I dont have a better solution, I dont know much about Docker. But I think the developer of the Java I2P router is on r/i2p on reddit, and I think you can find him on http://i2pforum.i2p/, he prolly knows a whole lot more about Java I2P and the Docker image than I do.