-
Notifications
You must be signed in to change notification settings - Fork 44
Proxy socks5 support #496
Comments
Please correct me if I'm wrong but it seems that you're using electron and it could support proxy by starting the app from CLI with https://www.electronjs.org/docs/latest/api/command-line-switches#--proxy-serveraddressport |
It's seems that the application accept Just found this https://www.npmjs.com/package/electron-proxy-agent |
So yes, using |
For appimage it works well too |
@sven-hash @polto We would greatly appreciate if you could test the latest RC with SOCKS5 proxy support: https://github.com/alephium/desktop-wallet/releases/tag/untagged-53d71f8e51fb98c48e49 Go to settings > network to set your proxy URL. Please share here any issue that you may encounter. Thanks 🙏 |
FYI, this is a draft release and only those with access to the repo can access it I think. |
My feedback @mvaivre 1 - I couldn't get it to work. As soon as I activate the Nym Connect, I then go in the network settings, activate custom URLs and then input the values (127.0.0.1 - 1080) then press "save", the wallet reloads, and stays stuck like this: At some point the "couldn't connect" error message appears, and the barred wifi symbol is shown up there. 2 - When switching networks (testnet/mainnet) it disconnects from the proxy (and you'd have to manually enter it again) 3 - Option to save proxy config Everytime I have to input the values again - maybe it'd be cool to have a way to save proxies (for future use). 4 - It keeps the proxy settings when i shut down and open the app again, that's cool. |
@VDAODAO your NYM connect is running on the phone and the desktop wallet ... well on the desktop. The 127.0.0.1 is an address only available locally, not across devices. |
Both NYM connect and the desktop wallet are running on the… desktop here :)I probably did something wrong, but it’s not that :)Sent from my iPhoneOn 22 Jun 2023, at 18:45, polto ***@***.***> wrote:
@VDAODAO your NYM connect is running on the phone and the desktop wallet ... well on the desktop. The 127.0.0.1 is an address only available locally, not across devices.
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you were mentioned.Message ID: ***@***.***>
|
If you want to test the wallet trough you will need to use a specific service provider for Nym connect. You can use ours, it already whitelist alephium domain ( Check the screen capture on how to set it. Just type And then connect, normally it should work If anybody want to drop me the alephium wallet I can test it (I've got a 404 when trying to access the release) |
@VDAODAO sorry, because of the look, I thought it was a mobile app. :) |
It works when I do as @sven-hash says. Rest of my points stand: 2 - When switching networks (testnet/mainnet) it disconnects from the proxy (without you knowing) and you'd have to manually enter it again. (maybe we need a small icon on top that tells you when you are (or not) protected, as Little snitch does for example. 3 - Option to save proxy config, that'd be nice to have. 4 - It keeps the proxy settings when i shut down and open the app again, that's cool. Thanks @mvaivre @nop33 for the cool feature. Thanks @polto @sven-hash for your help, pardon the beotian! Sadly testing beyond that (if and how the packets are effectively anon), I can't help :) |
Merged in |
Is your feature request related to a problem? Please describe.
It could be nice to support proxy socks5 to add a privacy layer at network level by using Tor (i2p or Nym) for example, and it could enable user without connections restriction to Internet to use the wallet
Describe the solution you'd like
Add the possibility to set a menu where the user could set a proxy socks5 address and port. A connectivity test might be nice but not necessary
Describe alternatives you've considered
The user could set a proxy for the whole system but it's not really a solution since it will forces all the connections to go trough
Additional context
Add any other context or screenshots about the feature request here.
The text was updated successfully, but these errors were encountered: