I’ve got a self hosted WCF service, and an ASP .Net web site that need to run on the same machine. I’ve discovered that when the self hosted service is running, all calls to port 443 intended for IIS (based on IP and host header/SSL bindings) get routed to the WCF architecture, and so the website stops working as long as the self hosted service is running. It’s effectively pre-empting IIS’ ability to do it’s job.
Note that IIS still works fine on other ports, like port 80. It’s just over-eager on port 443. Not entirely sure whether this is a server issue or a code/wcf issue.
After quite a bit of research, I was able to determine that one of the service endpoints, a REST endpoint set to simulate a crossdomain.xml file was pre-empting IIS. Otherwise everything was working as expected. I ditched that endpoint and used IIS to serve the file instead.