Viewing a single comment thread. View all comments

invertedlurker OP wrote (edited )

It never was disabled in the first place. But I added all these outproxies as you suggested. Still nothing. geez I wish I could show you pictures to make sure I'm not doing it wrong.

(also why is the title of every failed access "I2Pd HTTP proxy" ? I'm not using it as far as I know)

By the way here are the startup logs of the tunnel. Port 4444 fails, that might be why

<div>
• Client ready ➜ Listening on 127.0.0.1:7659
• Tunnels ready for client [Standard client on 127.0.0.1:7659]
• Client ready ➜ Listening on 127.0.0.1:4445
• Tunnels ready for client [HTTPS Proxy on 127.0.0.1:4445]
• Client ready ➜ Listening on 127.0.0.1:7660
• Tunnels ready for client [Standard client on 127.0.0.1:7660]
• Stopping client IRC Client on 127.0.0.1:6668…
• Error listening for connections on /127.0.0.1 port 6668: java.net.BindException: Address already used
• Stopping client HTTP Proxy on 127.0.0.1:4444…
• Error listening for connections on /127.0.0.1 port 4444: java.net.BindException: Address already used
</div>

Translated from French because even though I set English, network errors are in my language.

1

cumlord wrote

guessing ports 4444 and 6668 are in use already, any chance another router is running somehow? id figure out what's running those ports and/or change them

1

invertedlurker OP wrote

So I'm coming back, and I actually figured it out. Somehow, there was an instance of I2Pd that was set to run on startup with root privileges. "sudo lsof -i:4444" was what it took to find it. because I didn't think about using lsof with sudo. I killed that instance and also uninstalled I2Pd, to not have problems like that again, and because I never use it anyways. Yeah, you're right.

1