Hey Jonathan:
Unfortunately, I'm not receiving any other than a generic 403 error.
I have not found the time yet to try to see if this IIS driven. (or hook up Fiddler to see the traffic) but I did look at the built in IE F12 tools and all I'm seeing there is just 403.
I'll try to create a new virtual directory and see what happens.
Edit: So, yes Jonathan, I believe you are correct, this is an IIS issue.
When going to a new site as http, I get a 403.4 error.
Both the default web site and the two WA sites (Portal and Server) have Require SSL set in IIS.
What I don't recall, is if I did this or if it is done automatically during the installation.
I believe it happens during the IIS setup in the Chef cookbooks but I could have just as easily done it by hand.
Or does it get set when you bind the CA Cert to the website?
Removing the "Require SSL" in IIS (Default, Portal and Server) fixes the issue and once again allows for an HTTP/HTTPS portal.
Thanks!
One question: if I re-enable "Allow access to the portal through HTTPS only." via My Organization>Edit Settings>Security
Do I need to reset "Require SSL" in IIS?
My recollection is that this was needed originally to make things work correctly with HTTPS only?
I checked and just checking that box in Portal does not set the flag in IIS.
I guess the question is, when is this setting in IIS required?
Will that override the settings in Portal and AGS?
I would think so, if going through the WA.