tags:

views:

355

answers:

2

I am working on Windows Server 2003 (IIS6), which has two asp.net sites running in seperate app pools. One of the sites has an ssl certificate installed and was running fine on https. The other site has no certificate and does not require https

The problem I have is that when I publish my app from vs2005 to the site with ssl the https urls stop working and I can only use http. The error I get is as follows

From Google Chrome: Error 104 (net::ERR_CONNECTION_FAILED): The attempt to connect to the server failed.

From IE7: Internet explorer cannot display the web page, could be unavailable, dns is not reachable etc

The strange thing is the first time this happened, https eventually became available but I don't know what triggered the availability but when I published an updated assembly to the bin folder of the site which does not require https, the OTHER site became unavailable on https again

Help much appreciated!

UPDATED: Thanks for the suggestions but it turns out that the firewall was not open on the ssl port

+1  A: 

If both webs use the same IP address, make sure, that only the web with the certificate uses the SSL port 443 (first property page). The input field should be empty for the insecure site.

If that is not the problem, you could try to debug stopping the web without certificate and restart the web server.

splattne
+1  A: 

Check if the firewall port for SSL (443) wasn't accidentally closed 443. ;-)

splattne