I installed a new certificate on IIS 8.0 and added SAN attributes in the certificate so Chrome, IE reports the cert as secure, everything on the surface is working fine.
However, after a server reboot, anyone tries to browse a URL that is a level down in the directory structure causes a 500 error, but then I have them open the root of the site, say,https://abc.123.com this loads fine, then they can loadhttps://abc.123.com/requirements/index.cfm successfully.
So in a nutshell, Monday morning after server reboot:
https://abc.123.com/requirements/index.cfm ---- causes 500 error for all users when pasted in the browser.,
I have them load https://abc.123.com and it's good.
Then I have them open a new browser to try https://abc.123.com/requirements/index.cfm again and now it works fine, and is good until the IIS server is rebooted again (end users reboot their machines, no problems, so I think its IIS)
Any ideas as to why I need them to load the root URL first? Is the TLS certificate not happy when they try to go to a folder a few layers down in the directory of the site? Steve