I realised I missed a step in the Cloudflare configuration. A public hostname needs to be set up to forward to port 17423 as this is the port that nostdress listens on. I’ve updated the guide to include this step.
Discussion
Thanks. But after submitting the lightning node data (I used the one returned from my umbrel node"Connect to your node) I got the following error:
But I got couldn't make an invoice with the given data: Post "http://xxxxxxxxxxxxx.onion:8080/v1/invoices": proxyconnect tcp: dial tcp 127.0.0.1:9050: connect: connection refused
(Of course the xxxxx is my LND REST Host)
Any idea?
After changing Type in https of the cloudfare Public Hostname Page I got a little futher!
Now I got this.....

I used the LND REST (Local Network) rather than tor since I’m not running Tor on the Raspberry Pi that I’m running nostdress on. I also used used my Umbrel host’s IP address rather than the host name.
To complex for me.
I now also fucked up with the CNAME configuration because the Tunnel Id mismatched with the one in content of cloudfare.
This is way beyond my expertise.
Only the real linux professions can solve this.
But thanks for your help.
I go to sleep it is 6 am in the morning here in Malta.
Gn
It works!!!! Thank you
t4es5ter5@bitbubblex.com is my new lightning address
phil@nostrpurple.com ❤️❤️❤️❤️❤️
It worked I received 111sats directly on my node and they are zap counted!!!!!!!!..
THANK YOU
No worries, I’m glad you got it working. Let me know if there was anything you found in the guide that wasn’t correct or explained more clearly.
A couple of things
* You can use The Tor Lnd Rest host. Simply use https://
* You cannot use the Macaroon in "Connect a wallet to your node" specified in Umbrel.
You have to convert this to a hex one. I did this xxd -p admin.macaroon
I still cannot a new WAF in cloudfare.
In Cloudfare you cannot go to Account Home -> WAF anymore. Maybe they have moved this. I have to find out where to create a custom ruleset in Cloudfare.
For the rest your instruction is very good to follow!
Thanks again and let me know if you know how to create a custom ruleset to block URLs.
I read this:
Account-level WAF configuration requires an Enterprise plan with a paid add-on.
I’m just using the free plan and had the option to set it up..
Really? If have no option for it
Yeah I’ve just checked it is still there. From the main Cloudflare dashboard, I select my website, then Security, then WAF and can create up to 5 rules.
Interesting, I sure I used the macaroon from the “Connect a wallet” page in Umbrel so I’m mot sure what has changed. I’ll check on the Cloudflare WAF configuration a little later on to see if they have moved that option.

So it requires an enterprice plan to create a custom rules set.
Is it safe to delete my public hostname or does the whole thing not work anymore?


