says couldn’t resolve host the syntax is correct… any ideas how to fix this or what was changed? i tried again with whonix 15 and the site and other i2p eepsites worked
Nothing related in Whonix changed as far as I know.
@knoglez did you resolve this issue? I’m having the exact same problem. I’ve been trying to fix it for two days to no avail.
@Patrick I’ve attempted the same method as knoglez on both a Whonix Virtual machine through windows and Qubes-Whonix through QubesOS. Have you been made aware of any changes since this post?
No.
i2pd flatpak is working for me on Qubes-Whonix 16. Install as user in AppVM:
flatpak --user install flathub website.i2pd.i2pd
In TorBrowser, disable https-everywhere extension. In about:config change:
network.dns.offline-localhost–>false
network.dnsCacheEntries–>0
network.dnsCacheExpiration–>0
network.proxy.no_proxies_on–>1
network.proxy.share_proxy_settings–>true
network.proxy.ssl–>127.0.0.1
network.proxy.ssl_port–>4444
browser.fixup.fallback-to-https–>false
All of those may or may not be necessary but, looking back at my modified prefs, that’s what worked for me.
As for the toolbar search issue, also in about:config, change:
keyword.enabled–>false
browser.urlbar.suggest.searches–>false
1 Like
Hello, I was originally trying the whonix guide which didn’t work. I was sent to this thread. Trying your method. I’ve got the i2pd gui installed. It says connected
Routers: 275 Floodfills: 186 LeaseSets: 0
Client Tunnels: 41 Transit Tunnels: 0
But when I try to goto router page in tor browser or any .i2p sites it just states “unabled to connect”.
Before in the whonix guide it mentions all these proxy settings, privoxy, proxifyer, I didn’t do that here. Just your tor browser settings and installed i2pd from flatpak. Is there more i should do this time around? I’m also using whonix workstation on qubes for this. Thank you kindly for your advice.
1 Like
Your connection to the i2p network appears to be ok. In TorBrowser about:config, ensure you’ve changed these values as well:
extensions.torbutton.use_nontor_proxy–>true
network.proxy.http–>127.0.0.1
network.proxy.http_port–>4444
Now, try visiting a stable i2p site such as http://stats.i2p or http://zzz.i2p. If you can see those, then TorBrowser is configured correctly to access i2p.
With i2pd, there is no router config page at 127.0.0.1:7657. The flatpak gui app is in essence the router config.
1 Like
I’ve change the wiki Invisible Internet Project (I2P) from no longer working installation from packages.debian.org (i2p package no longer available for Debian 11 bullseye) to installation from official I2P APT repository.
Anything incomplete in the wiki? Could you please edit the wiki to add any new / additional / different (?) settings which are required nowadays?
(Anyone can edit the wiki. With or without account. → Improve the Documentation / Edit the Whonix ™ Wiki)
Okay these last three settings did it.
Actually I misread, and at first only entered
network.proxy.http>127.0.0.1
network.proxy.http_port>4444
Which didn’t work only at first!
Then reread and saw extensions.torbutton.use_nontor_proxy>true. After entering that it worked. So definitely need all those three settings.
However there seems to be still something strange going on with https.
If it takes a site too long to load, it seems to try to redirect to https. Then I can never get to the site again as it always tries to goto https.
I found this site: http://reg.i2p/alive/
Which seems to be a directory. And I’m just clicking whatever is stated at being alive. Now disclaimer I don’t know what these sites are so just clicking randomly to test. So forgive me if there’s something offensive there.
Thus far I’m able to get to some sites. But for some reason cannot currently see:
in.i2p
http://isitup.i2p/
darknetnow.i2p
aaaaaaaalivetalkzzzzzzzz09allarxmetarootsznzarxpostmetasymbol.i2p
Only listing them to figure out why I can visit some sites and not others in case others can visit them. Is it maybe these sites actually have https installed? Or maybe at the time of writing these sites are actually done. I don’t know.
But I can’t figure out why when I add http://isitup.i2p, it always changes to https then the site won’t load.
Currently https everywhere plugin is disabled.
And I’m usually the following recommended settings all listed above.
I tried looking in to if tor browser has a cache, it seems to be limited to the session only. So I cleared everything and restarted the browser. Still redirects to https.
Other than I’m glad to get some functionality out of the system and now I can learn more about i2p on whonix! Thank you for the assistance thus far! You guy have been a real help 
By the way this experience is very nostalgic. Because of the decentralised aspect you’re searching for lists of links. Some sites are already down. You feel surprised when you get an up to date list link.
And most of these sites seem to be purely html. It’s like using the internet again for the first time in the 90s when there were no search engines. Very old school. Very cool
Just tested two things. When there’s no internet sites like http://zzz.i2p/ automatically redirect to https. But when there’s internet, it will go back to not redirecting and accepting a connection to http://zzz.i2p.
However these site darknetnow.i2p/, isitup.i2p, in.i2p no matter what I do redirects to https. So as far as my limited knowledge can tell this site either requires https and I messed something up in setting up in i2pd or tor browser preventing it from establishing a secure https connection. Or there is a cache that I don’t know about in i2pd, tor browser or whonix workstation. Or those sites are actually down and there is some auto redirect setting still active in tor browser that I haven’t figure out how to disable 
I can edit it to include the flatpak solution. Is that considered foreign?
1 Like
Foreign: both, flatpak and upstream I2P repository is considered foreign from perspective of Whonix.
But I2P repository from geti2p is the official repository and flatpak is inofficial?
Hence, I2P repository version should be preferred. Any reason against it?
i have updated I2P wiki to the latest configs, dropping privoxy need and just making TB work with I2P nicely, fixing the force https…etc.
But there is a note need to be taken care and i have created a ticket about it which is you cant enter I2P eepsites and on the same time entering I2P console (127.0.0.1:7657) due to this issue:
1 Like
correct
nope, its just third party repo thats it (similar to TPO with Tor).
1 Like
1 Like
-
Tested I2P over Tor in Whonix-WS = connection working better than clearnet lol
-
Improved I2P eepsites opening in TB without enforcing HTTPS (TB about:config tweak), and hexchat connectivity with many I2P-Whonix wiki improvements.
-
Minor improvement to the router.config:
1 Like
This is outdated by now. Newer forum thread here:
I2P client inside Whonix-Workstation Issues - #15 by eyedeekay
Therefore closing this.