Closed andrei-21 closed 2 years ago
Thanks for the contribution!
Did you tested locally?
I'm having trouble connecting to it still.
Can you provide a minimal dockerfile that tries to connect to LND?
Did you tested locally?
I'm having trouble connecting to it still.
Can you provide a minimal dockerfile that tries to connect to LND?
Sure. Without the patch:
$ ./build/nigiri-linux-amd64 --datadir=data start --ln
$ docker run -it --rm --network nigiri --volume $PWD/data:/data networld/grpcurl ./grpcurl lnd:10009 list
Failed to dial target host "lnd:10009": x509: certificate is valid for 3a465453271a, localhost, unix, unixpacket, bufconn, not lnd
With the patch:
$ ./build/nigiri-linux-amd64 --datadir=data stop --delete
$ ./build/nigiri-linux-amd64 --datadir=data start --ln
$ docker run -it --rm --network nigiri --volume $PWD/data:/data networld/grpcurl ./grpcurl lnd:10009 list
Failed to dial target host "lnd:10009": x509: certificate signed by unknown authority
# And providing the certificate.
$ docker run -it --rm --network nigiri --volume $PWD/data:/data networld/grpcurl ./grpcurl -cacert /data/volumes/lnd/tls.cert lnd:10009 list
Failed to list services: server does not support the reflection API
Please note that LND does not issue a new certificate if there is an old one even if a configuration has changed.
https://github.com/vulpemventures/nigiri/releases/tag/v0.4.4
Thanks for your contribution @andrei-21
To allow to extend nigiri setup and allow RPC connections to LND from other containers
lnd
domain has to be added for a TLS certificate.A new certificate will have
DNS:lnd
: