Want to protect your cyber security and still get fast solutions? Ask a secure question today.Go Premium

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 396
  • Last Modified:

SBS 2008 SSL/Port issue

I have an SBS 2008 server set up.  It has a GoDaddy SSL cert that has no issues.

Each time the server reboots, the default Web Site binds to port 443, the SBS web applications then fails to start as there is a conflict for port 443.

I have edited the .config file previously to keep it from recurring but that now does not stop the issue, I must be missing a step, missing a file or doing it in the incorrect order.  After each reboot the configuration resets.

Also, I have to re-enable the certificate in the exchange shell after starting the service (at least that was one of my troubleshooting steps, it may no longer be necessary.
0
SoloComput
Asked:
SoloComput
  • 3
  • 2
1 Solution
 
Simon Butler (Sembee)ConsultantCommented:
The mistake you made was to use Exhcange to enable the certificate.
SBS makes a ton of changes to the IIS configuration, which affects Exchange as well.

In Exchange, disable the SSL certificate you have.
Then in the SBS management console, run the SSL wizard, choosing to use an existing certificate. Select your GoDaddy certificate and SBS will do the rest.

I cover this exact scenario on my web site: http://semb.ee/2007ssl

Simon.
0
 
SoloComputAuthor Commented:
@Sembee2, that may be so but it does not resolve the primary issue which is that after each reboot, the default website automatically takes port 443
0
 
Simon Butler (Sembee)ConsultantCommented:
That is because you enabled the certificate using the Exchange tools instead of the SBS tools. You have to undo that. If you setup the server using the wizards, which is how it is designed to be done, then everything works correctly.

Simon.
0
 
SoloComputAuthor Commented:
Thanks Simon but that is not the issue, nor the solution.  Using Exchange PS to enable the certificate is not the problem, it is the standard way of working with exchange certificates.  The issue of the default website binding to 443 with the self signed or third party certificate is widely found and the only seeming solution is to monitor and delete the config.xml files for IIS occasionally because updates to IIS will cause the problem to happen again once it starts to happen.
0
 
SoloComputAuthor Commented:
After searching google and applying multiple fixes this is the only one.  The proposed answer by Simon ignored the key issue which was that the SSL was being issued to the incorrect site due to IIS configuration issues.  As well the documented methods of applying the certificate using the Exchange shell is the standard accepted by microsoft.
0

Featured Post

VIDEO: THE CONCERTO CLOUD FOR HEALTHCARE

Modern healthcare requires a modern cloud. View this brief video to understand how the Concerto Cloud for Healthcare can help your organization.

  • 3
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now