Thursday, 17 January 2013

Azure Deployment Fails for SSL

I got the following error when trying to deploy an Azure project. This project had previously (successfully) been deployed but I was trying to move it to another subscription:

13:35:01 - Preparing deployment for AzureWeb2 - 17/01/2013 13:34:56 with Subscription ID 'xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx' using Service Management URL ''...
13:35:01 - Connecting...
13:35:06 - Object reference not set to an instance of an object.
13:35:06 - Deployment failed with a fatal error

(The short answer is I hadn't uploaded ALL of the SSL certs to the service I was deploying to.)

The problem was not noticeably described anywhere in any more detail and I couldn't find anything on Google that described how to log the error except that a manual deployment might help.

I worked out that I could upload to blob storage via the server explorer in Visual Studio and then "upload a deployment" from inside the management portal which then gave a more useful error:

"The certificate with thumbprint 01e3910d7f7cxxxxxxxxxxxxa1aa4b3de11c77f5 was not found."

This obviously explained the problem but what was confusing was that although I had two certificates linked to the project, only 1 of these was specified on an endpoint (this second one was a test certificate) so it seems strange that the deployment itself failed rather than a failure at runtime. It would also have been nice if Visual Studio displayed the same error as the management portal did!.

Anyway, as you might expect, once I also uploaded the second cert, it was all fine.
Post a Comment