-
Notifications
You must be signed in to change notification settings - Fork 3k
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
"No path found" error gets stuck after the offline destination comes online #7291
Comments
Thanks for the report. What's the onion error you get back in the log for the last hop? This behavior is probably because the onion error handling blacklists the receiving channel and the blacklist gets reset after restarting. Could you try |
Could you try with master? There it should work clearing the blacklist. |
Yes, sorry. Just checked with master and indeed clearing the blacklist helped to resolve it. I suppose it should be done automatically if the user retries a failed payment, also the |
Any idea which of those onion errors are sent by the second-to-last node (i.e. the node that has a direct channel with the payee)? I am wondering what the "expected" error is in this case ("next hop offline")... is it |
No idea. Is there an option to dump the routes that Electrum tries? |
No, the routes are not exposed to the GUI atm. You can see them in the logs though. |
This is about Lightning payments with gossip enabled and no trampoline routing. Testing the following case on 4.1.2:
Retry
on the payment.Failed
toExpires in about 24 hours
which is also confusing. TheLog
menu item also disappears.Pay...
in the failed payment's context menu.This error seems to be pretty sticky. If you only reopen the wallet without exiting Electrum (in case you run both Bob and Alice on the same machine) it doesn't go away and instantly says "Path not found". If you don't wait until gossip is downloaded and try to pay you'll get the same error, and it won't go away even after gossip is synchronized. So Electrum needs to be restarted fully again.
It seems that when using trampoline all of this above doesn't apply. As soon as the other node goes online it can be paid with a simple retry.
The text was updated successfully, but these errors were encountered: