pull down to refresh

I'm having issues sending out payments from my Alby node. I'm able to receive, but I also have plenty of outbound liquidity and also inbound, so I'm not sure what's going on here.
Can any one here help me troubleshoot this issue? I've emailed Alby as well and they've responded to my first email, so we'll see what they also say.
I appreciate the help, first time encountering this issue. Happy to share more details if need be. Thank you.
Is the little up arrow green on your wallet connection? Probably not, I guess. This has happened to me a few times. I would just delete your SN send connection, go to the Alby store, get another one, and follow the directions for send to get your new secrets.
reply
Not sure what little green arrow you're talking about? In the alby hub on my node? On the Alby Go app? I don't see an arrow on either one of those. The light is green on my Alby Hub
reply
On your stacker news wallet connection
reply
It is green. Like I said, I'm able to receive, but not able to send out. I have plenty of outbound and inbound liquidity.
reply
Did you open a channel to SN?
reply
I don't. I'm not sure why I would need to?
Both send and receive are green? If so, I'm stumped
reply
Looking into your logs you've sent me, I found this:
FAILURE_REASON_INCORRECT_PAYMENT_DETAILS
That means the invoice you received could contain blinded-paths that are incorrectly interpreted by your node and/or the invoice contain route hints that cannot be reached, or is using something wrong in that invoice.
reply
Interesting. I was attempting to send out from my Alby to Boltz that would go then to my cold storage.
reply
Hello Do you use your own node ? Make sure your Bitcoin node is fully synced before you start using your Lightning node. This sync ensures that your node is running smoothly and can interact effectively with the Lightning Network. After that I suggest you use alby go
reply
Yes, a Start9. Node is fully synced to Bitcoin Core (latest). Using Alby go. Can receive, can not send. There is enough inbound/outbound.
reply