1

I configured bitcoind RPC to authenticate clients with an authentication cookie. However I cant figure out if it's possible to use this method with lnd while connecting to bitcoind RPC.

I would like to clarify that I'm running bitcoind and lnd in two separated docker containers that share a volume where bitcoind save the authentication cookie. The problem is that lnd doesn't allow to specify the folder in which it could find the cookie... In bitcoin.conf for exemple you can specify the path where you can find the authentication cookie of the tor control port for example...

Someone knows how to do this in lnd ? Is it possible ?

Thank you!

2

It is supported according to the LND installation guide

NOTE:

The auth parameters rpcuser and rpcpass parameters can typically be determined by lnd for a bitcoind instance running under the same user, including when using cookie auth. In this case, you can exclude them from the lnd options entirely.

  • I'm running bitcoind and lnd in two separated docker containers that share a volume where bitcoind save the authentication cookie. The problem is that lnd doesn't allow to specify the folder in which it could find the cookie... In bitcoin.conf for exemple you can specify the path where you can find the authentication cookie of the tor control port... – Zighy Blue Nov 25 '19 at 20:54

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.