Closed AlexIvanHoward closed 7 months ago
Subscribing to this issue since I'm also having the same problem.
Hey @armarik. Envision suggested to me a few hours ago that I should create another w3 space and then regenerate the IPFS_STORAGE_KEY and IPFS_STORAGE_PROOF. I did it and it solved the problem. Super weird, though - my previous space, key and proof were all perfectly valid and functioning.
Hi @AlexIvanHoward, thanks for reaching out. That's weird, my IPFS provider is set to local instead of web3storage; I can try and switch it to web3storage and see if it makes any difference, I guess.
Problem description
Since upgrading our Guardian instance to v2.20.1 (released on 10 January 2024) I cannot set up a standard registry user - whether it be the built-in "demo" StandardRegistry or a new one.
Step to reproduce
Steps to reproduce the behavior:
Expected behavior
One should be able to create a standard registry user.
Screenshots
Screenshot 1:
Screenshot 2:
Screenshot 3: