# I2PInterface won't work for server, I2P over TCP/Backbone does!

_General · started by CarL_PetErson on Sun, Jun 21, 2026 3:19 PM_

---

## Original post

**CarL_PetErson** · Sun, Jun 21, 2026 3:19 PM

I tried to make I2P work on my setup, because the connection was flakey at best, if there was a connection at all, but with no success.  
Until I manually configured a tunnel and used the TCPServerInterface and it worked instantly and reliably. After that I tried the Backbone Interface and it also worked great.  
Interestingly this only seems to be a problem on the server side, I can connect to those with the I2PInterface without any issues.

I don't know if it's something with my setup or with the I2PInterface, but I thought I'd share, since a lot of people seem to have issues with I2P.  
Also: I only tested the connection between my server and sideband.

If someone wants to try the difference, I'll keep the old Interface running for now:
- I2PInterface: webejkcdlwk3z53cebtoed3lpeobrmlsaawvhx5mtx24sbbadneq.b32.i2p
- Backbone: emrpfen2gl6us7fl5mwuyskxnl5zjguodmyra5z7j3p747wjucpq.b32.i2p

---

## Reply 1

**CarL_PetErson** · Sun, Jun 21, 2026 4:03 PM

Sidenote: since the interface will show as backbone on discovery, one might have the idea to make a fake I2PInterface and set reachable_on= to the Backbone address. That won't work.

---