feature: support Tor for triggerforceclose

[ShadowStorm0]

I tried to use the triggerforceclose to force close a channel but I get this error error dialing peer: dial tcp: I checked on 1ML and Amboss and the peer is online. Can anyone explain what is happening please.

[guggero]

What's the peer address? Tor isn't supported by the command (yet).

[ShadowStorm0]

It was a tor address. But don't worry, in the meantime, the channel backup seams to have force closed it. I got 2 more channels that are still closing and I think both are clearnet IP's

[ShadowStorm0]

for a clearnet one I keep getting
[INF] CHAN: No spends found yet, waiting 5 seconds...
and sometimes Sending Ping is successful and other times it is unable to reason: unable to write message: write tcp

This is for the same command chain

[ShadowStorm0]

I'm getting Error: error getting channel address: invalid character '<' looking for beginning of value now

[guggero]

I haven't tested this extensively, so it's possible there are still a few bugs. Though this will only work with CLN peers, are you sure that's the case?

invalid character '<' looking for beginning of value

This is an error from the blockstream.info API, you're either being rate limited or they have an issue on their end. Just try again later.

[ShadowStorm0]

I'm not sure if they are a CLN peer, but it seems like that channel closed by itself overnight.
I got one more left that is not closed yet, but it's one over Tor.

[guggero]

If you're running the SCB recovery on a node as well, make sure you can connect to that last Tor node. If you can, just give it some more time. Or try the workaround described here: lightningnetwork/lnd#7301 (comment)

[ShadowStorm0]

Thank You. I'll try later today

[ShadowStorm0]

I stand corrected, they seam to be on the clearnet https://amboss.space/node/03c436af41160a355fc1ed230a64f6a64bcbd2ae50f12171d1318f9782602be601

[ShadowStorm0]

I keep getting [INF] CHAN: No spends found yet, waiting 5 seconds...
after I ran this command chantools triggerforceclose --peer [ ]@[ ]:[ ] --channel_point [ ]

[guggero]

Well, then it's not a CLN node or not the version affected. You'll need to continue trying with the SCB recovery.

[ShadowStorm0]

What steps can I do if the SCB recovery is not going anywhere?

[guggero]

What does the log say for the channel in question?

[ShadowStorm0]

[guggero]

No, I mean the log file.

[ShadowStorm0]

not sure what you mean than, can you point me to where it is

[guggero]

https://docs.lightning.engineering/lightning-network-tools/lnd/debugging_lnd

[ShadowStorm0]

found the lnd.log file. There is a lot to sort through tho

[guggero]

Try grepping by the channel point and remote node ID.

[ShadowStorm0]

This is what I got: https://paste.sethforprivacy.com/?9b5ce75fb9a7e2df=#2EY9P1QDAvJk5KpT35iZaAmBTMXbRRtW32fBooDT7ys9

[ShadowStorm0]

It's getting late, ill have to continue this tomorrow

[guggero]

It looks okay, nothing unexpected. Could be that this was an old channel format with a fixed fee rate which cannot be accepted by the mempool at the current fee rates. You'll just need to wait, and hope the fees come down. Also, restarting lnd every once in a while might help here (maybe once a day). You can also attempt to contact the peer if you find information about them and ask them to force close from their end.