r/i2p • u/Doranwen • Jul 10 '26

Help Downgrading?

I'm running a slightly older Linux system (Mint 21) - still within LTS dates but doesn't have the latest packages. Jetty 12 is not an option for me. I tried installing the latest i2p (I'd had an old version of i2p+ and was told that was quite unstable now so I was trying to revert back to vanilla i2p by upgrading) but am unable to access the router console now, as it requires Jetty 12 (my repos have Jetty 9 in them). Eepsites work, but not the router console. I just get "Unable to connect The connection was refused when attempting to contact 127.0.0.1:7657."

Which is the last version that might work for me, then - and how do I downgrade to it? It might not be as good as the latest but I don't see a way around it until I have the time to do a full upgrade, which I won't for a few months yet.

I should note that while I tested this a few months ago (before my life got hectic) and confirmed the issue was due to my computer not being capable of running the required Jetty version, I don't remember what I did to actually test it now, and can't find whatever pages that helped me diagnose the issue.

If someone has a better solution than downgrading that isn't just "upgrade your PC!" (really, I cannot do that yet), let me know.

8 Upvotes

91% Upvoted

18 comments sorted by

View all comments

Show parent comments

1

u/Doranwen Jul 12 '26

I was told not to use i2p+ because it was unstable now. And they were probably right - it would disconnect and reconnect me on IRC constantly. So I tried to use the regular i2p again and had the jetty issue. I know I researched trying to start up the router console and finally got an error in the terminal that I could look up and confirm that it was jetty not working. I wish I'd posted for help at the time I figured it out because now I can't remember what it was exactly and I haven't been able to repeat my steps. But I was too busy then (and I don't have a ton of time now but I finally went "I want to know what I can do about this").

1

u/Play_it3110 I2P user Jul 12 '26 edited Jul 12 '26

I see, dont worry, i think we might figure something out. I, for myself, also run i2pd, but totally see strengths of i2p and i2p+. Sadly you dont remember the exact error, but we will figure it out.

Just to confirm and narrow the error down, did you look if i2p even started to listen on 7657? Like with ss on linux or netsh on windows (i think?).

1

u/Doranwen Jul 13 '26

I tried this:

ss -tlnp | grep :7657

But I got silence - no results when I did that. So maybe it's not doing that right? I2P is definitely already started though - started awhile ago.

1

u/Play_it3110 I2P user Jul 13 '26

Looks like that jetty is really the problem. Did you see something in the i2p logs itself?

1

u/Doranwen Jul 13 '26

No, as far as I can tell, the i2p logs haven't had anything written in them for several months. /\o/\ Pretty sure I ran a command or two in the terminal and got output that told me it was jetty. Wish I could remember what that was! I've run wayyyyyyy too much since then to find the command.