How to abandon channel after all Umbrel updates

Support and Troubleshooting
1

Hello! I opened a channel a few days ago and the transaction did not go through; it’s not broadcasted on the mempool and restarted the Lightning node does not help. I’m afraid it’s because of a double spent problem…

I’ve read in the Community that “abandonchannel” it’s the way to go as the transaction will never be mined.

However, after checking several posts and trying different commands, none of them work. Apparently because of some limitations with LNCLI in the latest Umbrel updates.

I am running my node with Umbrel on a RPI 4, version 1.2.1. And, I’ve tried the following, all of them with the abandonchannel comand:

  • docker exec lnd lncli abandonchannel --funding_txid ‘CHANNEL POINT FOUND IN RTL UNDER PENDING CHANNELS’ --output_index 1 --i_know_what_i_am_doing. Nothing; error with docker.

  • ./scripts/app compose lightning exec lnd lncli abandonchannel --funding_txid $TX_ID --output_index 1 --i_know_what_i_am_doing. Nothing, scripts directory cannot be found.

  • sudo ~/umbrel/scripts/app compose lightning exec lnd lncli , as stated in the latest Troubleshooting guide, but nothing.

  • sudo docker exec -it lightning_lnd_1 lncli, same.

I’m turning crazy! Could you please help me out and guide me on how to abandon this zombie channel to get back my sats?

Thanks a lot!

2

It’s probably easiest to do it this way:

  1. open your umbrel dashboard in a web browser
  2. click on the settings icon
  3. click terminal
  4. select App: Lightning Node
  5. a terminal window is going to open
  6. enter this command
lncli abandonchannel --funding_txid ‘CHANNEL POINT FOUND IN RTL UNDER PENDING CHANNELS’ --output_index 1 --i_know_what_i_am_doing

:bangbang: Be very careful when using this command, as using it incorrectly can result in the loss of funds locked in other channels. Doublecheck that you know what you are doing and that you are abandoning the right channel!

1 Like
3

Thanks a lot, @Django !

It worked like magic! :grin: I wasn’t aware that I could use the Terminal for a specific app.

By the way, for whoever reads this, just a minor comment on @Django step-by-step list:
#3.1: click “Advanced settings”
#3.2: click “Terminal”

Otherwise, it takes you to the logs console, rather than to the command line interface.

1 Like
4

Yes, terminal, not troubleshoot. I’ve just corrected it, thanks for pointing it out.