Typo on my part. I meant 127. I forgot this topic as I found what had caused it. If you start i2p with “i2prouter start” it will successfully start a single node at 127.0.0.1. If you then for some reason type “sudo systemctl start i2p”, it will start a second node which will open at 127.0.0.2. It is not an issue that you will normally run into as you will only be using “i2prouter start”. I assume that is to do with apparmor?
dunno, just use the working method as mentioned in the wiki.
Yeah no issues with that, you need to enforce i2p apparmor anyway (comes in complain mode by default).