ForbiddenError while trying to use the deploy button
Closed this issue · 11 comments
In some cases you can receive the following error while trying to deploy an app to Azure:
.
I guess it might be related to some limitations of DreamSpark subscription because I have only it activated in my Azure account.
(This issue was transferred here from the original thread at madskristensen/MiniBlog#191)
Couple things to try:
- does https://portal.azure.com/ work for you?
- how about https://resources.azure.com/?
- when you get the error above, can you use F12 tools to get the request details?
Both sites are accessible and work fine:
I've captured the network traffic with IE F12 tools to a file http://1drv.ms/1DTZWC8
According to the log I get 500 HTTP error for https://deploy.azure.com/api/template?repositoryUrl=https:%2F%2Fgithub.com%2Fmadskristensen%2FMiniBlog
I'm guessing it's a Dreamspark specific issue. We'll need to investigate it.
Thank you for looking into this issue. Let me know if you need more details.
I reproed the issue with a Dreamspark subscription. Looks like the call we make to check if the site name is available is failing.
ForbiddenError: The server failed to authenticate the request. Verify that the certificate is valid and is associated with this subscription.
at Microsoft.WindowsAzure.Management.WebSites.WebSiteOperations.<IsHostnameAvailableAsync>d__114.MoveNext()
More investigation needed.
@davidebbo were you able to check this solution with DreamSpark subscription? I am still receiving the same error with 500 error code and the following response:
{"error":"ForbiddenError: The server failed to authenticate the request. Verify that the certificate is valid and is associated with this subscription.","exception":"Microsoft.WindowsAzure.CloudException: ForbiddenError: The server failed to authenticate the request. Verify that the certificate is valid and is associated with this subscription.\r\n at Microsoft.WindowsAzure.Management.WebSites.WebSiteOperations.d__114.MoveNext()\r\n--- End of stack trace from previous location where exception was thrown ---\r\n at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)\r\n at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)\r\n at Slingshot.Controllers.ARMController.d__5d.MoveNext()\r\n--- End of stack trace from previous location where exception was thrown ---\r\n at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)\r\n at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)\r\n at System.Runtime.CompilerServices.TaskAwaiter.ValidateEnd(Task task)\r\n at Slingshot.Controllers.ARMController.d__4a.MoveNext()"}
Sorry, not yet, I shouldn't have closed this. I did get a fix on the staging site, but it seems it runs into additional issue.
You can give it a try by going to https://deploy-staging.azure.com/?repository=https://github.com/Tuesdaysgreen/HelloWorlddemo. You shouldn't get the error above, but might run into a new one. Let me know.
You were right. I was able to proceed with the deployment form and schedule a deployment process but it ended with the following error:
{"operations":{"value":[{"id":"/subscriptions/e1cef2f7-14c7-487d-be6f-71b29ac4b042/resourceGroups/HelloWorlddemo2c6f/deployments/HelloWorlddemo2c6f/operations/390D6FF15819DCF4","operationId":"390D6FF15819DCF4","properties":{"provisioningState":"Failed","timestamp":"2015-05-20T15:04:08.9775528Z","duration":"PT3.4492455S","trackingId":"63d11168-db52-41e7-b681-4dcc060f5efe","statusCode":"Forbidden","statusMessage":{"error":{"code":"BadRequest","message":""}},"targetResource":{"id":"/subscriptions/e1cef2f7-14c7-487d-be6f-71b29ac4b042/resourceGroups/HelloWorlddemo2c6f/providers/Microsoft.Web/serverfarms/HelloWorlddemo2c6f","resourceType":"Microsoft.Web/serverfarms","resourceName":"HelloWorlddemo2c6f"}}}]},"provisioningState":"Failed"}
Yes, that's what I get too. There must be some more differences with those accounts that I need to isolate.
Ok, this time it's fixed for real! I tried the button from miniblog (https://github.com/madskristensen/MiniBlog), and it all worked.
@davidebbo, I've tried to deploy the MiniBlog and successfully created a new web application under my DreamSpark subscription without any errors or warnings.
Thank you for you help, David!