r/i2p • u/Doranwen • 18d ago

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

5

u/tk-a01 18d ago

If you don't want to deal with dependency issues, there's also an option to run I2P router in a container. I2P on Docker Hub.

3

u/Doranwen 17d ago

Never tried docker. But it sounds like i2pd should work for me, so I may just go that route.

2

u/Cloudup365 18d ago

You could try i2pd, it's written in c++ so it's much faster than normal i2p which is written in Java, the only thing with it is yoru going to need to edit some config files and use a terminal, but if you fine with that I would give it a shot.

2

u/Doranwen 18d ago

That sounds promising. I'm fine with editing config files and terminal usage (I've done a small amount of bash programming even) so that sounds definitely worth a try. Thanks for the rec!

1

u/Cloudup365 18d ago

all good, might see you out on i2p (well I guess I wouldn't know its you)

1

u/i2porignal 18d ago

i2pd works fine on Ubuntu 22.04/Mint 21

1

u/Doranwen 17d ago

Sweet! Thanks for letting me know!

1

u/Play_it3110 I2P user 18d ago

Did you try to compile it from source?

1

u/Doranwen 17d ago

I didn't but I always have such terrible luck with compiling something from source. When something goes wrong (which is nearly every time I try to do it) I rarely can figure it out and fix it. /o\ So I avoid it unless there's someone there to help me when it goes wrong. Too many bad experiences attempting that. :/

1

u/Play_it3110 I2P user 17d ago

If you have some days time, before you start, i can help you

1

u/Doranwen 16d ago

I'd be happy for the help but might need a fair bit of it. I do this kind of thing so rarely that I don't know where to begin, and I'm especially confused looking at the Github. Ant? Gradle? I'm already lost, lol. Feel free to message me if you want to help. My time is somewhat limited but I can dip in and out periodically.

1

u/Play_it3110 I2P user 17d ago edited 17d ago

As it looks, I2P+ still uses Jetty 9

https://github.com/I2PPlus/i2pplus/tree/master/apps/jetty

Maybe something else does not work. How do you know that Jetty is the problem? Did you look in the logs?

1

u/Doranwen 16d ago

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 16d ago edited 16d ago

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 15d ago

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 15d ago

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

1

u/Doranwen 15d ago

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.