Closed alevchuk closed 5 years ago
hmm, maybe i'm missing some config in my lnd server. When I try the same with lncli
I get:
[lncli] rpc error: code = Unavailable desc = all SubConns are in TransientFailure, latest connection error: connection error: desc = "transport: authentication handshake failed: x509:
certificate is valid for bl3, localhost, unix, unixpacket,
not ec2-34-123-123-123.us-west-2.compute.amazonaws.com"
Ok, I got it to work.
I had to do the following:
To LND config add:
rpclisten=0.0.0.0:10009
tlsextradomain=ec2-34-123-123-123.us-west-2.compute.amazonaws.com
Delete ~/.lnd/tls.*
files
Restart LND and copy ~/.lnd/tls.cert
to the client host.
Maybe this should be added to documentation on how to get TLS to work on a remote host.
Yeah I ran it to this the first time running on a remote host to - glad you figured it out. Maybe open a PR on the lnd repo to improve their docs if you have time.
I can add a note on the docs here too when I get a chance.
Cheers!
Hi, I'm trying to run:
and get this connection error:
same error when using an IP instead of the domain name.
Is there an additional step that needs to be done for TSL other then just copying over the "tls.cert" file?