pull down to refresh
- Avoid exposing Alby Hub to the public internet. We recommend running it behind a firewall or within a private network. Thanks to NWC (Nostr Wallet Connect), Alby Hub's core communication protocol, your Hub does not need to be publicly reachable — it works perfectly on private servers or systems like Umbrel.
Maybe this gave me a false sense of security?
Well, I don't audit Alby Hub so I can't tell you for sure, but in general, if you have lnaddr / lnurlp exposed, even through tor, then you're potentially still exposed? If you only have NWC and no listeners whatsoever, then maybe you're good.
But don't take my word for it please, because I haven't checked.
NWC is providing a limited communication protocol between apps and a wallet through relays. This the wallet itself does not need (and should not be) publicly accessible for it to be used by any apps and doing things like lnaddr/lnurlp.
A LNURL just needs a NWC permission to create an invoice.
it's another layer.
Thanks for coming over!
So if someone has a 3rd party distribution like Umbrel or Start9, and it takes a while for them to get an update, the thing to make sure is that:
- public access to the management interface is disabled (how?)
- in general port 8080 (or whatever is configured as the hub listening port) is firewalled
correct?
Possibly off topic- One thing I have noticed, and I'm sure @Alby is monitoring this post, regarding Umbrel is that there is often a really long delay before Alby updates reach Umbrel. That is probably an Umbrel thing, and it doesn't effect this issue.