separate how 2 thing debug
1. node work by itself without nostr at moment
2. use 2nd anywallet wallet in profile see it works
join 1 +2 test again -
change something in profile push to verify
Discussion
I think I’ve worked around it. The web server logs showed some requests coming to the old address so either some relays hadn’t picked up the change or maybe some clients cache the profile information. I’ve now allowed zaps on both the old and new address to my node and I can zap myself on both so is hopefully fixed.
metadata corruption -> propagation related issue have impacted many users - big learning thing