Question

My azure website is working fine with http. Now, I have added a self-signed certificate and a binding in IIS 7. When I run the application with https, I get certificate error warning. When I confirm ‘run anyway’. Then I get ‘http service 503 unavailable’ continuously only with https. My binding is correct(because I am seeing certificate error first time). No log found in IIS log files. Tried, IIS Failed-request tracing, no log found. I have confirm that iis user can register both port 80 and 443(using netsh). Any idea?

Edit: The site is now working if I use specific IP in binding. But when I chnage this to ‘All Unassigned’ I got the same error? why?

Answer 1

Based on above details it is not sure how it is done? Are you doing all of above RDP to Azure VM by manual binding or some startup process? Adding HTTPS endpoint to Azure Web Application is very easy and it should be done the pre-define process and there is nothing manual as you described above. This is how it is done:

1. Add an HTTPS Endpoint and bind a SSL certificate to it during development time in Windows Azure application
2. Deploy this SSL certificate (in PFX) to your “Certificate” section in Windows Azure Portal
3. Deploy your application to Windows Azure

How it works:

1. When Azure VM start the SSL certificate is provisioned to Windows Azure VM
2. Based on your Service Configuration and Definition settings IISConfigurator process include the certificate with your Web Application
3. When your web role starts, the binding are done based on Azure VM internal IP address. “All assigned” is not used instead the binding is done to specific internal IP address.

My this blog talk about how to add a HTTPS endpoint to Windows Azure application.