-
Notifications
You must be signed in to change notification settings - Fork 28
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Ran out of routes after X attempts #421
Comments
Sadly the error messages returned by the As a matter of fact, we're hoping to get some feedback on how to better report these in the future. Would adding an array of attempts in the |
Sorry I didn't answer this earlier (as I was stuck with the other bug lol). I retried again today and the error is still the same, impossible to send any payment from the node. Tbh I don't need this node anymore and it's fine for us to ditch it but we still have some sats on it (22951697 msats to be precise). So up to you:
No sats shall be wasted. |
Interesting, this is the second node I see today that is running into the HTLC addition timeout:
We're still investigating this in another issue, but maybe you can add a bit of color to this. The following are potential sources that we'd like to exclude:
The first two you can likely exclude by trying to perform a payment while connected to a WLAN that is low latency and high bandwidth. |
Hi everyone,
I've been looking around and realised this issue is common and other people are experiencing it. I open an issue nonetheless because I think it's node specific so we can track it.
For a long time I thought this was a Breez issue but it seems to be a Greenlight one as the Breez folks asked me to open an issue here.
The issue
Sending a payment to any node (tried: Alby, Phoenix, Blink and own personal node) always fails with
Using the Breez SDK.
Here is the node info:
and the LSP info:
Wouldn't mind simply withdrawing the sats of this node and create a new one as this one still uses the invite code from Breez but we'd like to switch to using Greenlight certificates.
Thanks for your time,
Dario
The text was updated successfully, but these errors were encountered: