Link to home
Create AccountLog in
Avatar of SoloComput
SoloComputFlag for Afghanistan

asked on

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.
Avatar of Simon Butler (Sembee)
Simon Butler (Sembee)
Flag of United Kingdom of Great Britain and Northern Ireland image

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.
Avatar of SoloComput

ASKER

@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
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.
ASKER CERTIFIED SOLUTION
Avatar of SoloComput
SoloComput
Flag of Afghanistan image

Link to home
membership
Create an account to see this answer
Signing up is free. No credit card required.
Create Account
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.