LND channels won’t close after recovery

Conrad · August 14, 2025, 9:05pm

Hi,
After a disaster recovery, I have two LND Lightning channels that won’t close. This shows up in the LND log:

2025-08-14T20:20:09+02:00  2025-08-14 18:20:09.710 [INF] CNCT: ChannelArbitrator(e4d0817c5427ce1834cc14e118b6db6feb07f72a725583291acf6132737204d5:1): skipping reading close events in state=StateWaitingFullResolution
2025-08-14T20:20:09+02:00  2025-08-14 18:20:09.710 [INF] CNCT: ChannelArbitrator(ab4637971c91fcfb6879bc436fa0d0894cb17bdc6dbc8138fb5d9802b8ce45fc:0): skipping reading close events in state=StateWaitingFullResolution

Any ideas on how to fix this?

Thanks!

Conrad · August 15, 2025, 9:06am

I’ve also tried manually force-closing the channels from a backup, but I keep getting an error even though the file exists.

sudo podman exec -it lnd.embassy lncli --rpcserver lnd.embassy restorechanbackup --multi_file /embassy-data/package-data/volumes/lnd/data/main/data/chain/bitcoin/mainnet/chan-backup-archives/channel.backup-2025-07-06-18-21-40

unable to decode multi packed backup: open /embassy-data/package-data/volumes/lnd/data/main/data/chain/bitcoin/mainnet/chan-backup-archives/channel.backup-2025-07-06-18-21-40: no such file or directory

Conrad · August 15, 2025, 9:32am

I managed to fix it in the end.

h0mer · August 15, 2025, 3:00pm

Hi

What append? Can you share for future generations?

Conrad · August 15, 2025, 4:01pm

The last thing I did was uninstall LND, reinstall it from my latest backup, avoid updating to the newest version of LND, and then start LND. That way, the channels closed without any issues.