Using IIS 10 with SQL Server Management Studio, Can't Connect SSL from Go Daddy

Question

IIS 10 refuses to accept an SSL cert from Go Daddy/Starfield Tech. Self-signed won't allow an SQL connection. What have I done wrong? I have worked through SSL Certificate portal with a crt request, inserted at Go Daddy, received back new cert, used the RUN>MMC app on my pc to install. Starfield SSL cert doesn't appear under bindings. Did an IIS restart...

Please help- need this to work.

Answer 1

It sounds like you are experiencing issues with your SSL certificate setup in IIS 10, particularly with the certificate from Go Daddy. Here are some steps to troubleshoot and resolve the issue:

1. Check Certificate Installation: Ensure that the SSL certificate from Go Daddy is correctly installed on your server. You can do this by opening the MMC (Microsoft Management Console) and navigating to the Certificates snap-in. Verify that the certificate appears under the appropriate certificate store (usually under "Personal" for the local computer).
2. Bindings in IIS: After installing the certificate, you need to bind it to your website in IIS. To do this:
   • Open IIS Manager.
   • Select your website from the left pane.
   • Click on "Bindings..." in the right-hand Actions pane.
   • Ensure that there is an HTTPS binding for your site. If it’s missing, you will need to add it and select the correct SSL certificate from the drop-down list.
3. Check for Other Processes: Make sure that no other processes are using the SSL port (default is 443). You can use the command netstat -ano to check if another application is listening on that port.
4. Verify Certificate Chain: Sometimes, the issue might be with the certificate chain. Ensure that the intermediate certificates from Go Daddy are also installed. You can download them from the Go Daddy website and install them in the appropriate certificate store.
5. Restart IIS: After making changes, restart IIS to ensure all configurations are applied. You can do this by running iisreset in the command prompt.
6. SQL Server Configuration: If you are trying to connect to SQL Server using SSL, ensure that the SQL Server is configured to allow encrypted connections. You may also want to check the "Trust Server Certificate" setting in your SQL connection settings.

If you follow these steps and the issue persists, consider checking the event logs for any specific error messages related to SSL or IIS that could provide further insights into the problem.

---

References:

• Troubleshooting SSL related issues (Server Certificate)

Answer 2

Make sure the certificate was installed in the Certificates (Local Computer) > Personal > Certificates. If I recall, Certificates - Current User is the default. If the certificate is in Current User or elsewhere then IIS will not be able to see the certificate.

Even if the certificate is in the correct folder, it will not show up in the IIS Bindings dropdown if it is missing its private key. In the MMC Certificates snap-in, double-click the certificate. On the "General" tab, you should see a small key icon and the message: "You have a private key that corresponds to this certificate.