-
Notifications
You must be signed in to change notification settings - Fork 216
unable to find a path to destination #261
Comments
Same problem with Yalls even though I am connected directly to Yalls. However, I have no problems sending payment to or receiving from htlc.me. This is strange since the connection to Yalls is my only connection. |
It is still not working. I connected to 031dc566ea7e71531edba5929e11de824bf4bfd2062f840499223398a56644e5e2@52.3.235.238 today. But still no path to destination. However, it worked at the beginning, two days ago. |
Thus far, for me, it says "Unable to find a path to destination" every single time. I have never successfully sent a LN payment on testnet.also, about this: I also experience this problem. It should either automatically clear at some point, or at least a button to clear. Ideally, a button and a checkbox to either leave it on auto-clear, or manually clear in case your flow is better like that. Some people prefer the flow of actually manually clicking. |
This is a normal error. Just means your node is unable to find a route. The UX/error handling can be better but this is not a bug. Closing |
I have the same problem: Channel opened with yalls but when I pay I get "unable to find a path to destination". I succeeded making this just the firs day of testing.. then not anymore.. |
Same problem. Many channels opened but "unable to find a path to destination". |
Same problem here, I have a channel opened directly with the destination node and I even closed all my other channels so this is the only one left open. |
Hi,
I am playing around with Zap. However, I cannot make any payment. I always get the "unable to find a path to destination" error even though I am directly connected to a Y'alls node.
Moreover, the GUI (Linux) always keeps the input. That is, e.g., if one has copied an URI into some field, reopening the window with the field keeps the URI. So one always has to remove the string in the field. There should be a "clear" -button or similar.
Also closing the wallet does not stop the porgram. If it was started in a terminal via "./", one hast to use Ctrl+C to kill it, otherwise the terminal blocks.
Regards,
cu
The text was updated successfully, but these errors were encountered: