lnd: UnknownNextPeer error on payinvoice
I’m consistently getting this error when trying to send payment from one of my nodes to another, I’ve restarted both nodes and created lots of invoices to try but the error persists.
Whenever I try to pay a simple invoice I get unable to route payment to destination: UnknownNextPeer
. There is an active channel between the two nodes with plenty of balance belonging to the sender. Here’s some of the relevant output from the sending node:
$ lncli decodepayreq lntb1u1pd9qaztpp5pat93v4kg7z393ggrvd5r0u9tflxum3f7t9zq56scma3e480smqsdq4f35kw6r5de5kueeqgajk6cqzysx9zgpskkh0y0jxnmwzljtuw54h6g3z7jve0l8s5rhff244epjg8r5eqj7nez8f70psjqkyff5fl7n7z9ksrgjrgsv9k4sm5h2s26cqcqularhs
{
"destination": "023c1fc1ef2d9a555693cf0fdc39b66d934dfc07bc0b1ee050fd3f4aeb773b9438",
"payment_hash": "0f5658b2b6478512c5081b1b41bf855a7e6e6e29f2ca205350c6fb1cd4ef86c1",
"num_satoshis": "100",
"timestamp": "1515222091",
"expiry": "3600",
"description": "Lightning Gem",
"description_hash": "",
"fallback_addr": "",
"cltv_expiry": "144"
}
Here’s the active channel (I trimmed the other channels from the listchannels
output):
$ lncli listchannels
{
"active": true,
"remote_pubkey": "023c1fc1ef2d9a555693cf0fdc39b66d934dfc07bc0b1ee050fd3f4aeb773b9438",
"channel_point": "6aa0bada9d2fce57f61d7d93bb4b8fc5189c03e722c963d5aadd52968852f934:0",
"chan_id": "1381799143597932544",
"capacity": "1000000",
"local_balance": "995436",
"remote_balance": "220",
"commit_fee": "4564",
"commit_weight": "600",
"fee_per_kw": "6000",
"unsettled_balance": "0",
"total_satoshis_sent": "220",
"total_satoshis_received": "0",
"num_updates": "4",
"pending_htlcs": [
],
"csv_delay": 4
}
And here’s the error:
$ lncli payinvoice lntb1u1pd9qaztpp5pat93v4kg7z393ggrvd5r0u9tflxum3f7t9zq56scma3e480smqsdq4f35kw6r5de5kueeqgajk6cqzysx9zgpskkh0y0jxnmwzljtuw54h6g3z7jve0l8s5rhff244epjg8r5eqj7nez8f70psjqkyff5fl7n7z9ksrgjrgsv9k4sm5h2s26cqcqularhs
{
"payment_error": "unable to route payment to destination: UnknownNextPeer",
"payment_preimage": "",
"payment_route": null
}
About this issue
- Original URL
- State: closed
- Created 6 years ago
- Reactions: 2
- Comments: 22 (15 by maintainers)
This isn’t an implementation issue, rather it’s a network level error. This is only the last error returned. For example, if the node you’re trying to pay isn’t online, then you’ll get this error. It just means that in one of the routes (usually the last one) that we attempted, one of the peers wasn’t online so we weren’t able to proceed. I’d also recommend you run master as there’ve been several bugs fixed, and they’ll be packaged in a new point release soon.