This may indeed have been an issue with Brave's proxying layer (Hello, I'm Sampson from the Brave team). I was able to reproduce the user's screenshot by settin

This may indeed have been an issue with Brave's proxying layer (Hello, I'm Sampson from the Brave team). I was able to reproduce the user's screenshot by setting up an AutoResponder in Fiddler to serve a 401 Unauthorized response from go-updater.brave.com, which yielded the "Access Denied" message in the Chrome Web Store. I'm not aware of any issue where this endpoint authentically served a 401 response, but it's entirely possible the user happened to catch a rare, transient event. I'm checking with my team either way.