SharePoint Stack Exchange is a question and answer site for SharePoint enthusiasts. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I created a web app (, then extended it (AAM) to I also created a Site Collection called with our subsites under that (to mimic our 2007 install). All above sites & subsites utilize SSL successfully (https://sharepoint2, etc and https://sharepoint, etc. The problem is I've created a new Site Collection ( and it works using either the sharepoint2 or sharepoint URL, however, but not using the https URL. SSL does not work. In IIS, we had previously defined both http and https for but only http for In an attempt in resolving this issue, we added the binding for https to in IIS but that causes to be completely inaccessible.

Could someone please offer some advice? Thanks!!

share|improve this question
This is a little confusing. You said sites utilize ssl successfully then you say you added binding to and it doesn't work. Can you detail each site and the AAM setup for each? Each AAM has to be setup in IIS bindings as well. – David Lozzi Mar 27 '12 at 14:40
My apologies. Our main Web App is Under that are site collections and our recently created Months ago, I created the AAM which points to All works fine for those sites - SSL and non-SSL access. Our new site ( does not work using SSL. In IIS, I have two entries under Sites and http & https is defined on sharepoint2 but only http on sharepoint. If I add https binding to sharepoint, it no longer loads. – user4747 Mar 27 '12 at 15:02
up vote 1 down vote accepted

The, from what I have gathered, is the URL you want to use. This site should have the SSL setup on it, not sharepoint2. If users are going to use securely, that'll need the SSL as well, but I think that's not the case. If it is, then you need a unique IP per site running SSL, so you'll need 2 IPs for both sites.

I think you want the following

Web App default AAM internet AAM extranet

Again, if you want will need it's own IP in IIS.

Check out this blog post, might help clarify it a little

share|improve this answer
Thanks for replying! Correct - (or https) is the URL that our users use and it works (ideally no one should be using - that was the temp setup to allow us to move content over from 2007). The problem is that the new site collection at doesn't work at Perhaps IIS isn't the place I should be looking? Sorry - for not explaining it clearly. Reading your blog post now. Thanks!! – user4747 Mar 27 '12 at 16:42
thinking through it some more, does this site collection reference anything using the other URL? Custom masterpage including assets? Check the ULS logs for an error? – David Lozzi Mar 27 '12 at 16:48
You're answer was the solution. We hadn't setup a secure AAM. I find it odd that one site collection worked via https but the other didn't the way it was configured but I'm ok with that now that it works. Thank you!!! – user4747 Mar 27 '12 at 18:37
I'm glad it worked! IIS will handle the request so that port 443 (SSL) will go to the website setup for it, and if the host header is setup on the same site, not necessarily the same port, it may trick SharePoint into thinking it's setup correctly. Always best to set it up correctly ;) – David Lozzi Mar 27 '12 at 19:09

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.