LN-Zap / zap-desktop

Zap Wallet - Cross platform Lightning Network wallet focused on user experience and ease of use ⚡️
MIT License
1.28k stars 216 forks source link

TLS handshake error: no cipher suite supported by both client and server #1525

Closed aggieben closed 5 years ago

aggieben commented 5 years ago

I'm running the latest beta of lnd on Windows 10 (v1809, build 17763.253)

C:\Users\ben
λ  lnd --bitcoin.active --bitcoin.mainnet --bitcoin.node=bitcoind --bitcoind.dir=E:\Bitcoin --bitcoind.zmqpubrawblock=tcp://127.0.0.1:28332 --bitcoind.zmqpubrawtx=tcp://127.0.0.1:28333 --bitcoind.rpcuser=<snip> --bitcoind.rpcpass=<snip>
2019-02-06 17:54:13.887 [WRN] LTND: open C:\Users\ben\AppData\Local\Lnd\lnd.conf: The system cannot find the file specified.
2019-02-06 17:54:13.894 [INF] LTND: Version: 0.5.2-beta commit=v0.5.2-beta-rc7, build=production, logging=default
2019-02-06 17:54:13.894 [INF] LTND: Active chain: Bitcoin (network=mainnet)
2019-02-06 17:54:13.925 [INF] CHDB: Checking for schema update: latest_version=7, db_version=7
2019-02-06 17:54:13.936 [INF] RPCS: password RPC server listening on 127.0.0.1:10009
2019-02-06 17:54:13.936 [INF] RPCS: password gRPC proxy started at 127.0.0.1:8080
2019-02-06 17:54:13.936 [INF] LTND: Waiting for wallet encryption password. Use `lncli create` to create a wallet, `lncli unlock` to unlock an existing wallet, or `lncli changepassword` to change the password of an existing wallet and unlock it.

When I try running the latest Zap to connect on port 10009, it times out and I see nothing at all on the Lnd console: image

If I try connecting to port 8080, it also times out, but the Lnd console reports a TLD handshake error: image

For the search index:

2019/02/07 12:00:03 http: TLS handshake error from 127.0.0.1:32681: tls: no cipher suite supported by both client and server

Any ideas? One thing that isn't clear to me is if the RPC server listening on 10009 is the gRPC endpoint Zap wants, or if the "gRPC proxy" on 8080 is. I'm new to Lnd, so I'm not sure what the difference between these services are.

aggieben commented 5 years ago

Looks like this isn't specific to Zap. Crossposted here: https://github.com/lightningnetwork/lnd/issues/2614

mrfelton commented 5 years ago

Any ideas? One thing that isn't clear to me is if the RPC server listening on 10009 is the gRPC endpoint Zap wants, or if the "gRPC proxy" on 8080 is. I'm new to Lnd, so I'm not sure what the difference between these services are.

gRPC listens on port 10009. A REST interface is exposed on port 8080 (this is just a proxy to the rpc interface)

I'm going to close this issue since it sounds like you have this resolved now based on your comments over in the other issue that you created.