Azure SSL Certificate

Question

I am running into an issue when uploading my SSL certificate to Azure. I have a premium certificate from GoDaddy that has been running in IIS for the past year. As we are migrating to Azure, I exported it to a PFX, went to Azure to add it to my Web App, and received the following error message:

Failed to update web app settings
Failed to update web app settings for [APP_NAME]: The password is incorrect, or the certificate is not valid

I have tried the following:

• Ensure password is correct
• Export from IIS as pfx
• Export from MMC as pfx with full paths available

They all have the same results with the error message. Does anyone have any ideas?

Answer 1

So I got the certificate uploaded. The new Azure portal failed, so for a long shot, I tried the old portal which uploaded it without any issues.

Hopefully this helps someone else out in the future.

Answer 2

I had a similar issue using the "https://portal.azure.com" trying the approach "App Service - "your app service" - ssl certificates - upload certificate"

When I tried to upload a certificate PFX file nothing happend, no error message, nothing.

The workaround I found was to re-generate the PFX file using openssl and this time add a short and simple password.

"openssl pkcs12 -export -out certificate.pfx -inkey privkey.pem -in cert.pem -certfile chain.pem"

Hope this helps

Answer 3

This is my case: I used tool to OpenSSL for windows to generate pfx file by using command openssl pkcs12 -export -out domainname.pfx -inkey privatekey.key -in doamainname.crt.

When I upload certificate domainname.pfx to Azure portal I got the following error: "The password is incorrect, or the certificate is not valid." After struggling a lot I did the following:

1. Imported my domainname.pfx file to IIS locally.(Open IIS -> Select your machine name in the left menu -> Select Server certificates in the middle window -> On the right Action side select Import). It will ask pass for pfx file.
2. Export pfx certificate from IIS. (Select imported certificate in the middle window and then click Export on the right side of IIS window). It will ask you a new pass for a new pfx file and path where you want to save it.
3. After doing points 1,2 I uploaded newly created pfx file to Azure and Azure accepted it.

For me it's not still clear why local IIS was able import inital PFX file, but Azure not, looks like a bug in Azure. Cheers!