I’m not super impressed with OCEAN right now and going to move some hash back to Braiins. Currently I have Braiins payout being sent to a Speed wallet. BTW- I would not suggest using Speed as they require KYC to withdraw funds. Boo.
So…without getting ahead of the upcoming tutorials I’m trying to setup Alby but as usual confusion is in the air.
Alby says: Low receiving limit
You likely won’t be able to receive payments until you swap out funds or increase your receiving limits.
So…I imagine a swap would be the way to go? I have a Spending Balance of 550,000, Receive 0, On-chain 133,00. When I click on Swap I get this window…
Without revealing upcoming content inside your upcoming videos…what the heck do I do here @paul
Reason: I’m going to be bringing 90TH/s unit online in a 2 weeks and participate in two pools. If you would rather not jump ahead of tutorial I do understand. The current videos I see online speak to the Cloud hub for Alby which I do not want to participate in as I’d rather self host on Start9.
Your channel with ACINQ is 100% outbound. You likely want to move most of that out (typically, you would send it to cold storage, but you could send it to a hot wallet or to your Lightning node’s base layer wallet). That will create inbound liquidity on that channel (which is what Alby is referring to).
The important point there is just “No Route” (the rest is contextual info for debugging purposes in case it is useful). There are typically two things that cause that:
Not enough liquidity on the nodes you are connected with to handle the transaction amount
Not enough outbound was left on the channel to meet the min channel balance
In both cases, breaking the invoice into smaller chunks usually resolves the problem. The drawback of course is that you pay more than one base layer transaction fee, so best to do this when the fee rates are low.
A third possible cause:
The max fee rate you specified (or the default if you didn’t set this) is too low. I typically select 2% for maximum fee rate and don’t ever see the fees get that high. This is why I don’t use the swap feature, and instead create the invoice directly on Boltz.exchange, and pay it from RTL (which lets me select a max percentage where I can enter “2”)
I’ve not run into that problem before, but maybe we can try to step through the process to see what is breaking. Lightning-address resolution is a two-step LNURL-pay flow:
Payer turns USERNAME@getalby.com into https://getalby.com/.well-known/lnurlp/USERNAME (LUD-16)
It fetches that JSON and then calls the callback URL it returns to pull a BOLT-11 invoice.
So starting with the .well-known JSON, let’s make sure that is working. Run the following (should work on Linux or Mac, let me know if you are on Windows instead, or if this returns an error) Replace USERNAME with your Alby username:
If that returns a good JSON file, post it here (feel free to replace your username in the callback and metadata fields if you don’t want to share your actual LNURL address).
Ok, so your “well-known” JSON file looks fine. Next, lets make sure Alby is able to generate an invoice at all. Replace USERNAME with your Alby username to generate a 200 sat invoice:
If Alby is having a problem creating an invoice for your node, you will likely see:
{
“invoice”: null
}
If you get a big JSON output that includes an invoice (starting with something like “lnbc…”), let me know. I don’t need to see the output, just confirm whether or not it has an invoice generated.
That is the minimum “keysend” amount (measured in milisats – i.e. the minimum is 1 sat)
Yep. Invoice created. I did try and create an invoice inside the GUI by clicking receive and fill in an amount. Doing this does create a lightning invoice with a address lnbcblahblahblahblahblahblah.
If i just copy the alby address and paste it into the Funds financial account that is when Braiins shows the alby address failing. (image above)
If I paste in my speed address then Braiins see it as an lightning invoice…(as above image shows).
I might request a payout from Braiins via lighting using an invoice generate in Alby and see what transpires.
To better assist you, could you please let us know which wallet you used to interact with Braiins and generate the Lightning address? This will help us confirm compatibility and ensure the correct setup.
Also, for payouts like these to work seamlessly, it’s important that your wallet and node are properly validated on the Alby RPC Portal. This validation step ensures that the Lightning address is recognized correctly and can parse invoices properly—especially when using self-hosted setups like on Start9.
If you’re not a Pro member, payouts might still work, but proper configuration and validation on the RPC portal is required to avoid any miscommunication between services.
Let us know the wallet in use, and we’ll guide you from there
I’ll have to put my thinking cap back on a bit later and parse what they are saying.
No record of the invoice is found in Alby. Sent the invoice to Braiins and it was verified as a legit invoice. Braiins tried to pay but payment failed. Something is broken on the Alby side evidently.
What was it that @Fletcher said about lightning…it’s so easy it’s hard! (or something to that effect).
I’ll have to wait 24 hours to “demand payment” from Braiins again (their policy). This time I’m going to try it all from the RTL side.
Alby support is flaky at best…I don’t think they know either but I might be to judgemental today. At this point CL works way smoother in my opinion…but then again…maybe I’m being to dense.
Not sure what it means. IMO, Core Lightning looks beautiful and simple from a UI/UX perspective. If only they could fix the routing issues.
I honestly don’t do much with Alby + LND – I use it for Alby Go (lightning payments for lunch down at the Steak N Shake) and for Nostr zaps. For everything else related to Lightning, I use RTL + LND. The one exception is Ocean mining, which requires Core Lightning for payouts (and I’ll be dropping that too as soon as LND supports offers)
