I have been doing some setting changes for both the lightning node and the bitcoin node opening it to clearnet connections and sending it to my address stopped working.
Initially, I suspect this might be incorrect DNS records for my domain, but now I don’t believe this is the case and don’t know what else to check.
I have triple-checked DNS settings and also baked new macaroons.
I have made the setup for another domain with the same results.
I have loaded the default setup to both Lightning and Bitcoin nodes (closed clearnet inbound).
No matter what I always get the Lnurlp error. Any ideas what else to check are welcome.
Waiting support, sorry for the perhaps basic question, but have you tried checking if your node is listening on port 9050 or if there’s a firewall drop?
I have even set the port forward on the router to the internal IP of Umbrel to test the theory. Still the same error…
The thing is the connection from the bridgeaddr to Umbrel is Tor. I have limited knowledge about Tor, but I think, the onion address should point the traffic to the right machine directly (Umbrel) and REST will come from one of the Tor exit nodes. If the connection is refused by Umbrel LN proxy, there has to be another reason for that.
I will dig further…
I didn’t find any solution and don’t know how to debug further… It’s sad as it was working before.
In the end, I have configured the BTCpay server on my Umbrel node so now I have the lightning address working and the Pay button as a bonus.
It took me less time (2 hours) to follow this excellent guide:
I hit this issue while trying to setup a lightning address. I thought it was my node but it turned out to be the bridgeaddr service that was throwing the error. I used the same DNS params with https://satspay.to/ and it worked first time. Not quite identical, unless you run your own service, but useful to test your node.
