[Solved] I2p app disruption

I’ve been using i2p - but now that FreedomBox has removed i2p I’m having trouble getting this sorted. I’d like to recreate the FreedomBox experience for that app which was really great.

Problem Description
This all started with a recent update taking some additional steps with i2p removal from FreedomBox. I was no longer able to access the FreedomBox console at http://freedombox:7657/.

I can see that /usr/share/freedombox/etc/apache2/conf-available/i2p-freedombox.conf is removed and the symlinks in /etc/apache2/conf-available and /etc/apache2/conf-enabled point to the missing file.

What I’d like to do is get copies of the relevant and deleted Freedombox configurations and use those to get i2p working well as it was.

Thus far I have the /usr/share/freedombox/etc/apache2/conf-available/i2p-freedombox.conf file from an older release, but I’m wondering how to find the other modifications FreedomBox did for i2p.

This is the merge request in which i2p app was removed:

You can see all the specific files that were removed here.

1 Like

Fabulous, @jvalleroy, that is immensely helpful!

I’m up and running again - only missing the i2p link on the FreedomBox page, but I can type the url freedombox/i2p.

If you are installing i2p on FreedomBox you can use the debian packages distributed from the i2p project.

  • Follow the installation instructions
  • note random router port in /var/lib/i2p/i2p-config/router.config
  • add that port number to your external firewall exceptions (and never share this port number which can be used to identify you)
  • read the i2p FAQ which contains the port numbers used by i2p - you set these up on your internal firewall

This next step seems to be the key. Once you do this you can access the console from a client on the internal network. After this step, you just need to fix up the settings in the i2p console.

Now you’ll need to go into the tunnel manager in the console and tunnels to your internal IP address.

  • i2p http proxy is bound to 127.0.0.1 - stop the tunnel and change it to internal IP
  • repeat with the other tunnels you need (https proxy, i2psnark, IRC, etc.)
1 Like