I initiated a channel close on Umbrel 2 weeks ago but it remains stuck on “closing”." If I select “view info” on the channel in RTL (Ride The Lightning), I can see it under “Waiting Close.” I have tried restarting my node several times.
If anyone can provide the command to force close the channel via command prompt that would help. I have managed to connect via C:\WINDOWS\system32>ssh umbrel@umbrel.local
Managed to figure it out. Executed the command via command prompt on desktop PC to force close:
Connect to Umbrel:
C:\WINDOWS\system32>ssh umbrel@umbrel.local
Execute command:
umbrel@umbrel:~ $ ~/umbrel/bin/lncli closechannel --force … //(channel point with a space instead of “:” )
Transaction was re-broadcast successfully. “blocks_til_maturity” of 143 so presumably have to wait for these to clear before funds are returned.
@bitcarnicoin I have the same issue, but I’m confused what you meant by "channel point with a space instead of a : "
When I tried the command to force the channel to
“037cc5f9f1da20ac0d60e83989729a204a33cc2d8e80438969fadf35c1c5f1233b@165.227.103.83:9735”
I did ~/umbrel/bin/lncli closechannel --force 037cc5f9f1da20ac0d60e83989729a204a33cc2d8e80438969fadf35c1c5f1233b@165.227.103.83 9735
But I got the error [closechannel] unable to get funding txid: max hash string length is 64 bytes
So I tried the TXID I used for opening the channel
~/umbrel/bin/lncli closechannel --force <TXID>
The error from the logs was [/lnrpc.Lightning/CloseChannel]: channel not found
I’m not sure what I’m doing wrong here…
Just kidding! The channel point is found when you enter ~/umbrel/bin/lncli pendingchannels
And look inside the waiting_close_channels array for channel_point… from there it’ll be a string like
851ddc0900b775ff4afbd12ed4c8c003456eaea862ba96664344b06a04eec7c5:1
And to close the channel it’s like you said
~/umbrel/bin/lncli closechannel --force 851ddc0900b775ff4afbd12ed4c8c003456eaea862ba96664344b06a04eec7c5 1
Hope this helps someone in the future!
One more thing, after the closechannel command works, you can see when your funds will be released in the maturity_height value inside the pending_force_closing_channels array.
~/umbrel/bin/lncli pendingchannels
"pending_force_closing_channels": [ ...."maturity_height": 694303,
thank you this helped me a lot.
@Mikey, after running the force close command there was a brief pause then nothing. Ran the pendingchannels, but nothing shows up in “force_closing”. How long might I need to wait?
Not seeing “maturity_height” either.
Also, local and remote balances are both shown as “0”?
Not really. Some explorers showed the channel as still being active while others showed it as non-existent. I waited a few weeks then still found it to be inactive by most accounts, so I dropped it.
Currently, I’m working on a cluster-computer to make sure this doesn’t happen to me again! Even if the setup experiences hardware failures, the bitcoin clock should keep on ticking…
I also have this exact problem @zipfastlnd @mugiwara . I am attemping to find a solution. But did you find a solution?
This aspect is very well explained in the troubleshooting guide and what you can do about, but seems that users don’t want or don’t have the patience to read that manual, just asking over and over same questions.
You are incorrect, it is not very well explained in the troubleshooting guide.
I already checked the troubleshooting guide and it details that you should expect to see a “maturity_height”. As you can see from the picture above in this thread, there is no “maturity_height” listed.
I carried out the force close as this thread and the guide states, and I still see no maturity_height. The channel also doesn’t move into “pending_force_closing_channels” like you may expect, it just stays in “waiting_close_channels”.
So from trying to do everything “correctly” and “reading the manual” and “having patience” - there’s still problems.
You said yesterday you always say the truth. So here’s some truth - You shit on people for not reading guides, having no patience and being noobs - which makes you just come across as an awful person. Many of your guides have mistakes and errors making them difficult to understand or even more confusing. Your behaviour is detrimental to the growth of bitcoin, lightning and the Umbrel community and you make the culture around here downright awful. There’s much nicer communities to go to and that’s exactly what I’ve done and found much more help from people who aren’t just plain old grumpy arseholes.
You are welcome to write better guides. Are you capable to do that? Or just complaining?
I gave you the right information how to proceed with channels in closing. If you are not capable to understand how LN works then sorry but these things are not for you.
I am not here to talk nice with you, this is not a “be nice” contest. I don’t have time to find the words that make you happy. Take it or leave it.
There is a tool called “chantools” which may help your scenario if you’re still having a problem. I’ll paste my problem I had and it’s solution below incase it is useful to help you.
That’s it. All my funds were recovered. I’d like to thanks again the folks that helped me out, so thank you!
Thank you for this answer. Using Lightning Shell (add-on app via the Dashboard on Umbrel) to perform this force close of a stuck channel has been the only solution for me recently. Somehow, moving my Umbrel to a different network IP address totally killed SSH, and using Lightning Shell to force close my stuck channel is the only way for me to get all my sats back from my Lightning channels before rebuilding my Umbrel. How else will I get SSH working again?! 
I like my Umbrel on Raspberry Pi 4 box a lot - very easy to use, generally - but I’d like to continue to see more stability to handle these one-off situations I’ve found myself stuck in recently.
Agree with you, Diiikco. @DarthCoin has done lots and lots of work to inform, which is appreciated, but yes, many times the individual interactions seen on forum posts is rather rude and condescending, as if Darth’s writing and instruction is always infallible, and it’s not.
There will always be edge cases and unexpected errors with systems so complex as hardware, software, internet, networking, security, Bitcoin and Lightning networks, and how it all fits together. That is A LOT of potential failure points for any individual user to have to navigate, and for @DarthCoin to behave as though everyone who hasn’t encountered many of those failure points before is a retard is rude, at best.
Will this also work if the other node initiated the channel to me? I seem to have 2 missing channels after restoring a channel backup and one stuck on waiting close with 0 limbo balance reported. ( which is not correct). If they force close to me will I be able to get the sats balance on my side of the channels back or are they lost forever? I’ve been fighting with this for 4 days and it seems no one is able to answer my question, losing my patience and my mind over this. 
I used the original command and there was an Deprecation notice as below.
My Umbrel version is the most latest.
"~/umbrel/bin/lncli closechannel --force
*** Deprecation notice ****
In a future version of Umbrel, ‘lncli’ will be removed.*
Please instead use:*
./scripts/app compose lightning exec lnd lncli "*
Anyone helps provide the updated command, pls.
