I recovered my node and have successfully settled the majority of my sats. However, I have two channels that wont close after a month. I have tried force closing via command:
looks like the channel is maybe not initialized correctly
try to recover it again with the backup
when you see the cannel with it’s full capacity try to close it again
you can also try using different app for this
I’ve tried restoring channel backups a few times, along with the command for scanning UTXOs. I’ve also had one of the peers restart their nodes to see if that would free anything up.
I’ll keep trying different channel recovery backups since I think that’s the only option I have left.
Not sure what apps to use, don’t see any options for me on RTL or Thunderhub
not so familiar with this but i think it ill take some time
otherwise you can force close these channels when the other person is not responding or something.
when you have the access you will get the funds back (i guess)
lightning is still somehow experimental but this should work.
Lots of steps took place so I’m not sure what exactly did it, but here is what happened for me:
After the initial channel recovery, I had two channels stuck closing. I performed reboots, asked the peers to reboot, scanned UTXOs, searched the forums, posted on here, and I couldn’t get anything to work. Then, I found an old sd card with umbrel on it from when I replaced it (due to that bug in the previous version). I booted up that old sd card and one channel immediately closed! But one was still stuck pending…so I deleted my lightning node app, recovered from the seed words, restored a channel backup, and there it was – the last of my sats recovered.
If anyone else is stuck, try recovering using seed words (again), and recover channels using backup (again). I used an older backup and that seemed to work for me…
Linux&Umbrel beginner here. Thanks for the steps goliath77, it was helpful. I reinstalled Lightning node, restored it and one stuck channel disappeared. I was trying to close the second with different approach but I got stuck.
I’m running standard Umbrel 0.5.3 on Pi 4, 8Gb ram.
1/ I tried channel recovery scenario mentioned in Chantools github but it seems it got stuck.
I used the recommended command (chantools compactdb --sourcedb <recovered-channel.db> --destdb ./results/compacted.db). The log was created and after 24h results/compacted.db didn’t exists. There was no other info in the log, only one line with tool version. The Bitcoin node was stopped. Is this expected?
2/ I tried another approach. I got channel:id (lncli pendingchannels) and peer address and tried
chantools triggerforceclose --peer [peer@address:port] --channel_point [channel:id ]
command.
I got following error:
“error requesting force close: error connecting to peer: error dialing peer: dial tcp: address fs4…onion: no suitable address found”
I checked the peer and he’s offline since January 2024. Does the peer needs to be online to force close the channel? Or am I missing something here?
3/ As a last option I tried sweepremoteclosed. Here is the command:
umbrel@umbrel:~ $ chantools sweepremoteclosed --recoverywindow 300 --feerate 20 --sweepaddr ‘fromseed’ --publish
But I also got error. This time:
Error: could not query API for addresses with funds: could not query unspent: error decoding data from API ‘https://blockstream.info/api/address/’, server might be experiencing temporary issues, try again later; error details: invalid character ‘Y’ looking for beginning of value
Is it because the peer is offline?
