This #nostr verified address (NIP-05) thing is frustrating. Why do some clients show it as working, yet other show (!) or unable to verify? I (believe) I have a valid formatted .json file. Any tips/tricks? #asknostr #nostrhelp #anyone?

Reply to this note

Please Login to reply.

Discussion

It's showing as fine in your #Amethyst profile, so it's fine, it's working!

Thanks. I’ve noticed a few that don’t work. Time to move on…

Looks good to me.

Fiddling around with the nip-05 files on my servers but it just won't work. Doesn't matter which one I try.

I had to add a "_config.yml" file to my root containing the text "include: [“.well-known”]" to expose the .well-known directory to searches. Try that if you haven't already.

Nope I did not. Will try later.

Cors test shows it's working via http.

Seems like SSL is misconfigured.

I had to fix my CORS header settings - now the infamous little tick mark is showing across all the clients I've tested with. #sigh

In amethyst still red. But nostrudel is fine after making the nostr.yml file that where suggested here. Which changes to cors?