PurpleI2P / i2pd

🛡 I2P: End-to-End encrypted and anonymous Internet
https://i2pd.website
BSD 3-Clause "New" or "Revised" License
3.28k stars 424 forks source link

[Question] Unable to connect to I2P #1757

Closed sjehuda closed 2 years ago

sjehuda commented 2 years ago

Hello, For several weeks, I'm not avle to connect. I'd like to inspect I2Pd for possible issues. Is this a proper place to ask for help?

Proxy error: Host is down Can't create connection to requested host, it may be down. Please try again later.

r4sas commented 2 years ago

Are you sure that requested host is online? What about stats on main page of Webconsole?

sjehuda commented 2 years ago

Are you sure that requested host is online?

Yes, those are the i2p registries I'm trying to reach.

What about stats on main page of Webconsole?

Proxy error: Outproxy failure Host localhost not inside I2P network, but outproxy is not enabled http://localhost:4444/

r4sas commented 2 years ago

Proxy error: Outproxy failure Host localhost not inside I2P network, but outproxy is not enabled http://localhost:4444/

You mustn't use proxy for accesing webconsole.

sjehuda commented 2 years ago

As far as I know, I'm not accessing http://localhost:4444/ via proxy

r4sas commented 2 years ago

Webconsole is on http://127.0.0.1:7070/, 4444 is proxy.

sjehuda commented 2 years ago

Oops. Here it is:

i2pd webconsole
Uptime: 18 hours, 56 minutes, 19 seconds
Network status: Unknown
Tunnel creation success rate: 0%
Received: 0.00 KiB (0.00 KiB/s)
Sent: 0.00 KiB (0.00 KiB/s)
Transit: 0.00 KiB (0.00 KiB/s)
Data path: /var/lib/i2pd
Routers: 88 Floodfills: 0 LeaseSets: 0
Client Tunnels: 2 Transit Tunnels: 0

HTTP Proxy | Enabled -- | -- SOCKS Proxy | Enabled BOB | Disabled SAM | Enabled I2CP | Disabled I2PControl | Disabled
i2pd webconsole [Main page](http://127.0.0.1:7070/) [Router commands](http://127.0.0.1:7070/?page=commands) [Local Destinations](http://127.0.0.1:7070/?page=local_destinations) [Tunnels](http://127.0.0.1:7070/?page=tunnels) [Transit Tunnels](http://127.0.0.1:7070/?page=transit_tunnels) [Transports](http://127.0.0.1:7070/?page=transports) [I2P tunnels](http://127.0.0.1:7070/?page=i2p_tunnels) [SAM sessions](http://127.0.0.1:7070/?page=sam_sessions) Uptime: 18 hours, 56 minutes, 19 seconds Network status: Unknown Tunnel creation success rate: 0% Received: 0.00 KiB (0.00 KiB/s) Sent: 0.00 KiB (0.00 KiB/s) Transit: 0.00 KiB (0.00 KiB/s) Data path: /var/lib/i2pd Hidden content. Press on text to see. Routers: 88 Floodfills: 0 LeaseSets: 0 Client Tunnels: 2 Transit Tunnels: 0 Services HTTP Proxy Enabled SOCKS Proxy Enabled BOB Disabled SAM Enabled I2CP Disabled I2PControl Disabled
r4sas commented 2 years ago

Hm, looks like i2pd haven't internet access. Maybe you blocked outgoing connections?

sjehuda commented 2 years ago

I use OpenSnitch Firewall. I've disabled it and I still get the same result for I2P.

If that helps, I'm running a Tor proxy and Tor works well.

r4sas commented 2 years ago

Stop i2pd, set loglevel to info in /etc/i2pd/i2pd.conf and start it again. If after restarting in 5 minutes nothing changes, check logs at /var/log/i2pd/i2pd.log.

Are you forwarding all traffic to tor?

sjehuda commented 2 years ago

On Mon, 23 May 2022 07:00:16 -0700 R4SAS @.***> wrote:

Stop i2pd, set loglevel to info in /etc/i2pd/i2pd.conf and start it again. If after restarting in 5 minutes nothing changes, check logs at /var/log/i2pd/i2pd.log.

Now, it's working, with Privoxy and directly with proxy port 4444. I don't know why it didn't earlier.

Are you forwarding all traffic to tor?

Yes, except for port 4444 (i2p)