I have been at this for days now, and cannot get the SSL certificate (issued from GoDaddy), that I installed on my Azure VM's and binded to my website to work properly. After everything is done, I still get the below error:
Websites prove their identity via certificates. Firefox does not trust this site because it uses a certificate that is not valid for 52.191.190.38. The certificate is only valid for the following names: manifestmanager.xyz, www.manifestmanager.xyz
...
Error code: SSL_ERROR_BAD_CERT_DOMAIN
...
https://52.191.190.38/
Unable to communicate securely with peer: requested domain name does not match the server’s certificate.
On GoDaddy, I have the following setup for my domain "manifestmanager.xyz":
Domain Name: manifestmanager.xyz
DNS Configuration on manifestmanager.xyz:
Records
Type Name Value TTL
A @ 184.168.131.241 600 seconds
CNAME www manifestmanager.westus2.cloudapp.azure.com 1 Hour
CNAME _domainconnect _domainconnect.gd.domaincontrol.com 1 Hour
NS @ ns69.domaincontrol.com 1 Hour
NS @ ns70.domaincontrol.com 1 Hour
SOA @ Primary nameserver: ns69.domaincontrol.com. 1 Hour
Forwarding
DOMAIN
http://manifestmanager.westus2.cloudapp.azure.com
SUBDOMAIN
Not set up
On Azure.
VM Name: MMApp
VM Public IP: 52.191.190.38
Virtual network/subnet: MMGroup-vnet/default
DNS name: manifestmanager.westus2.cloudapp.azure.com
To set up the SSL.
1. I purchased a Standard SSL Certificate from GoDaddy and applied to the GoDaddy domain that I purchased: "manifestmanager.xyz"
2. On my Azure VM IIS Manager, I created a certificate request. For the Common Name, I used manifestmager.xyz
3. On Godaddy, under Manager Certificate (for the SSL Certificate that is applied to the manifestmanager.xyz domain, I select Re-Key your certificate. Then, I copy and past the certificate request data (from the generated file from previous step) and submit the update.
4. After GoDaddy process this update, I receive an email. Then I download the IIS certificate files and copy to my VM.
5. Using the VM's Certificate Manager, I import the .p7b file to the Intermediate Certification Authority Folder.
6. Using the VM's IIS Manager, I complete the certificate request by using the .crt file.
7. Using the VM's IIS Manager, I bind this SSL Certificate to my web site (https, port 443).
8. I restart the web site.
All of these steps work, but I still get a common name error or server name error on the SSL certificate. I have tried many different things to vary the common name, such as the VM's public IP, VM's DNS name. What am I doing wrong. These are all the steps I know to do, based on everything I've researched.