Closed zyklopisch closed 8 months ago
Problem still persists in 4.0.24.
Hi @SergeyShirin @zyklopisch
To better understand what's going on with your node and to try to fix the issue, please export your Lightning account logs.
To do this follow the steps:
Please use the official support form to share the logs.
DO NOT share the logs in this public issue.
Thank you.
Hi @SergeyShirin @zyklopisch
To better understand what's going on with your node and to try to fix the issue, please export your Lightning account logs. Please use the official support form to share the logs.
I have attached the logs to my support ticket #35901.
@SergeyShirin We are looking into your logs. I have some questions.
Thanks
@angelix ,
In the app instance from which I sent the logs, I have one wallet and one LN account in it. At the moment when the channel was force-closed, the LN account was the only account in the app. Later, right after the closure of the channel, I also opened Legacy Segwit account, Standard account, 2FA Protected account and 2of3 with 2FA account. All of them are within the same wallet.
Then, a couple of days later, I also installed the app on another device and restored the wallet from the seed phrase there. So, on another device, I have two wallets in the app, and only one LN account which is within the restored wallet.
Interesting fact. Two different instances of the app (on two different devices) show different txid for the transaction which closes the channel. The second device (where the wallet was restored from the seed phrase) shows correct txid. The first (initial) device shows the txid which doesn’t exist in the blockchain.
Do you need my logs from the second device?
Do you need my logs from the second device?
@SergeyShirin Sure, that would be helpful
@angelix , I’ve sent them in the ticket.
Problem still persists in 4.0.25
Today I tried again and it worked! Seems fixed!
Description
After the Lightning-channel was force closed automatically and when I now want to Sweep the BTC to get it back on-chain, it everytime throws this error messages. I tried about 30x times throughout a month, it is everytime the same. Tried with and without TOR-connection.
Version
4.0.21
Screenshots
Device or machine
Android Phone, latest