Sadly I get this a lot using the btcpayserver self custodial zaps.

Back to getalby

nostr:nevent1qqs0d26rfc8gtcu30wzmdy7v27u9ntz6qdtfpu5fnzjzktalr0phthqpz3mhxue69uhhyetvv9ujuerpd46hxtnfdupzqj5kregwqxq369mmyjk5avhv5lzm47t5j38mm24czytpjd72ak77qvzqqqqqqyeg9f6e

Reply to this note

Please Login to reply.

Discussion

Yeah, self-custody apps might be kinda garbage in general, tbh. I use Exodus and it's pretty trash ass if I'm being honest.

Same and same. I just can't get it working.

Were you running btcpayserver over a VPN or cloudflare tunnel from home or via cloud?

Wondering if this is a btcpayserver problem or a dns one πŸ€”

Lololololololol - you even have to ask?

It's not DNS.

It’s always dns. Even when it’s not, it is.

If this was a work conversation I would say it was DNS.

Cloudflare.

I'm running cloudflare too, I noticed it sometimes has problems when cloudflare changes your IP. Peers can't find me on thunderhub etc

Potentially DNS πŸ€” (their provider still pointing to old cloudflare IP?)

Oh my problem is that the zaps don't happen. They just go through as normal lightning tips.

Why that is? Tor or ?

Primal doesn't work for my self custodied one either. I think it may be because I have a subdomain in the URL at the end of it

A few things helped with my BtcPayServer zaps.

1. Compress LND database on BtcPayServer. Should improve performance overall.

2. Run LNbits on top of BtcPayServer's LND node to handle zaps instead of the built-in zaps setup.

Good suggestions! I will try

You can get a lightning address with zap support directly to your own node on lnaddress.com , the service provider (me) could change the invoice so not fully trust less but less trust than Alby