Setup LND within Docker, Startupfailure wallet shutting down

[toconspiracy]

I have tried to start LND with the Dockerimage provided by the Repo via Dockerhub. The Bitcinchain is synced an reachable over all related Ports, i still get below error on Startup:

2024-02-12 13:22:29.397 [INF] LTND: Version: 0.17.4-beta commit=v0.17.4-beta, build=production, logging=default, debuglevel=trace
2024-02-12 13:22:29.397 [INF] LTND: Active chain: Bitcoin (network=mainnet)
2024-02-12 13:22:29.397 [DBG] NRPC: Neutrino RPC server successfully register with root gRPC server
2024-02-12 13:22:29.397 [DBG] SGNR: Signer RPC server successfully register with root gRPC server
2024-02-12 13:22:29.397 [DBG] VRPC: Versioner RPC server successfully registered with root gRPC server
2024-02-12 13:22:29.397 [DBG] NTFR: ChainNotifier RPC server successfully register with root gRPC server
2024-02-12 13:22:29.397 [DBG] NTFR: ChainKit RPC server successfully register with root gRPC server
2024-02-12 13:22:29.397 [DBG] WLKT: WalletKit RPC server successfully registered with root gRPC server
2024-02-12 13:22:29.397 [DBG] ARPC: Autopilot RPC server successfully register with root gRPC server
2024-02-12 13:22:29.397 [DBG] IRPC: Invoices RPC server successfully registered with root gRPC server
2024-02-12 13:22:29.397 [DBG] RRPC: Router RPC server successfully register with root gRPC server
2024-02-12 13:22:29.397 [DBG] PRPC: Peers RPC server successfully register with root gRPC server
2024-02-12 13:22:29.397 [INF] RPCS: RPC server listening on 127.0.0.1:10009
2024-02-12 13:22:29.398 [DBG] NRPC: Neutrino REST server successfully registered with root REST server
2024-02-12 13:22:29.398 [DBG] SGNR: Signer REST server successfully registered with root REST server
2024-02-12 13:22:29.398 [DBG] VRPC: Versioner REST server successfully registered with root REST server
2024-02-12 13:22:29.398 [DBG] NTFR: ChainNotifier REST server successfully registered with root REST server
2024-02-12 13:22:29.398 [DBG] NTFR: ChainKit REST server successfully registered with root REST server
2024-02-12 13:22:29.399 [DBG] WLKT: WalletKit REST server successfully registered with root REST server
2024-02-12 13:22:29.399 [DBG] ARPC: Autopilot REST server successfully registered with root REST server
2024-02-12 13:22:29.399 [DBG] IRPC: Invoices REST server successfully registered with root REST server
2024-02-12 13:22:29.400 [DBG] RRPC: Router REST server successfully registered with root REST server
2024-02-12 13:22:29.400 [DBG] PRPC: Peers REST server successfully registered with root REST server
2024-02-12 13:22:29.400 [INF] RPCS: gRPC proxy started at 127.0.0.1:8080
2024-02-12 13:22:29.401 [INF] LTND: Opening the main database, this might take a few minutes...
2024-02-12 13:22:29.401 [INF] LTND: Opening bbolt database, sync_freelist=false, auto_compact=false
2024-02-12 13:22:29.401 [INF] LTND: Creating local graph and channel state DB instances
2024-02-12 13:22:29.907 [DBG] CHDB: Populating in-memory channel graph, this might take a while...
2024-02-12 13:22:29.907 [DBG] CHDB: Finished populating in-memory channel graph (took 39.72µs, num_node_features=0, num_nodes=0, num_channels=0)
2024-02-12 13:22:29.907 [INF] CHDB: Checking for schema update: latest_version=31, db_version=31
2024-02-12 13:22:29.907 [INF] CHDB: Checking for optional update: prune_revocation_log=false, db_version=empty
2024-02-12 13:22:30.049 [INF] LTND: Database(s) now open (time_to_open=648.784708ms)!
2024-02-12 13:22:30.049 [INF] LTND: We're not running within systemd or the service type is not 'notify'
2024-02-12 13:22:30.049 [INF] LTND: Waiting for wallet encryption password. Use lncli create to create a wallet, lncli unlock to unlock an existing wallet, or lncli changepassword to change the password of an existing wallet and unlock it.
2024-02-12 13:22:57.967 [DBG] RPCS: [/lnrpc.WalletUnlocker/UnlockWallet] requested
2024-02-12 13:22:59.957 [INF] LNWL: Opened wallet
2024-02-12 13:23:00.448 [INF] CHRE: Primary chain is set to: bitcoin
2024-02-12 13:23:18.870 [INF] LNWL: Started listening for bitcoind block notifications via ZMQ on 172.14.0.67:28332
2024-02-12 13:23:18.870 [INF] CHRE: Initializing bitcoind backed fee estimator in CONSERVATIVE mode
2024-02-12 13:23:18.870 [INF] LNWL: Started listening for bitcoind transaction notifications via ZMQ on 172.14.0.67:28333
2024-02-12 13:23:31.318 [INF] LNWL: The wallet has been unlocked without a time limit
2024-02-12 13:23:36.369 [INF] CHRE: LightningWallet opened
2024-02-12 13:23:36.369 [DBG] LNWL: Waiting for chain backend to sync to tip
2024-02-12 13:23:36.545 [INF] LNWL: Stopped waiting for wallet sync due to error: wallet shutting down
2024-02-12 13:23:36.546 [INF] LTND: Shutdown complete

I have also set the Loglevel to trace, unfortunately i do not get a clear direction where the Issue is, may someone have a idea what i can check further?

[guggero]

Can you check the lnd log file (or stderr if that's not printed to the default output in your Docker setup)? It's possible the actual error isn't logged to stdout for some reason.

[toconspiracy]

Thx, just checked the logfile itself, sadly there is not more output than above. DO you have any idea what exactly happens at that Step? That may give some hint where to look :)

[guggero]

It's usually a connection issue between lnd and bitcoind. So best to check IP addresses/hostnames and ports.

[toconspiracy]

Thats what i also think, so far i have checked following connections:

• RPC Host, Port 8332

8513c21e0f43:/# nc lnd-bitcoind 8332
HTTP/1.1 400 Bad Request

• zmqpubrawblock, Port 28332

8513c21e0f43:/# nc lnd-bitcoind 28332
��

• zmqpubrawtx, Port 8332

8513c21e0f43:/# nc lnd-bitcoind 28333
��

From all Ports i get a response, any connection i missed?

[toconspiracy]

I just dug a bit in the code and the logentries below seems to be generated by the used bitcoin wallet in context with neutrino:

2024-02-12 13:23:36.369 [DBG] LNWL: Waiting for chain backend to sync to tip
2024-02-12 13:23:36.545 [INF] LNWL: Stopped waiting for wallet sync due to error: wallet shutting down

https://github.com/btcsuite/btcwallet/blob/1f3534b00d1440cd6c7f4b68e7dedeeed51d3d84/wallet/wallet.go#L411
and
https://github.com/btcsuite/btcwallet/blob/1f3534b00d1440cd6c7f4b68e7dedeeed51d3d84/wallet/chainntfns.go#L155

This part shouldn't be executed anyways as i use bitcoind as backend.

[toconspiracy]

Well i was able to get it up&running. It seems it is related to Tor. For the config sharing i stripped it down to only the necessary stuff and it worked.

I found out (after testing each tor setting) that when i enable following setting the issue occures:

tor.skip-proxy-for-clearnet-targets=true

Working config:

[Application Options]
restlisten=:8080
externalip=###OBFUSCATED###
debuglevel=trace
wallet-unlock-password-file=/root/.lnd/pw.txt
wallet-unlock-allow-create=true
alias=###OBFUSCATED###

[prometheus]

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

[Btcd]

[Bitcoind]
bitcoind.dir=/.bitcoin
bitcoind.config=/.bitcoin/bitcoin.conf
bitcoind.rpccookie=/.bitcoin/.cookie
bitcoind.rpchost=lnd-bitcoind:8332
bitcoind.zmqpubrawblock=tcp://lnd-bitcoind:60601
bitcoind.zmqpubrawtx=tcp://lnd-bitcoind:60602
bitcoind.rpcpolling=false

[neutrino]

[autopilot]

[tor]

tor.active=true
tor.socks=lnd-torproxy:9050
tor.streamisolation=true
tor.control=lnd-torproxy:9051
tor.password=###OBFUSCATED###
tor.v3=true

[watchtower]
watchtower.active=true
watchtower.listen=0.0.0.0:9911
watchtower.externalip=###OBFUSCATED###

[wtclient]
wtclient.active=true

[healthcheck]

[signrpc]

[walletrpc]

[chainrpc]

[routerrpc]

[workers]

[caches]

[protocol]

[db]

[etcd]

[postgres]

[sqlite]

[bolt]

[cluster]

[rpcmiddleware]
rpcmiddleware.enable=true

[remotesigner]

[gossip]

[invoices]

[routing]

[sweeper]

[htlcswitch]

[grpc]

[guggero]

Did you use the sample config as the template? We've had some weird issues with that, the config parser library we use is a bit wonky at times. Can you try if you have the same issue if you create a config that only contains the actual values you need? With all the empty section headers removed?
I don't see how the Tor option could make a difference. So perhaps it's a red herring?

[toconspiracy]

Yes indeed i used the sample config. I have now removed all unecessary blocks, but still same behaviour. When tor.skip-proxy-for-clearnet-targets=true is configured, it wont work, if its set to false, then it is fine.

[toconspiracy]

Ok, i found the culprit after reading following issue: #6005

I also had tor.streamisolation=true enabled together with proxy-for-clearnet-targets=true which does not work. It might be a good Idea if LND reports that mismatch clearly in the logoutput ;)