pull down to refresh

and in config, hitting test on the receive config works too?

I'll test that now, but I misspoke earlier. I also had Zeus connected to receive, and checked the logs:

I don't know what this is worth, though, because my Zeus connection has been failing for a while and I stopped playing with it.

reply

So what I do right now is I disable all my backup for each side, so that I have only 1 green icon at a time - one for send and one for receive. (And I delete the ones that don't work.)

If something goes wrong, I just enable another one. I sometimes got an invoice QR, which is ez to pay too.

reply

Maybe you can figure something out with this info: I couldn't zap your last comment even with an LN address with Alby, receiving an NWC failure. I could with my Zeus wallet, which connects to an LND node through LNC.

reply

According to the alby status page they still have an outage going on:

From what I can tell, SN itself is working fine. I'm both receiving zaps and sending zaps to many stackers (but using CLINK over Justin's relay, not NWC)

reply

I am using a wallet (not alby) connected to SN via NWC with no problem today or yesterday, so I don't think it's a nostr issue.

reply

I'm receiving some zaps from SN now, but it's not managing to pay out my rewards from yesterday.

reply

test & save your wallet receive config should trigger it on the current prod commit, unless it failed within the last few minutes.

reply

It still doesn't seem to like the msats

I received yesterday and through the night with NWC. Maybe it's the specific relay your NWC uses?

reply

depends on the relay(s) used in your nwc connection string!

reply

I will try that

reply

I just retested the send and receive connections on Alby and they both failed.

reply