I try to reach zzz.i2p and get this Unsupported encryption options. On some other sites too. I have the latest router 1.5.0. Is it wrong with my router? This happened when I upgraded. Cany anyone help?

--
Posted on RetroBBS

notbob.i2p shows up! Click on the bottom and it will show up

Don't freak out my records show he is eating turkey and peaches. I keep a close eye on him so he does not wet the bed or drupe on his pillow.

--
Posted on RetroBBS

If you have a dual install with i2pd 0.9.31 and you did not change i2pd.conf to add the encryption you need to change the port on i2p+ and your browser to access zzz.i2p. In the tips for Qubes users that port is 3333 so to access zzz.i2p you have to set your browser to 127.0.0.1:3333. Ideally you do have 2 browsers... New I guess.

--
Posted on RetroBBS

Anonymous wrote:

> If you have a dual install with i2pd 0.9.31 and you did not change i2pd.conf to add the encryption you need to change the port on i2p+ and your browser to access zzz.i2p. In the tips for Qubes users that port is 3333 so to access zzz.i2p you have to set your browser to 127.0.0.1:3333. Ideally you do have 2 browsers... New I guess.

I haven't tried i2pd yet, just using Java i2p. Should I expect to be able to reach zzz.i2p with this router, or do I need to change something?

I'm very interested in i2pd and it sounds from your reply that it can run alongside my current routher. I'll try this soon.

--
Posted on Rocksolid Light

If i2pplus 1.50 is your ONLY router and can't reach zzz.i2p you have a problem. Can you reach notbob.i2p?
1. The download was corrupt or your OS is corrupt.
2. I would try GUIX overlay first for your OS and download i2pplus with Epiphany browser (or ungoogled-chromium). GUIX uses Mozzila https witch is the latest and greatest. Or you can try the download again from shanks.i2p or tracker2.postman.i2p

--
Posted on RetroBBS

Anonymous wrote:

> If i2pplus 1.50 is your ONLY router and can't reach zzz.i2p you have a problem. Can you reach notbob.i2p?
> 1. The download was corrupt or your OS is corrupt.
> 2. I would try GUIX overlay first for your OS and download i2pplus with Epiphany browser (or ungoogled-chromium). GUIX uses Mozzila https witch is the latest and greatest. Or you can try the download again from shanks.i2p or tracker2.postman.i2p

Yes, it's 1.50. I can't reach notbob.i2p or stats.i2p, but I can reach postman. I'll have to dig further, thanks for your suggestions.

--
Posted on Rocksolid Light

I had a similar problem at some point. Turned out i was running a massively outdated version of i2p.

--
Posted on RetroBBS

Anonymous wrote:

> I had a similar problem at some point. Turned out i was running a massively outdated version of i2p.

I've done that in the past since I don't always run the latest stuff or upgrade as I should. But afaik I'm running the latest i2p router. When I get more time I'll try to figure it out and post back what was wrong. Don't have time right now as rl always gets in the way of more important things.

--
Posted on Rocksolid Light

I have it working now. First I upgraded java, but that made no difference.

Then I stopped the debian(ubuntu) install from i2p repository and installed the latest without using the package manager. The version number for what I stopped is 1.5.0-0 and exactly matches the version number I just installed (which works).

Not sure where the issue was but I'm still wondering why the exact same version number is working differently. But it is working.

Thanks for the suggestions here.

--
Posted on Rocksolid Light

(note: i may be wrong, i am not using stock i2p, apologies for that)
(also i believe this is the solution, sorry if not)

I2P has 2 encryption across the network.
ElGamal, the old one, and ECIES, the one to replace ElGamal.
"Unsupported encryption" came to me too.
Turns out my HTTP tunnel somehow set itself to ElGamal only.

How to fix it (for future readers):
1. Go to Tunnel Manager (http://127.0.0.1:7657/i2ptunnelmgr)
2. Go to whatever HTTP tunnel you are using.
(most probably the one at the top saying "HTTP Tunnel" with port number 4444)
3. Under "Encryption Types" there are 3 options. (may be a dropdown box with a different name)
"ElGamal", "ECIES", and "Both types".
4. Until ElGamal is fully deprecated (probably won't be in near future) select Both.
5. At the bottom of the page press Save.

Since apt and your home-install uses different directories for configurations, your install (most likely) defaulted to "Both encryption types" on first-launch.
But apt's configuration kept the old setting, whatever zzz.i2p doesn't allow.
Hope this helps somebody.

--
Posted on Rocksolid Light

Anonymous wrote:

> (note: i may be wrong, i am not using stock i2p, apologies for that)
> (also i believe this is the solution, sorry if not)

> I2P has 2 encryption across the network.
> ElGamal, the old one, and ECIES, the one to replace ElGamal.
> "Unsupported encryption" came to me too.
> Turns out my HTTP tunnel somehow set itself to ElGamal only.

Thanks for posting this, it was exactly what was wrong with my setup!

--
Posted on Rocksolid Light

Glad I could help.

--
Posted on Rocksolid Light