Replies: 1 comment 8 replies
-
|
Sounds like it could be a connection issue. Are you running a Tor only node or are you using the |
Beta Was this translation helpful? Give feedback.
-
|
Can you try if that still happens with 0.16.0? There were a few improvements in that area of the code I think. |
Beta Was this translation helpful? Give feedback.
-
|
I left LNDg rebalancing turned off and noticed that the channel was much less offline. It goes offline when there is a routing attempt or a rebalance for it. In other words, when you have an HTLC attempt. I'll have to wait for Umbrel to release version 16 to be able to test it. |
Beta Was this translation helpful? Give feedback.
-
|
I tried now to close the channel and I get the following message: "Channel close failed! Error: link failed to shutdown" |
Beta Was this translation helpful? Give feedback.
-
|
I'd try again with 0.16 (I think Umbrel will publish the update soon). Or try directly after re-connecting. If it still doesn't work, I'd create an issue with the full logs around the time of the close attempt. Or, if you don't want to wait, you can also just force close the channel (though then we won't know what caused the problem). |
Beta Was this translation helpful? Give feedback.
-
|
I couldn't wait and decided to force the channel to close. I'll follow up if it happens again with another channel. |
Beta Was this translation helpful? Give feedback.
-
I have a channel that is constantly offline. But I already noticed that the LND shows the channel as offline, but the peer is active and I can connect to it.
I didn't understand the reason for the error in ChannelLink that in the sequence when trying to connect again indicates that the peers are already connected.
Beta Was this translation helpful? Give feedback.
All reactions