Channel force-closed: Unknown channel for WIRE_CHANNEL_REESTABLISH

[Bayernatoor]

I created a fresh Mutiny wallet yesterday and funded the on-chain wallet. I swapped my on-chain btc to open a lightning channel. Channel was almost immediately closed.

Error message: Channel closed because counterparty force-closed with message: Unknown channel for WIRE_CHANNEL_REESTABLISH

Channel Open txid: b35065b458010416c3d013118b347615f0239a64ea6c84553ba984162386d2b4
Channel Id: b4d286231684a93b55846cea649a23f01576348b1113d0c316040158b46550b3
Logs: mutiny-logs.txt

Channel closing in logs (line 9425+):

2023-10-04 08:27:31.043 INFO  [lightning::ln::channelmanager:8423] Queueing monitor update to ensure missing channel b4d286231684a93b55846cea649a23f01576348b1113d0c316040158b46550b3 is force closed
2023-10-04 08:27:31.043 INFO  [mutiny_core::node:319] creating lsp client
2023-10-04 08:27:31.044 TRACE [lightning::chain::chainmonitor:659] Got new ChannelMonitor for channel b4d286231684a93b55846cea649a23f01576348b1113d0c316040158b46550b3
2023-10-04 08:27:31.046 INFO  [lightning::chain::chainmonitor:673] Persistence of new ChannelMonitor for channel b4d286231684a93b55846cea649a23f01576348b1113d0c316040158b46550b3 completed
2023-10-04 08:27:31.047 INFO  [mutiny_core::node:537] Node started: 0230e0b739d777735d809572a18afb02307d992e75ab13712f8542f54c3cf8acf8
2023-10-04 08:27:31.047 INFO  [mutiny_core::nodemanager:742] inserting updated nodes
2023-10-04 08:27:31.047 INFO  [mutiny_core::nodemanager:749] inserted updated nodes
2023-10-04 08:27:31.057 TRACE [mutiny_core::background:556] Calling ChannelManager's timer_tick_occurred on startup
2023-10-04 08:27:31.058 TRACE [lightning::chain::chainmonitor:707] Updating ChannelMonitor for channel b4d286231684a93b55846cea649a23f01576348b1113d0c316040158b46550b3
2023-10-04 08:27:31.058 INFO  [lightning::chain::channelmonitor:2434] Applying post-force-closed update to monitor b4d286231684a93b55846cea649a23f01576348b1113d0c316040158b46550b3 with 1 change(s).
2023-10-04 08:27:31.058 TRACE [lightning::chain::channelmonitor:2497] Updating ChannelMonitor: channel force closed, should broadcast: true
2023-10-04 08:27:31.058 TRACE [lightning::chain::channelmonitor:2509] Avoiding commitment broadcast, already detected confirmed spend onchain
2023-10-04 08:27:31.059 DEBUG [lightning::chain::chainmonitor:727] Persistence of ChannelMonitorUpdate for channel b4d286231684a93b55846cea649a23f01576348b1113d0c316040158b46550b3 completed

Note:

The original fee to open the channel was ~3k sats. The confirmed channel open tx shows a fee of 2,664 SATS. However, my onchain balance (since the channel close) is 7008 sats less then it originally was. Is that due to additional fees for the channel close?

I also created a nostr wallet connection but never actually connected my nostr to it.

[benalleng]

the extra 4344 sats is the fee from the transaction that moved the channel funds back to your wallet.
Not sure exactly what the error indicates but it looks like there is another issue of it happening before ElementsProject/lightning#3608

[benthecarman]

What were you doing when this happened, from looking at the logs it looks like you had the page open for 10+ hours and then refreshed the page

[Bayernatoor]

Actually, I have this wallet running on mobile but i also imported it on my desktop. So it's possible that it was open in both the PWA on android and my desktop browser at the same time. Which come to think of may not be supported.

My mutiny wallet in my browser was definitely open for awhile and I may have refreshed the page at some point but I dont quite remember.

I can always try to reproduce.

[benthecarman]

Yeah it's not supported to have the wallet running in multiple places at the same time.

[Bayernatoor]

Yep, that's likely the issue then. If it can help I can try to reproduce the same error by running the same wallet on 2 devices.

[benthecarman]

No please don't do that, it'll just cause issues again

[Bayernatoor]

Sounds good. Let me know If i can do something else to help otherwise. I can close this issue.

[TonyGiorgio]

Sounds good. Let me know If i can do something else to help otherwise. I can close this issue.

We do have signet-app.mutinywallet.com if you want to play around with reproducing issues on a test network. But it sounds like it was just from running two at once.

[TonyGiorgio]

This should not happening anymore due to putting a lock around channel connections.