Consistent "No route found" error with self hosted Lightning Node
Consistent "No route found" error with self hosted Lightning Node
Loading saved threads...
desolate_mountain · External communityPost link
External question — Bitcoin Stack Exchange
Author: desolate_mountain
Original post: https://bitcoin.stackexchange.com/questions/125044
License: CC BY-SA 4.0 — https://creativecommons.org/licenses/by-sa/4.0/
Adaptation: HTML converted to plain text; contact email addresses removed.
I followed the
Raspibolt guide
on how to setup Lightning. Everything is up and running smoothly, except I consistently get issues with a route not being found for my payments... I've been running tests with small txs: sending some sats to myself, friends, and overall the experience seems unstable... Sometimes it works, other times I'm unable to find routes.
Right now, I only have 1 channel open.
What do I need to do to have greater success, and an overall more stable experience when finding routes for my payments? Open more channels? Add more peers?
I tried opening a channel with Kraken, but quickly learned that some Lightning nodes set a minimum channel balance that... let's say is high for solo node runners like myself.
Quote
Report
MegalithicBTC · External communityPost link
External answer — Bitcoin Stack Exchange
Author: MegalithicBTC
Original post: https://bitcoin.stackexchange.com/a/127755
License: CC BY-SA 4.0 — https://creativecommons.org/licenses/by-sa/4.0/
Adaptation: HTML converted to plain text; contact email addresses removed.
We run The Megalith Node, which is one of the biggest and highest volume nodes on the Lightning Network. The “route not found” message is frustratingly generic and can be triggered by a bunch of different issues:
-- There’s no channel path between your node and the destination.
-- A path exists, but liquidity along it can’t carry your amount.
-- The receiver sits behind private channels and didn’t provide valid route hints in the invoice.
-- Your max-fee cap is too tight, so no route qualifies at that price.
-- A hop’s policy blocks your amount (min_htlc too high, max_in_flight reached, or max_accepted_htlcs full). This usually only happens if you’ve tweaked your node’s defaults.
-- Your internet link is unstable or some or all peers have flaky connectivity.
And this still isn’t an exhaustive list. ;)
If you’re determined to run your own node, open multiple channels to several large, well-connected routers to improve payment success.
Alternatively, use a third party for Lightning... Rizful or Alby Hub are solid options; if you want an exchange-linked wallet, try River.
Quote
Report
Post Reply
Quoted from Forex.com.bd-Editorial External answer — Bitcoin Stack Exchange Author: MegalithicBTC Source score (net votes, not local likes): 0 Original post: https://bitcoin.stackexchange.com/a/127755 License: CC BY-SA 4.0 — https://creativecommons.org/licenses/by-sa/4.0/ Adaptation: HTML converted to plain text; contact email addresses removed. We run The Megalith Node, which is one of the biggest and highest volume nodes on the Lightning Network. The “route not found” message is frustratingly generic and can be triggered by a bunch of different issues: -- There’s no channel path between your node and the destination. -- A path exists, but liquidity along it can’t carry your amount. -- The receiver sits behind private channels and didn’t provide valid route hints in the invoice. -- Your max-fee cap is too tight, so no route qualifies at that price. -- A hop’s policy blocks your amount (min_htlc too high, max_in_flight reached, or max_accepted_htlcs full). This usually only happens if you’ve tweaked your node’s defaults. -- Your internet link is unstable or some or all peers have flaky connectivity. And this still isn’t an exhaustive list. ;) If you’re determined to run your own node, open multiple channels to several large, well-connected routers to improve payment success. Alternatively, use a third party for Lightning... Rizful or Alby Hub are solid options; if you want an exchange-linked wallet, try River.
Checking account access…