You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hello, same as other wallets, Electrum, Sparrow, etc, this is a request to add a new feature to Nunchuk Android on Network settings
After testing the Electrum server connection using the SSL port to a secure connection it doesn't work:
I suggest the following features:
Enable compatibility with a secure connection to a personal Electrum Server using SSL
Obtain the SSL certificate automatically without the need to transfer it manually from the server
Enable availability to connect to Electrum Servers using its onion address Tor, integrating a Tor instance on the Nunchuk app or in conjunction with Orbot app (SSL not needed)
Thanks!
The text was updated successfully, but these errors were encountered:
twofaktor
changed the title
[FEATURE REQUEST] Enable Electrum server SSL connection with automatic get SSL certificate
[FEATURE REQUEST] Enable Electrum server SSL connection with automatic get SSL certificate + onion Tor address connection
Nov 24, 2023
You can actually use SSL, somebody once told me the trick was to write the URL as ssl://ADDRESS:PORT. Unfortunately I can't give credit because I forget who mentioned it. Tor support would be nice though.
You can actually use SSL, somebody once told me the trick was to write the URL as ssl://ADDRESS:PORT. Unfortunately I can't give credit because I forget who mentioned it. Tor support would be nice though.
Ok, I solved it by using your tip, but I think this shouldn't be a hidden feature, it is much better to use a special and dedicated switch to enable this feature.
Hello, same as other wallets, Electrum, Sparrow, etc, this is a request to add a new feature to Nunchuk Android on Network settings
After testing the Electrum server connection using the SSL port to a secure connection it doesn't work:
I suggest the following features:
Thanks!
The text was updated successfully, but these errors were encountered: