nostr:npub1y3uh89v5a4vq92t8q0j6su94zhvcdxpywjn3l6hpsr5welarqtrqj7yzhd I'm having issues with my new node and new LN address. I'm starting to wonder if it's a Cloudflare issue. If so, you're going to be so happy 🤣🤣

Reply to this note

Please Login to reply.

Discussion

Connect up Logflare to check access logs in real-time. And if you're using their WAF you can check if some security sensitivity is getting in the way.

It has some WAF rules deployed but turned them off for this test. They aren't the issue at least right now.

He is going to love this. A told you so incoming

Dude! It is Cloudflare! As soon as I turned off their reverse proxy everything worked. Now I have to figure out why and how I can use their reverse proxy and have my shit work.

I still blame dns

U mean nsaflare?

Why are you using cloud flair?

Reverse proxy to hide my home IP

What is a reverse proxy? What is your threat model?

Derp right.

The order of blame goes Cloudflare > DNS. 🤣

It was their bot blocker. I fixed it. I spent way way too much time figuring this out. But we're good now 🤣

It's always DNS until it isn't 🤣

Do you allow them to do where they decrypt your traffic and use their certs? Anyone allowed to decrypt traffic to monitor what my node is doing sounds scary. Even from the meta data angle.