-
Notifications
You must be signed in to change notification settings - Fork 230
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Connection through Tor/Socks5 doesn't work #1028
Comments
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. |
But it works from Firefox without credentials. Should work from Yggdrasil, no? |
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
|
Maybe you want to try setting |
Also I2P connections stopped working with error: |
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 |
Is this still an issue? |
Yes. add: users say sockstls solves that issue. |
If you try to add something like
socks://127.0.0.1:9050/ygg.mkg20001.io:80
into peers you will getinvalid 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.
The text was updated successfully, but these errors were encountered: