pull down to refresh

cln contributor here!
Let's try to put this down ok and solve your problem!
I have limited experience with command line and Linux but I can follow instructions if they are clear and well written.
Based on my experience, using the command line interface (CLI) is the best option, as there may be UI bugs that can cause issues. I can provide you with copy-and-paste commands to help you.
To view your UTXO info and open channels, you can run lightning-cli listfunds and find your UTXOs under the outputs section. If you have jq installed, you can run lightning-cli listfunds | jq .outputs to see this information.
I'm interested in seeing the status of your UTXOs and if possible, information about your channels. Let me know if you have any questions.
I completed this i see the Two pending channels both say “channelD awaiting lockin. Both ssh connected true
The channel I tried to close says connected “false” But the state says “ONCHAIN”
I also see my two UTXOS that are showing up in RTL and Zeus
What should I do next?
reply
Nothing, just wait. The thing that can happen here is that at the moment of your closing the channel, the counterparty was offline.
In this case, you should force close, but CLN can choose another way, which is to wait for a certain amount of time before trying to close again. Only if the node is still offline after this waiting period will Core Lightning force close the channel.
This may result in a slightly higher fee, but your bitcoins will be safe and will eventually be returned to you, or maybe they have already been returned
reply
The sats came back but how do I fix my pending channel problem? Any idea s?
reply
I been waiting for at least two weeks. How much longer will I have to wait? I already tried to force close the channel on RTL
reply
what the core lightning logs are telling you?
reply
I paid half the bounty to you. Thanks for your help getting into the cli put me at ease. But a further dive into the docs I saw what the issue is with the two pending channels. I think I discovered a new bug in CLN I haven’t posted it to the GitHub yet but the solutions they explain in their documentation doesn’t work.
reply
If you open an issue and tag me we can work around it, maybe the docs is not updated or just we had a bug.
Please make the issue when you had time
reply
reply
Okay thanks I have to ssh in first to access the ln cli.
reply