LND is locked. Lightning Wallet don`t run

Hello,
I need help. My Lightning wallet is locked. Channels are offline a few Days.
Can someone explain to me, what i should do?

My Troubleshooting:

LND logs

Attaching to lnd
lnd | 2021-10-04 10:05:20.130 [ERR] RPCS: [/lnrpc.Lightning/GetTransactions]: wallet locked, unlock it to enable full RPC access
lnd | 2021-10-04 10:05:20.130 [ERR] RPCS: [/lnrpc.Lightning/WalletBalance]: wallet locked, unlock it to enable full RPC access
lnd | 2021-10-04 10:05:20.146 [ERR] RPCS: [/lnrpc.Lightning/ListInvoices]: wallet locked, unlock it to enable full RPC access
lnd | 2021-10-04 10:05:20.147 [ERR] RPCS: [/lnrpc.Lightning/GetInfo]: wallet locked, unlock it to enable full RPC access
lnd | 2021-10-04 10:05:20.161 [ERR] RPCS: [/lnrpc.Lightning/ListChannels]: wallet locked, unlock it to enable full RPC access
lnd | 2021-10-04 10:05:20.179 [ERR] RPCS: [/lnrpc.Lightning/PendingChannels]: wallet locked, unlock it to enable full RPC access
lnd | 2021-10-04 10:05:20.376 [ERR] RPCS: [/lnrpc.Lightning/ListPayments]: wallet locked, unlock it to enable full RPC access
lnd | 2021-10-04 10:05:20.803 [ERR] RPCS: [/lnrpc.Lightning/GetInfo]: wallet locked, unlock it to enable full RPC access
lnd | 2021-10-04 10:05:21.129 [ERR] RPCS: [/lnrpc.Lightning/GetInfo]: wallet locked, unlock it to enable full RPC access
lnd | 2021-10-04 10:05:22.292 [ERR] RPCS: [/lnrpc.Lightning/GetInfo]: wallet locked, unlock it to enable full RPC access
lnd | 2021-10-04 10:05:24.204 [ERR] RPCS: [/lnrpc.Lightning/GetInfo]: wallet locked, unlock it to enable full RPC access
lnd | 2021-10-04 10:05:24.456 [ERR] RPCS: [/lnrpc.Lightning/GetInfo]: wallet locked, unlock it to enable full RPC access
lnd | 2021-10-04 10:05:24.527 [ERR] RPCS: [/lnrpc.Lightning/GetInfo]: wallet locked, unlock it to enable full RPC access
lnd | 2021-10-04 10:05:26.136 [ERR] RPCS: [/lnrpc.Lightning/GetInfo]: wallet locked, unlock it to enable full RPC access
lnd | 2021-10-04 10:05:26.980 [ERR] RPCS: [/lnrpc.Lightning/GetInfo]: wallet locked, unlock it to enable full RPC access
lnd | 2021-10-04 10:05:27.226 [INF] LNWL: Opened wallet
lnd | 2021-10-04 10:05:27.452 [INF] CHRE: Primary chain is set to: bitcoin
lnd | 2021-10-04 10:05:27.480 [INF] CHRE: Initializing bitcoind backed fee estimator in CONSERVATIVE mode
lnd | 2021-10-04 10:05:27.481 [INF] LNWL: Started listening for bitcoind block notifications via ZMQ on 10.21.21.8:28332
lnd | 2021-10-04 10:05:27.486 [INF] LNWL: Started listening for bitcoind transaction notifications via ZMQ on 10.21.21.8:28333
lnd | 2021-10-04 10:05:30.198 [INF] LNWL: The wallet has been unlocked without a time limit
lnd | 2021-10-04 10:05:30.207 [INF] CHRE: LightningWallet opened
lnd | 2021-10-04 10:05:30.211 [INF] SRVR: Proxying all network traffic via Tor (stream_isolation=false)! NOTE: Ensure the backend node is proxying over Tor as well
lnd | 2021-10-04 10:05:30.219 [INF] HSWC: Restoring in-memory circuit state from disk
lnd | 2021-10-04 10:05:30.220 [INF] HSWC: Payment circuits loaded: num_pending=0, num_open=0
lnd | 2021-10-04 10:05:30.224 [INF] HSWC: Trimming open circuits for chan_id=702311:1456:1, start_htlc_id=1
lnd | 2021-10-04 10:05:30.225 [INF] HSWC: Trimming open circuits for chan_id=702310:1130:0, start_htlc_id=0
lnd | 2021-10-04 10:05:30.264 [INF] LTND: Channel backup proxy channel notifier starting
lnd | 2021-10-04 10:05:30.265 [INF] ATPL: Instantiating autopilot with active=false, max_channels=5, allocation=0.600000, min_chan_size=20000, max_chan_size=16777215, private=false, min_confs=1, conf_target=3
lnd | 2021-10-04 10:05:30.277 [INF] LTND: Waiting for chain backend to finish sync, start_height=703487

Tor logs

Attaching to tor
tor | Oct 04 09:35:00.000 [notice] New control connection opened from 10.21.21.9.
tor | Oct 04 09:36:02.000 [notice] New control connection opened from 10.21.21.9.
tor | Oct 04 09:37:06.000 [notice] New control connection opened from 10.21.21.9.
tor | Oct 04 09:38:09.000 [notice] New control connection opened from 10.21.21.9.
tor | Oct 04 09:39:12.000 [notice] New control connection opened from 10.21.21.9.
tor | Oct 04 09:40:15.000 [notice] New control connection opened from 10.21.21.9.
tor | Oct 04 09:41:18.000 [notice] New control connection opened from 10.21.21.9.
tor | Oct 04 09:42:21.000 [notice] New control connection opened from 10.21.21.9.
tor | Oct 04 09:43:24.000 [notice] New control connection opened from 10.21.21.9.
tor | Oct 04 09:44:27.000 [notice] New control connection opened from 10.21.21.9.
tor | Oct 04 09:45:31.000 [notice] New control connection opened from 10.21.21.9.
tor | Oct 04 09:46:34.000 [notice] New control connection opened from 10.21.21.9.
tor | Oct 04 09:47:36.000 [notice] New control connection opened from 10.21.21.9.
tor | Oct 04 09:48:40.000 [notice] New control connection opened from 10.21.21.9.
tor | Oct 04 09:49:43.000 [notice] New control connection opened from 10.21.21.9.
tor | Oct 04 09:50:46.000 [notice] New control connection opened from 10.21.21.9.
tor | Oct 04 09:51:49.000 [notice] New control connection opened from 10.21.21.9.
tor | Oct 04 09:52:52.000 [notice] New control connection opened from 10.21.21.9.
tor | Oct 04 09:53:55.000 [notice] New control connection opened from 10.21.21.9.
tor | Oct 04 09:54:58.000 [notice] New control connection opened from 10.21.21.9.
tor | Oct 04 09:56:01.000 [notice] New control connection opened from 10.21.21.9.
tor | Oct 04 09:57:04.000 [notice] New control connection opened from 10.21.21.9.
tor | Oct 04 09:58:08.000 [notice] New control connection opened from 10.21.21.9.
tor | Oct 04 09:59:11.000 [notice] New control connection opened from 10.21.21.9.
tor | Oct 04 10:00:14.000 [notice] New control connection opened from 10.21.21.9.
tor | Oct 04 10:01:17.000 [notice] New control connection opened from 10.21.21.9.
tor | Oct 04 10:02:21.000 [notice] New control connection opened from 10.21.21.9.
tor | Oct 04 10:03:24.000 [notice] New control connection opened from 10.21.21.9.
tor | Oct 04 10:04:27.000 [notice] New control connection opened from 10.21.21.9.
tor | Oct 04 10:05:30.000 [notice] New control connection opened from 10.21.21.9.

lightning-terminal

web_1 | 2021-10-04 10:04:31.421 [INF] LNDC: lnd version: v0.13.1-beta, build tags ‘autopilotrpc,signrpc,walletrpc,chainrpc,invoicesrpc,watchtowerrpc,monitoring’
web_1 | 2021-10-04 10:04:31.421 [INF] LNDC: Using network mainnet
web_1 | 2021-10-04 10:04:31.422 [INF] LNDC: Waiting for lnd to be fully synced to its chain backend, this might take a while
web_1 | 2021-10-04 10:05:11.342 [WRN] GRPC: grpc: addrConn.createTransport failed to connect to {10.21.21.9:10009 0 }. Err: connection error: desc = “transport: authentication handshake failed: read tcp 10.21.21.17:33686->10.21.21.9:10009: read: connection reset by peer”. Reconnecting…
web_1 | 2021-10-04 10:05:11.343 [WRN] GRPC: grpc: addrConn.createTransport failed to connect to {10.21.21.9:10009 0 }. Err: connection error: desc = “transport: authentication handshake failed: read tcp 10.21.21.17:33692->10.21.21.9:10009: read: connection reset by peer”. Reconnecting…
web_1 | 2021-10-04 10:05:11.343 [WRN] GRPC: grpc: addrConn.createTransport failed to connect to {10.21.21.9:10009 0 }. Err: connection error: desc = “transport: authentication handshake failed: read tcp 10.21.21.17:33688->10.21.21.9:10009: read: connection reset by peer”. Reconnecting…
web_1 | 2021-10-04 10:05:11.343 [WRN] GRPC: grpc: addrConn.createTransport failed to connect to {10.21.21.9:10009 0 }. Err: connection error: desc = “transport: authentication handshake failed: read tcp 10.21.21.17:33690->10.21.21.9:10009: read: connection reset by peer”. Reconnecting…
web_1 | 2021-10-04 10:05:11.615 [ERR] LITD: Could not start subservers: error waiting for chain to be synced: error in GetInfo call: rpc error: code = Unavailable desc = connection error: desc = “transport: authentication handshake failed: read tcp 10.21.21.17:33690->10.21.21.9:10009: read: connection reset by peer”
web_1 | error waiting for chain to be synced: error in GetInfo call: rpc error: code = Unavailable desc = connection error: desc = “transport: authentication handshake failed: read tcp 10.21.21.17:33690->10.21.21.9:10009: read: connection reset by peer”
web_1 | 2021-10-04 10:05:11.616 [INF] SGNL: Received shutdown request.
web_1 | 2021-10-04 10:05:14.614 [INF] LITD: Dialing lnd gRPC server at 10.21.21.9:10009
web_1 | 2021-10-04 10:05:14.659 [INF] LITD: Listening for http_tls on: 127.0.0.1:8443
web_1 | 2021-10-04 10:05:14.660 [INF] LITD: Listening for http on: [::]:3004
web_1 | 2021-10-04 10:05:15.892 [WRN] GRPC: grpc: addrConn.createTransport failed to connect to {10.21.21.9:10009 0 }. Err: connection error: desc = “transport: Error while dialing dial tcp 10.21.21.9:10009: connect: connection refused”. Reconnecting…
web_1 | 2021-10-04 10:05:15.892 [WRN] GRPC: grpc: addrConn.createTransport failed to connect to {10.21.21.9:10009 0 }. Err: connection error: desc = “transport: Error while dialing dial tcp 10.21.21.9:10009: connect: connection refused”. Reconnecting…
web_1 | ----------------------------------------------------------
web_1 | Lightning Terminal (LiT) by Lightning Labs
web_1 |
web_1 | Operating mode remote
web_1 | Node status locked
web_1 | Alias ??? (node is locked)
web_1 | Version ??? (node is locked)
web_1 | Web interface 127.0.0.1:8443, 0.0.0.0:3004 (open https://127.0.0.1:8443 or http://localhost:3004 in your browser)
web_1 | ----------------------------------------------------------
web_1 | 2021-10-04 10:05:16.094 [INF] LNDC: Creating lnd connection to 10.21.21.9:10009
web_1 | 2021-10-04 10:05:16.095 [INF] LNDC: Connected to lnd
web_1 | 2021-10-04 10:05:16.095 [INF] LNDC: Waiting for lnd to unlock
web_1 | 2021-10-04 10:05:31.163 [INF] LNDC: lnd version: v0.13.1-beta, build tags ‘autopilotrpc,signrpc,walletrpc,chainrpc,invoicesrpc,watchtowerrpc,monitoring’
web_1 | 2021-10-04 10:05:31.163 [INF] LNDC: Using network mainnet
web_1 | 2021-10-04 10:05:31.163 [INF] LNDC: Waiting for lnd to be fully synced to its chain backend, this might take a while

@mayank or @lukechilds please can you assist with unlocking wallet procedure?

1 Like

Nobody who wants to help me?

Sorry for the delay @Lord_of_Waringham, @louneskmt are you able to take a look at this?

1 Like

Nobody who wants to help me?

I wish I would have all the info about unlocking the wallet, but I don’t have it and this is a very delicate situation.
You better wait the answer from @mayank or contact him in the Telegram group @getumbrel

1 Like

Responded on Telegram :grin:

Can you send the link. I have the same problem.

Thx

Lounès K:
Hey there

Can you try to unlock it manually?

You need first to ssh into your Pi. Open a terminal (Powershell on Windows, Terminal app on macOS) and execute:

ssh -t umbrel@umbrel.local

The prompted password is your dashboard password.

Then execute:

cd ~/umbrel && docker-compose exec lnd /bin/bash

Then:

lncli unlock

When prompted, enter the password “moneyprintergobrrr” (without quotes)

1 Like

There are many you tube videos for ssh connection to your pi. I will try it at monday.

Yes I tried that and it says lnd successfully unlocked! but when I ran the log, it still says locked

umbrel@umbrel:~ $ cd ~/umbrel && docker-compose exec lnd /bin/bash
bash-5.1$ lncli unlock
Input wallet password:

lnd successfully unlocked!
bash-5.1$ umbrel@umbrel:~/umbrel $

umbrel-1633715924557-debug.log (20.2 KB)

In the log, I see a lot of “ThreadRPCServer incorrect password attempt from 10.21.21.9:39002”

I don’t know if that has something to do with the problem

Talk to them via telegram

Problem: Incli unlock not found.

These should be 2 separate commands

  1. cd ~/umbrel
  2. docker-compose exec lnd /bin/bash

1 Like

Now i login the passwort: moneyprintergobrrr
But i have an rpc error. Where is the problem?

1 Like

Do you see the Problem in the LND Logs?!

1 Like

1 Like

1 Like