question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

LiT crashes after LND has changed wallet password

See original GitHub issue

If you change the wallet password in LND then LiT will display the error oops, that password is incorrect when trying to log in with a password and then the LiT daemon will crash.

It doesn’t seem to be any sort of issue with password authentication since the config has not changed and the same password is being entered. It seems like something else errors and is swallowed and this password error is what’s returned.

I’m not sure if this is a bug in LiT or LND but either way it would be great if the error could be handled in LiT to make it more clear what’s going on.

Once in this state even if you completely uninstall LiT and reinstall it, nuking all data directories, the issue persists. However if you reinstall LND and nuke it’s data directories and then create a new wallet, then the issue is resolved.

So it seems like changing the LND password is putting LND in a strange state that LND itself can still run in but LiT errors out.

Attached LiT logs below:

[INF] LITD: Dialing lnd gRPC server at 10.21.21.9:10009
[INF] LITD: Listening for http_tls on: 127.0.0.1:8443
[INF] LITD: Listening for http on: [::]:3004
----------------------------------------------------------
 Lightning Terminal (LiT) by Lightning Labs               
                                                          
 Operating mode      remote                                   
 Node status         online                                   
 Alias               02d561a482b9ddd1b492                                   
 Version             0.11.1-beta commit=v0.11.1-beta                                   
 Web interface       https://127.0.0.1:8443, http://localhost:3004                                   
----------------------------------------------------------
[INF] LNDC: Creating lnd connection to 10.21.21.9:10009
[INF] LNDC: Connected to lnd
[INF] LNDC: lnd version: v0.11.1-beta, build tags 'autopilotrpc,signrpc,walletrpc,chainrpc,invoicesrpc,watchtowerrpc'
[INF] LNDC: Using network mainnet
[INF] LNDC: Waiting for lnd to be fully synced to its chain backend, this might take a while
[INF] LNDC: lnd is now fully synced to its chain backend
[INF] LOOPD: Swap server address: swap.lightning.today:11010
[INF] STORE: Checking for schema update: latest_version=4, db_version=4
[INF] LLMD: Version: 0.3.4-alpha commit=
[INF] LOOPD: Starting liquidity manager
[INF] LOOPD: Waiting for updates
[INF] LOOPD: Starting swap client
[INF] LOOP: Connected to lnd node '02d561a482b9ddd1b492' with pubkey 02d561a482b9ddd1b492f208ab72275b73eb57f7f9e9fd6b76521f3e0d524b0f23 (version v0.11.1-beta, build tags 'autopilotrpc,signrpc,walletrpc,chainrpc,invoicesrpc,watchtowerrpc')
[INF] LOOP: Wait for first block ntfn
[ERR] LOOP: Swap client terminating: rpc error: code = Unknown desc = verification failed: signature mismatch after caveat verification
[INF] LOOP: Swap client terminated
[INF] LOOPD: Swap client stopped
[ERR] LOOPD: Runtime error in daemon, shutting down: rpc error: code = Unknown desc = verification failed: signature mismatch after caveat verification
[INF] LOOPD: Stopping gRPC server
[INF] LOOPD: Stopping REST server
[WRN] GRPC: grpc: addrConn.createTransport failed to connect to {swap.lightning.today:11010  <nil> 0 <nil>}. Err: connection error: desc = "transport: Error while dialing dial tcp 52.25.40.106:11010: operation was canceled". Reconnecting...
[INF] LOOPD: Liquidity manager stopped
[INF] LOOPD: Daemon exited
[INF] LLMD: Auction server address: pool.lightning.finance:12010
[INF] CLDB: Checking for schema update: latest_version=1, db_version=1
[INF] RPCS: Starting trader server
[INF] RPCS: Connected to lnd node 02d561a482b9ddd1b492 with pubkey 02d561a482b9ddd1b492f208ab72275b73eb57f7f9e9fd6b76521f3e0d524b0f23
[INF] AUCT: Shutting down auctioneer client
[ERR] LITD: Could not start subservers: rpc error: code = Canceled desc = grpc: the client connection is closing
[ERR] LITD: Error stopping loop: rpc error: code = Unknown desc = verification failed: signature mismatch after caveat verification
[ERR] LNDC: Error closing client connection: rpc error: code = Canceled desc = grpc: the client connection is closing
[INF] SGNL: Received shutdown request.
[INF] SGNL: Shutting down...
[INF] SGNL: Gracefully shutting down.
[WRN] GRPC: grpc: addrConn.createTransport failed to connect to {pool.lightning.finance:12010  <nil> 0 <nil>}. Err: connection error: desc = "transport: authentication handshake failed: context canceled". Reconnecting...
[ERR] LITD: Error shutting down: rpc error: code = Unknown desc = verification failed: signature mismatch after caveat verification
rpc error: code = Canceled desc = grpc: the client connection is closing

You can reproduce this with Umbrel by:

  • Setting up Umbrel
  • Installing LiT
  • Opening the LiT app and logging in fine
  • Change Umbrel password (which also changes the LND password)
  • Log back in to Umbrel
  • Open the LiT app and logging in will fail
  • LiT server will soon crash
  • You should see the logs above at http://umbrel.local/logs

Nuking the LND data directory and creating a new wallet solves the issue.

A few Umbrel users have run into this and as far as we’re aware there’s no easy fix apart from us walking them through nuking their LND wallet and recreating it via CLI. Any help resolving this issue would be hugely appreciated!

Issue Analytics

  • State:closed
  • Created 3 years ago
  • Reactions:1
  • Comments:7 (3 by maintainers)

github_iconTop GitHub Comments

1reaction
lukechildscommented, Jan 6, 2021

Perfect! Thanks @guggero we’ll wait for that.

0reactions
guggerocommented, Jan 6, 2021

It looks like there is only one major issue around the payment_addr field. But once that gets resolved, I think the final release could happen soon. So maybe something around 2 weeks?

Read more comments on GitHub >

github_iconTop Results From Across the Web

How to Tell if Your Phone Has Been Hacked - Techlicious
It's a good idea to change your passwords – without updating them on your phone – before running a security sweep on your...
Read more >
Check your wallet.dat passphrase - Bitcoin Stack Exchange
Yes, open the command console inside the GUI and type walletpassphrase "your password" 1. This will only succeed if the password is correct....
Read more >
How to use oracle wallet - Stack Overflow
For listing the existing credentials in the wallet you can use the below command, but you need to provide the wallet password which...
Read more >
Timeline of Cyber Incidents Involving Financial Institutions
On April 1, 2022, North Korean state-sponsored threat group Lazarus was found to be using 'Trojanised' decentralised finance apps to deliver malware in...
Read more >
Half a Billion in Bitcoin, Lost in the Dump | The New Yorker
When plans for bitcoin were first introduced, in 2008, it was one of ... “If somebody's losing his wallet (e.g. due to disk...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found