Navigating to the PortalGuard website after completing the PortalGuard install and configuration results in this default IIS webpage appearing:
The PortalGuard MSI creates the new PortalGuard Website and assigns it to port 80 by default. On a standard IIS installation, there will always be the Default Website which is also pointing to port 80. Because the default site is already running and bound to port 80, the PortalGuard website is not able to bind to port 80 and does not start.
There are 3 distinct solutions to this situation:
- If not needed, delete the Default Website and then start the PortalGuard website.
- Change the Default Website to a port other than 80 (81 or 8080 are commonly used) and then assign port 80 to the PortalGuard website and click start to get it operational.
- Change the PortalGuard website to a port other than 80 and click start to get it running on the new port. The hostname for the PortalGuard server will have to have the new port specified after the name on the URL. Ex. http://portalguardwebsite:81.