• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 811
  • Last Modified:

Cannot start default website

This is SBS 2008/Exchange 2007

I noticed today in IIS that the Default Website is not started. All the other sites look ok though. When I tried to start it, I got a message saying that the site could not be started because another website may be using the port.

Is it something is SBS that is doing this? Or is something completely seperate? And how would I track it down. I've tried browsing to port 80 on that machine. Nothing comes up.

Ian
0
ipendlebury
Asked:
ipendlebury
  • 3
  • 2
1 Solution
 
merowingerCommented:
Like the errors already points to - There is another website running on the default websites's port. Can you choose another ip address for the website?
Could you post a screenshot of the bindings?
0
 
ipendleburyAuthor Commented:
As far as I know, this is a default installation of SBS. I would hope that I didn't have to use another port. I took a look at the bindings.  the  http has got www.ourdomain.com bound to port 80 and the https is bound to 443

Interestingly I changed to port 81 and still got the same message. So I changed the https to 444 and then it would start normally. So i've got something else using port 443. But this is strange because for instance, OWA is still available on https://www.ourdomain.com/owa 

So I am still wondering if SBS is causing this?
0
 
saku99Commented:
in SBS 2008 OWA is nor running in default web site container but in the SBS Web Application container

For the default web sites container leave port 80 but remove 443 from the bindings that is the default configuration.
0
Cloud Class® Course: Microsoft Azure 2017

Azure has a changed a lot since it was originally introduce by adding new services and features. Do you know everything you need to about Azure? This course will teach you about the Azure App Service, monitoring and application insights, DevOps, and Team Services.

 
ipendleburyAuthor Commented:
I just tried to remove the https bind. It gave me a message:

"The certificate associated with this binding is also assigned to another site's binding. Deleting this binding will cause the HTTPS binding of the other site to be unusable. Do you still want to continue>"

What should I do?
0
 
merowingerCommented:
0
 
ipendleburyAuthor Commented:
That did it. Thank you very much
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Free Tool: SSL Checker

Scans your site and returns information about your SSL implementation and certificate. Helpful for debugging and validating your SSL configuration.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

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