Closed mattttt closed 8 years ago
latest changes have been deployed.
Thanks! When you get a moment, can you fill me in on what the issue was and what was different about those accounts?
The ns1 demo account had a rdns zone which had a "/" in the zone name. As the zone name is included in the url it needed to be url encoded.
Dobt know avout vayl's account. You mention a "permission denied" can you elaborate on what you mean or add a screenshot. The only error i am aware of is backend 404 error caused by the zone names.
This issue has been largely addressed via Slack, but will create a proper issue here to fix.
Short version. Some accounts work great, other accounts (Vayl persona, and ns1 demo) do not. We're receiving permission denied, despite the permissions being the same on the NS1 side.
Shannon can help troubleshoot, but would like to see the snap code and better error logging to troubleshoot.
@woodsaj When you're back in action, this is one of our high priorities. It's a blocker before they can start testing with customers.