Connection through Tor/Socks5 doesn't work

[Revertron]

If you try to add something like socks://127.0.0.1:9050/ygg.mkg20001.io:80 into peers you will get invalid username/password in yggdrasil log.

But if I configure some username and password in Tor and use those creds in socks:// url it works. I think Yggdrasil needs to send empty username+password to the socks-server.

[majestrate]

if tor does not support no auth in socks5 would it not be a bug in our socks5 client dep? it should send back an error like "proxy refused request, authorization type [placeholder values goes here] not supported" if we are talking to a socks5 proxy that does not accept anon socks5 request.

[Revertron]

But it works from Firefox without credentials. Should work from Yggdrasil, no?

[majestrate]

On Thu, 06 Apr 2023 04:52:33 -0700 Revertron @.***> wrote:

But it works from Firefox without credentials. Should work from Yggdrasil, no?

it may be that firefox will try to use empty user/pass if it rejects anon socks5, which would be rich af to see other people work around shitty bugs like this.

-- ~jeff

[Vort]

Maybe you want to try setting SocksPort 9050 PreferSOCKSNoAuth in torrc.

[0Flag]

Also I2P connections stopped working with error: Failed to dial SOCKS localhost:4449: socks connect tcp localhost:4449->xmgzqfidm3zn4y3vfljqiuyfxorifntjca3rfnwv3dbbfcrx4uca.b32.i2p:30112: EOF. Tor and I2P connections worked fine for 0.4.4. It seems there was a refactoring from 0.4.4 to 0.4.5 which borked the socks connections.

[Vort]

I2P network is under attack now by the way. Not sure if it is related to proxy problem however.

[0Flag]

I2P network is under attack now by the way. Not sure if it is related to proxy problem however.

True, but that's not the issue. I can connect to I2P peers right now with V 0.4.4

[neilalexander]

Is this still an issue?

[r4sas]

Is this still an issue?

Yes.

add: users say sockstls solves that issue.