Troubleshooting: 404 Error Browsing to a SecureAuth Realm

Follow
    Applies to:
Deployment model:
  • On Premises
  • Version Affected: All
     
     

    Overview

    Browsing to a SecureAuth realm's URL shows IIS's HTTP Error 404.0 - Not Found page, and/or the realm does not appear in the Admin Console's realm list.

    IIS 8.5 Detailed Error page showing HTTP Error 404.0 - Not Found for a request to https://localhost/SecureAuth3, with the Physical Path listed as D:\inetpub\wwwroot\SecureAuth3.

    This detailed error confirms the request reached IIS, but IIS has no site or application configured to answer it.

     

    Cause

    The realm's application is missing from IIS Manager under the Default Web Site — it was removed, or was never added after the realm's folder was created.

    IIS Manager's Default Web Site application list, with a red arrow pointing at a gap in the sequence of SecureAuth realm applications where one is missing.

    IIS treats each realm as its own application under the site, so a missing application means IIS has nothing configured to handle requests for that realm's path.

     

    Resolution

    1. Open IIS Manager and right-click Default Web Site.
    2. Click Add Application.
    3. Enter the realm's name as the Alias (for example, SecureAuth3), and set the Application Pool to .NET v4.5.
    4. Browse to the realm's Physical Path folder (for example, D:\SecureAuth\SecureAuth3).
    5. Click OK.

    Add Application dialog in IIS Manager, with Alias set to SecureAuth3, Application pool set to .NET v4.5, and Physical path set to D:\Secureauth\SecureAuth3.

    The realm is back in IIS Manager and should be reachable again.

     

    SecureAuth Knowledge Base Articles provide information based on specific use cases and may not apply to all appliances or configurations. Be advised that these instructions could cause harm to the environment if not followed correctly or if they do not apply to the current use case.

    Customers are responsible for their own due diligence prior to utilizing this information and agree that SecureAuth is not liable for any issues caused by misconfiguration directly or indirectly related to SecureAuth products.

    0 out of 0 found this helpful

    Comments

    0 comments

    Please sign in to leave a comment.