Only if the VPN is blocking nostraddress servers specifically.
But your configuration on nostraddress is definitely wrong.
Discussion
Ok how do I fix this ? To make the npub the same for both clients, and signing notes with the same npub across clients ? Again, thank you for all your help I super appreciate it.
On Nostr address, you have to register your user with this hex key:
6f2a40b0be331a2aa81f4445cf4d5c24b4a7de197177e86636c5af5dfee020e8
Then it says my username is taken 😂 oh lort halp me
Are you using the paid or the free versions?
Freebie..
Hum.. that's first come first serve... :(
So are you saying I just need to use a different "username" for my NIP-05 because if that's the case that's no big deal, I just want to make sure both clients have the correct npub and signing with it.
Yeah, just paste that code in their website and wait about an hour to update.
Ok so it confirmed the new username I chose worked with the hex you provided, and when I pasted the new username in my Amethyst it automatically updated in the Primal client and shows the check in primal but still won't in Amethyst.. I will give it a little time but it worked immediately in the primal client..
Frankly, I don't know what primal is doing. There is no THEDISTRICT registered in the site yet (it is still updating).
Lol all good, I just thought it was odd that when I updated my NIP-05 I'm Amethyst that it updated it Primal as well without going to the Primal client, which to me says we are using the correct npub but I'm no web3 dev..
You can see the list of all usernames they have here: https://nostraddress.com/.well-known/nostr.json?name=THEDISTRICT
or here if you are using the "verified" domain:
https://nostrverified.com/.well-known/nostr.json?name=THEDISTRICT
This also just showed a extremely large string of black and white code
Woahhh that just brought up a bunch of black and white code 😅😬