Yup, all that's been done, and unfortunately
doesn't help me further my understanding of
the structure of the model in use.
The 500 error I'm receiving is a generic error
without further explanation. The following XML
code was what I received from my ISP that I
can reportedly add to my web.config file to get
more detailed failure messages reported in my
error logs:
Code:
<configuration>
<system.webServer>
<httpErrors errorMode="Detailed"/>
</system.webServer>
</configuration>
I haven't added it yet. I'm currently waiting for
their tech support to confirm the SSL on 80 and
443. Then I need to go looking for my config.php
and check my SSL status there.
When I add the XML, the error may raise its head
again, in which case I'll hopefully have a better
snapshot taken of its failure mode.
Then? I dunno. :-j