It's 3 in the morning and I'm googling how to handle punycode in nginx.
Discussion
What's the difficulty you're having? I've hosted a few punycode sites on nginx and just used the ASCII version in the config files. Everything worked without an issue?
Thanks... but after verifying no, nothing to do with punycode and nginx. For months I've been running my nip5 as a serverless cloudflare worker and it stopped working... yesterday updated everything and restarted and it worked for a few hours... and then broke again...
So I double checked nginx and everything and everything is... as it should be...
Got a funny feeling it's something to do with cloudflare's new paid workers plan. Maybe I was using something that needs the new paid plan.... next step to debug after I grab some breakfast!
nostr:npub1mqcwu7muxz3kfvfyfdme47a579t8x0lm3jrjx5yxuf4sknnpe43q7rnz85
nostr:nprofile1qqsdhqcp7zgw4fk87txza3ggtr5p5sl9km54kvpcg73wzcy3me7c0lqpp4mhxue69uhkummn9ekx7mqpr4mhxue69uhkummnw3ez6ur4vgh8wetvd3hhyer9wghxuet5qyw8wumn8ghj7mn0wd68ytnzd96xxmmfdejhytnnda3kjctvne85hv is dealing with a problem setting up his NIP-05 (a way to verify identity on Nostr). Here’s what’s happening..
- **Initial Issue** His NIP-05 setup worked before, but recently stopped working.
- **First Guess** He thought it might be related to punycode and nginx configuration (punycode helps handle non-English domain names).
- **New Discovery** After checking, nginx wasn’t the issue. The setup is fine there.
-**Cloudflare Suspect** Don now thinks the trouble might come from Cloudflare’s updated Workers plan. Maybe he was using a feature that’s now locked behind a paid tier.
- **Next Step?** He’s going to eat breakfast, then come back to test if upgrading or changing his configuration fixes the problem.
- **In short** Don learned that his NIP-05 problem isn’t about punycode or nginx, but likely a change in Cloudflare’s rules. He’ll try adjusting his plan or setup to solve it.
to be continued... lol