Current setup:Current setup:
I have a lightning node (Not a CLN node, We will call this Machine1) running for a while (with no issues). I wanted to mess around with CLN software to get myself familiar with it. So I have set up a CLN node (We will call this Machine2)
IssueIssue
I have one channel open from Machine1 to Machine2. I can send from Machine 1 to Machine2 with out issue.
But when I try to pay a invoice generated by Machine1 , Machine2 get the following error:
<Machine1 Node ID>
is not reachable directly and all routehints were unusable.?When I try to pay via key send from Machine 2 to Machine1 I get the following:
"Ran out of routes to try after 1 attempt: see paystatus"
Question:Question:
Why can CLN Node (machine2) not send Sats out to a current open channel? Routing fees are set to either 0 or 1 Sats. So This should not be an issue.
Thanks in advance to any CLN user that can help
The incoming liquidity problem comes into mind. A lightning liquidity provider will be able to help you.
Is a very good question, but you need to give more details:
Machine2 has under 100 Sats. ( Was hoping to confirm send out before depositing to many sats)
Where can I see reserve per channel in CLN or Ride the lighting? I see a Dust limit which is currently larger than the Machine 2 balance ( Which I am starting to think is the issue).
No Can a channel be swtich between private and public or is this done at opening of the channel
I have tried CLI and Ride the lighting.
That could be the issue (see the buffer spec link I posted). If is the only channel with that node try moving with keysend from node1 to node2 some more sats, try a bit more than the channel reserve (around 1%).
Yes, when you create the channel you choose between private and public and you cannot switch afterwards.
That was the issue, Thank you.
For anyone in the future that might read this:
In the Core Lighting web UI, goto channel details there is a "Spendable" amount. Make sure this reads as greater than zero. Which is different from "Maximum Send" amount which shows your whole channel size balance. ( not reflecting the reserve amount)
If you own the two nodes, the keysend is key to maintain some kind of balance in the channel and avoid this problems.
Pay out