I removed my NIP05 verification because it only seemed to be showing up on Damus for some reason (and not on any other clients).
Working on troubleshooting the issue, I followed all instructions and all the files at my domain host seemed to be fine so not sure why it wasn't working.
You probably didn’t publish your kind 0 far enough; this is a good use of blastr
We can see it on Amethyst.. IMO is a good thing to have
Weird. Will fix it when I’m back home next week
if it worked on Damus, but not other clients, it sounds like it's a CORS issue. 9 times out of 10, it's always a CORS issue.
What’s the resolution if that’s the case??
I’m currently using cors parameters copy pasta’d from w3docs.com:
Header set Access-Control-Allow-Origin "*"
Header set Access-Control-Allow-Methods "GET, POST, PUT, DELETE, OPTIONS"
Header set Access-Control-Allow-Headers "Content-Type"
…SSL absolutely necessary or nah?
Remove leading and trailing spaces; many clients didn't catch those early on.
I did some checking and.....
https://btcgandalf.com/.well-known/nostr.json gives me a 404 error. Make sure you create the nostr.json file in that location. To do so...
Copy the nostr.json file from my site: https://m.rtijn.info/.well-known/nostr.json and replace the long hex string with the hex of your npub. Hint: it's:
ee0e01eb17fc6cb4cd2d9300d2f8945b51056514f156c6bc6d491b74496d161a
Upload to the location specified in the first step. Your nip05 will be @bitcoingandalf (without anything in from of the @ is much cooler)
Hope this helps! 🧙♂️ If not, feel free to ask me. Here to help.
I’m having the same problem!
I had the same problem. I needed to add wildcard Allow Origin header to my htaccess and that fixed it.
I’m having the same problem too.. Are you running a wildcard SSL? I have Header set Access-Control-Allow-Origin "*" in my htaccess file but did you need to actually include the word wildcard in that line?
👀
Do you have an SSL cert?
I can investigate ...
