From a126c91745c3413128722db2223499b4239f19e6 Mon Sep 17 00:00:00 2001 From: Max Vernon Date: Mon, 7 May 2018 23:29:20 -0500 Subject: [PATCH] docs/INSTALL: add advice for using 127.0.0.1 for bitcoind backend on Windows (#1195) Using localhost to connect lnd to bitcoind on Windows is very slow. Use 127.0.0.1 instead. --- docs/INSTALL.md | 1 + 1 file changed, 1 insertion(+) diff --git a/docs/INSTALL.md b/docs/INSTALL.md index bd39a4409..9502b2b26 100644 --- a/docs/INSTALL.md +++ b/docs/INSTALL.md @@ -244,6 +244,7 @@ lnd --bitcoin.active --bitcoin.testnet --debuglevel=debug --bitcoin.node=bitcoin - 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. - If you DO choose to explicitly pass the auth parameters in your `lnd.conf` or command line options for `lnd` (`bitcoind.rpcuser` and `bitcoind.rpcpass` as shown in example command above), you must also specify the `bitcoind.zmqpath` option. Otherwise, `lnd` will attempt to get the configuration from your `bitcoin.conf`. - You must ensure the same address (including port) is used for the `bitcoind.zmqpath` option passed to `lnd` as for the `zmqpubrawblock` and `zmqpubrawtx` passed in the `bitcoind` options. +- When running lnd and bitcoind on the same Windows machine, ensure you use 127.0.0.1, not localhost, for all configuration options that require a TCP/IP host address. If you use "localhost" as the host name, you may see extremely slow inter-process-communication between lnd and the bitcoind backend. If lnd is experiencing this issue, you'll see "Waiting for chain backend to finish sync, start_height=XXXXXX" as the last entry in the console or log output, and lnd will appear to hang. Normal lnd output will quickly show multiple messages like this as lnd consumes blocks from bitcoind. #### Disabling Wallet Encryption