Loop out still showing Initiated status after 2 weeks #836
-
A loop out request carried out using RTL on 3 October 2021 is still showing status Initiated. Here is a screenshot RTL is running as an app on umbrel. A loop out request worked successfully on 2 October 2021. For some reason, this one on 3 October 2021 has got stuck at initiated status. |
Beta Was this translation helpful? Give feedback.
Replies: 2 comments
-
Hi @jc-jnet do you see any Active HTLCs on the channels page? If you can login to your umbrel via command line, you can try running |
Beta Was this translation helpful? Give feedback.
-
Thanks. I did not see any active HTLCs. I noticed that the channel with
Wallet of Satoshi node has become inactive. My other channels are active.
Not sure why thus one became inactive. I have been talking to them on Slack
about the loop out issue.
I have now rebooted umbrel.
…On Sun, 17 Oct 2021, 21:38 Suheb, ***@***.***> wrote:
Hi @jc-jnet <https://github.com/jc-jnet> do you see any Active HTLCs on
the channels page?
if not, it's likely that the Loop out request has timed out, but for some
reason not reflecting the status correctly. You can try restarting your
umbrel once, so that loop server restarts and updates the status correctly.
If you can login to your umbrel via command line, you can try running loop
monitor command which might provide you status of your loop out command.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#836 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AGDILYCFLSA2EESVI7GNV73UHMXSJANCNFSM5GFGPHEQ>
.
Triage notifications on the go with GitHub Mobile for iOS
<https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675>
or Android
<https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.
|
Beta Was this translation helpful? Give feedback.
Hi @jc-jnet do you see any Active HTLCs on the channels page?
if not, it's likely that the Loop out request has timed out, but for some reason not reflecting the status correctly. You can try restarting your umbrel once, so that loop server restarts and updates the status correctly.
If you can login to your umbrel via command line, you can try running
loop monitor
command which might provide you status of your loop out command.