<p>Found out that any bitcoind.XXX options need to be under a [Bitcoind] heading. Working lnd.conf is as follows:</p>

<pre><code>[Application Options]
debuglevel=info
debughtlc=false
maxpendingchannels=5
alias=WittyAlias
color=#000300
maxlogfiles=3

[Bitcoin]
bitcoin.active=1
bitcoin.node=bitcoind
bitcoin.mainnet=1

[autopilot]
autopilot.active=1
autopilot.maxchannels=16
autopilot.allocation=0.1

[Bitcoind]
bitcoind.rpchost=127.0.0.1:8332
bitcoind.rpcuser=wittyusername
bitcoind.rpcpass=VerySecretSuperDuperRPCauthPassword
bitcoind.zmqpubrawblock=127.0.0.1:28332
bitcoind.zmqpubrawtx=127.0.0.1:28333
</code></pre>

CC BY-SA 4.0
2018-11-17T00:12:23.913Z
2018-11-17T00:12:23.913Z
Mike
<p>I run lnd and bitcoind under their own users, but on the same physical machine. This means lnd has trouble accessing the bitcoind .cookie, so I'm trying to configure lnd to use RPC. </p>

<p>When I use the following options in my lnd.conf as described in the lnd <a href="https://github.com/lightningnetwork/lnd/blob/master/sample-lnd.conf" rel="nofollow noreferrer">documentation</a>:</p>

<pre><code>bitcoind.rpchost=127.0.0.1:8332
bitcoind.rpcuser=joeblow
bitcoind.rpcpass=superSecretPasswordByRPAUTH.py
bitcoind.zmqpubrawblock=127.0.0.1:28332
bitcoind.zmqpubrawtx=127.0.0.1:28333
</code></pre>

<p>lnd errors out with the following error:</p>

<pre><code>lnd.conf:16: unknown option: bitcoind.rpchost
</code></pre>

<p>lnd runs fine if I specify the above options using the command line like this:</p>

<pre><code>lnd -bitcoind.rpchost=127.0.0.1:8332 -bitcoind.rpcuser=joeblow ... etc
</code></pre>

<p>This means typing in the RPC password in the command-line and command-line options can be seen by users running 'top' or task manager. This exposes RPC password to users other than 'lnd.' Having RPC password in lnd.conf is moderately more secure because the file can be locked down with chmod.</p>

<bitcoind><lightning-network-daemon>
lightning daemon rejects bitcoind RPC variables in lnd.conf
Mike
# lightning daemon rejects bitcoind RPC variables in lnd.conf

(Asked by: username_0 on 2018-11-03)

I run lnd and bitcoind under their own users, but on the same physical machine. This means lnd has trouble accessing the bitcoind .cookie, so I'm trying to configure lnd to use RPC.

When I use the following options in my lnd.conf as described in the lnd [documentation](https://github.com/lightningnetwork/lnd/blob/master/sample-lnd.conf):

```
bitcoind.rpchost=127.0.0.1:8332
bitcoind.rpcuser=joeblow
bitcoind.rpcpass=superSecretPasswordByRPAUTH.py
bitcoind.zmqpubrawblock=127.0.0.1:28332
bitcoind.zmqpubrawtx=127.0.0.1:28333

```

lnd errors out with the following error:

```
lnd.conf:16: unknown option: bitcoind.rpchost

```

lnd runs fine if I specify the above options using the command line like this:

```
lnd -bitcoind.rpchost=127.0.0.1:8332 -bitcoind.rpcuser=joeblow ... etc

```

This means typing in the RPC password in the command-line and command-line options can be seen by users running 'top' or task manager. This exposes RPC password to users other than 'lnd.' Having RPC password in lnd.conf is moderately more secure because the file can be locked down with chmod.

**Tags:** bitcoind, lightning-network-daemon


---

## 1 answers

### Answer by username_0 on 2018-11-17. Score: 4 | Accepted answer

Found out that any bitcoind.XXX options need to be under a [Bitcoind] heading. Working lnd.conf is as follows:

```
[Application Options]
debuglevel=info
debughtlc=false
maxpendingchannels=5
alias=WittyAlias
color=#000300
maxlogfiles=3

[Bitcoin]
bitcoin.active=1
bitcoin.node=bitcoind
bitcoin.mainnet=1

[autopilot]
autopilot.active=1
autopilot.maxchannels=16
autopilot.allocation=0.1

[Bitcoind]
bitcoind.rpchost=127.0.0.1:8332
bitcoind.rpcuser=wittyusername
bitcoind.rpcpass=VerySecretSuperDuperRPCauthPassword
bitcoind.zmqpubrawblock=127.0.0.1:28332
bitcoind.zmqpubrawtx=127.0.0.1:28333

```


---

