Hello all,
The last couple of days I have been getting a very small payout and reviewing my Ocean page, I see all my minors on-line, howerver I have a Lightening Payout Error that points me to.
Latest lightning error: Unknown payout error, contact lightning@ocean.xyz
Raw error: cln err code: -1 - message JSONRPCError: code=1005, message=Timeout waiting for response, data=map[]
Encountered at: 2025-09-10 07:01:55 UTC
Any ideas?
I’ve heard from a couple of other folks who have issues with Ocean showing a payout error as well. The first thing that I would check is if shutting down all your services (taking a backup if you have one due), restarting your server, and then start the services back up one by one making sure the health checks pass.
If that doesn’t work, then I would check whether you can pay a test invoice to your Core Lightning node. This would help you rule out potential liquidity problems with the nodes you are connected to.
If that a test invoice goes through without problems, then maybe the next thing you could try is to shut down your Core Lightning service, clear the gossip data, and then start it back up. It will take a few hours for the gossip data to be reassembled if you do this.
If you still have a problem, then you will probably need to reach out to Ocean for help to see if they can provide any other insights.
Does anyone else here on the forum who has had a problem with Ocean reporting an error, have anything else that might be helpful? I haven’t experienced this problem yet myself, so I don’t have any good troubleshooting experience.
Ocean retries payment every time a block is mined, so your sats are still being stacked and you will be paid when the issue/s are resolved. Contacting Ocean at this point will gain a reply saying payments will retry until successful.
Unfortunately sometimes Lightning does strange things and often these errors occur and resolve themselves. I would follow Paul’s advice above to look after the things you can control like backup and restart, followed by an invoice test for the same / slightly more than the amount that failed. If that works I would wait and see what happens the next time Ocean hits a block and payment is due. This is not a long wait now their hash rate is much higher.
If it fails again follow Paul’s advice re clearing and refreshing gossip data, wait for another block payment, then email Ocean if it fails once more. Remember that other nodes going offline temporarily can cause payment routing / timeout issues, nodes charging different fee amounts can cause failures, etc.
Actually…I got a payout earlier today at 15:55 OCEAN time : But this is the last line in the log as I just checked at the time of this response.
2025-09-10T15:55:35-06:00 2025-09-10T21:55:35.376Z INFO lightningd: Resolved invoice ‘869aea5cf4657cafa74cac64d18eff7a32795a063a3e8e46c3434220820de3b2-02cfb4639d0eedabf65ac5fcb5294617b5c2b301ae5c4ab8d559dce415e00d14cb-0’ with amount 3461000msat in 1 htlcs
But I do see another upcoming invoice payment sitting in Core receive failed. The invoice will expire on 9-10-25 at 17:55…and I have one more sitting in Unpaid Earnings in my Dashboard.
OCEAN has reported no errors to me though. So I will wait and see.
Oh and I did find this in the log 8 times today as well: These eight were earlier in the log
2025-09-10T15:55:35-06:00 2025-09-10T21:55:35.376Z INFO lightningd: Resolved invoice ‘869aea5cf4657cafa74cac64d18eff7a32795a063a3e8e46c3434220820de3b2-02cfb4639d0eedabf65ac5fcb5294617b5c2b301ae5c4ab8d559dce415e00d14cb-0’ with amount 3461000msat in 1 htlcs
Disconnected at 2025-09-10T16:10:59-06:00
Reconnected at 2025-09-10T16:10:59-06:00