Anyone here with deeper knowledge of #LND? My lightning node can't send payments to Alby and says "no_route" all the time. My node is well connected to large nodes so that should not be an issue.
How can I debug this? The "no_route" error appears imedately - maybe some weird caching issue? Restarting LND didn't help.
#asknostr
Try to send to WOS.
Maybe there are no routes if they have problems on their end
All other payments work. Only Alby doesn't.
Obvious questions like, how are your channels balanced, what are your fees?
You can use tools like Amboss to dig a little deeper on your side and Alby’s side
Channels are balanced, fees are low (80 msat). I'll try Amboss.
Here’s Chat GPT’s advice…
The "no_route" error in your Lightning node can be caused by several factors, despite your node being well connected. Here are some steps to help you debug and potentially resolve the issue:
1. **Channel Capacity and Balances**:
- Ensure that both your node and the nodes in the route have sufficient capacity and that the balances are sufficient to cover the payment.
2. **Channel States**:
- Verify that the channels you are relying on are active and not in an offline or disabled state. Use `lncli listchannels` to check the state of your channels.
3. **Routing Fees**:
- Check if the fee settings of the intermediary nodes are preventing the route from being viable. Some nodes might have high fees or specific policies that make the route unfeasible.
4. **Node and Channel Policies**:
- Ensure that there are no policy restrictions on the channels, such as minimum HTLC amounts or maximum HTLC limits, that could be preventing the route. Use `lncli getchaninfo
5. **Graph Synchronization**:
- Ensure your node's network graph is up-to-date. Sometimes, a "no_route" error can be due to outdated network information. Use `lncli describegraph` to check your graph status and consider forcing a graph sync if necessary.
6. **Routing Hints**:
- Sometimes providing routing hints can help. Make sure the invoice you are trying to pay includes routing hints if needed.
7. **Payment Splitting**:
- If the payment amount is large, consider splitting it into smaller parts. This can help find routes that may not support larger single payments.
8. **Logs and Debugging**:
- Check the LND logs for any additional error messages or warnings that can provide more insight into why the route is not being found. Logs can be found typically at `~/.lnd/logs/bitcoin/mainnet/lnd.log`.
9. **Channel Rebalancing**:
- If your channels are imbalanced, try to rebalance them. You can use tools like `lndmanage` to help with rebalancing.
10. **Network Issues**:
- Ensure there are no network issues or connectivity problems with your node or the nodes in the route.
11. **Reputation and Reliability**:
- The reliability and reputation of the nodes in the route can affect routing decisions. If nodes frequently fail, they might be avoided by routing algorithms.
To provide more specific guidance, examining the exact error messages and your node's current status in detail would be helpful. If the problem persists, consider reaching out to the Lightning community or forums where you can get more targeted advice based on your specific setup.
Do you have a direct channel to nostr:npub1getal6ykt05fsz5nqu4uld09nfj3y3qxmv8crys4aeut53unfvlqr80nfm ? If so, check that both sides see it as 'active'
The strange thing is that I CAN route to Alby Routing 1, but not to getalby.com, which is the next hop. nostr:npub1getal6ykt05fsz5nqu4uld09nfj3y3qxmv8crys4aeut53unfvlqr80nfm Do you guys have any idea?
Oh yeah, that's pretty strange. This must be an internal issue w/ Alby
Hey, thanks for reporting! What is your node? Best if you could dm or reach support@getalby.com
Thanks, DM sent.
hmm... is there a chance you can try to reset the mission control of your LND?
maybe it blocks that hop? - I think this can happen if it failed before for some reason.
