this post was submitted on 17 Jun 2023
3 points (100.0% liked)

The Invisible Internet Project

1757 readers
1 users here now

I2P Community Edition

This isn't the official I2P channel, if you want go there then you can find it in the links below.

Rules

"Don't be a dick" - Wil Wheaton

General

Media:

File Hosting and Pastebins

Torrents

Social Networks and Microblogging

Exploring I2P

I2P Name Registries

Search engines

IRC

Irc2P comes pre-configured with I2P. To connect with other networks, please follow this tutorial.

Syndie

An open source system for operating distributed forums in anonymous networks

Inproxies

You can use inproxies to surf the I2P network without having to have an I2P router.

Follow us on Twitter

founded 2 years ago
MODERATORS
CAVOK@lemmy.world
idki2p@lemmy.one
3
Host 127.0.0.1 is not inside I2P network, but outproxy is not enabled (kbin.social)
submitted 2 years ago by ReCursing@kbin.social to c/i2p@lemmy.world
4 comments fedilink hide all child comments
 

I have installed i2pd from the Manjaro package, and everything seems to be working fine, I can access i2p sites without problem. However I can't access my local console and everything that entails because I get the the following error

Proxy error: Outproxy failure

Host 127.0.0.1 is not inside I2P network, but outproxy is not enabled

I have tried enabling the outproxy (or at least uncommenting all the lines that include the word outproxy in the default i2pd.conf, and setting outproxy.enabled = true), it makes no difference

I'm using foxyproxy to enable and disable the proxy as needed. If it's disabled, or if I use firefox's internal proxy settings, I get s standard "firefox can't find this site" page, so it's clearly doing something!

This is probably a really obvious mistake I'm making with a three second fix, but I have hit a wall and don't know what I'm doing!

top 3 comments
sorted by: hot top controversial new old
[–] immibis@social.immibis.com 2 points 2 years ago* (last edited 2 years ago) (1 children)

@ReCursing @i2p You are trying to access 127.0.0.1 through I2P. This doesn't work because I2P can only be used to access I2P sites. I guess this is occurring in your web browser. Use a browser that is not using I2P as a proxy, or if it has a list of addresses to not use the proxy for, you can put 127.0.0.1 (and anything else you want to not go through I2P) on that list

[–] immibis@social.immibis.com 2 points 2 years ago

@ReCursing @i2p Sorry that should be: use a browser that is NOT using I2P as a proxy. I edited the toot, but I'm not sure how well that propagates through the Fediverse.

[–] ReCursing@kbin.social 2 points 2 years ago

@immibis (hope I got that link right - I can see your responses on lemmy.world from immibis.social.com but they've not propagated to kbin yet - this whole federation this is really new to me and rather cool, but clearly not quite flawless yet!)

I have now set up foxyproxy to access all *.i2p links through the i2p proxy and all others (including explicitly 127.0.0.1) without. Now I can access i2p links fine and regular links fine in the same browser.

Until five seconds ago I was not able to access the web console, then I thought to check the config file and it turns out the default port is not, as was stated elsewhere, 7657, but 7070, and it seems to be working fine!

Still, without this problem I'd not have sorted foxyproxy so that I can access both networks in the same browser.

Thank you for your help!

load more comments
view more: next ›