Skip to content
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

Allow local monerod server when using Socks5 proxy #4027

Closed
zquestz opened this issue Sep 9, 2022 · 3 comments · Fixed by #4085
Closed

Allow local monerod server when using Socks5 proxy #4027

zquestz opened this issue Sep 9, 2022 · 3 comments · Fixed by #4085

Comments

@zquestz
Copy link

zquestz commented Sep 9, 2022

Currently there is no way to connect to a local monerod instance and have all other connections go over the Socks5 proxy. When the Socks5 proxy is set, you lose connection to your local node. Many users will want to make sure price discovery is happening over Tor, and that is not currently possible when connecting to your own local monerod instance.

image

Ideally we can add a check box that allows it to bypass the proxy for local connections.

image

I wouldn't mind looking into adding it, as long as that is something that would be accepted.

@zquestz zquestz changed the title Allow local monerod server when using socks proxy Allow local monerod server when using Socks5 proxy Sep 9, 2022
@plowsof
Copy link
Contributor

plowsof commented Dec 18, 2022

Confirmed issue:

  • ./monerod
  • point wallet at localhost:18081 (connected)
  • enable socks5 proxy
  • note the disconnection from localnode
    Some problems at connect, message: Socks request rejected or failed

@selsta
Copy link
Collaborator

selsta commented Dec 18, 2022

This does work by selecting "Local node" inside Settings -> Node with socks5 proxy enabled.

@plowsof
Copy link
Contributor

plowsof commented Dec 18, 2022

Confirmed this fixes the problem, thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants