After recovering the node, some channels are still being closed

[smolgrrr]

We could possibly make this clearer for users, as I believe if you start up a new LND instance with the same key while the old one is still live, LND rules will attempt to close your channels. There are other causes too, for the moment we generally recommend closing channels before migrating servers. Reference: Migrating LND - Builder's Guide

If you are unable to contact the other nodes, you will likely need to use Chantools as per the below.

@stargati

If that’s not possible, chantools developer just added a workaround that sends the error message separately to trigger the force close and recover funds.

chantools: https://github.com/guggero/chantools

solution: https://github.com/lightningnetwork/lnd/issues/7301#issuecomment-1445121739

Steps, per the developer… will need to ssh into your Umbrel and run via command line/terminal:

• Download the latest version of chantools (v0.10.7) (use arm64 version for Umbrel)
• Run the following command (replacing the peer address with the full address of the remote peer and the channel point with the channel in question):chantools triggerforceclose --peer [peer@address:port] --channel_point [channel:id]
• The tool will ask you for your seed, which is required to initiate the encrypted p2p communication with the peer.
• If the channel is observed by lnd (e.g. showing up in the list of lncli pendingchannels), then just wait until the force close transaction is confirmed and the channel should automatically update the status there.
• If the channel isn’t showing up in the list of pending channels, you can use the chantools sweepremoteclosed command to sweep the funds.

After running the above steps, channel was closed almost immediately and funds were secured on-chain.

Please give me a moment, and I will try to write this up into a concise guide.