Closed aggieben closed 5 years ago
Looks like this isn't specific to Zap. Crossposted here: https://github.com/lightningnetwork/lnd/issues/2614
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.
I'm running the latest beta of lnd on Windows 10 (v1809, build 17763.253)
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:
If I try connecting to port 8080, it also times out, but the Lnd console reports a TLD handshake error:
For the search index:
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.