Resolving "503 Service Unavailable" Error

    Applies to:
  • Legacy SecureAuth IdP
Deployment model:
  • On Premises
  • Description:
    User receives a 503 Service Unavailable error when accessing https://localhost/secureauth0/localAdmin.aspx


    To resolve "503 Service Unavailable" issues, there are two main items to look at:

    - SecureAuth0 account

    • SecureAuth0 account must be a member of the local Administrator's group.
    • Ensure the SecureAuth0 account is not locked or disabled.
    • If theappliance has been joined to the domain, ensure there are no GPOs limiting the rights of local service accounts.

    -SecureAuth0Pool Application pool

    • SecureAuth0 local account/application pool configuration password mismatch. You can run Start > All Programs > SecureAuth > "Refresh_SecureAuth0" to refresh the password and set the application pool.
    • Run Start > All Programs > SecureAuth > "Reset File Perms and Shares" to ensure the basic permissions have been refreshed.
    • If you suspect .NET is corrupt, you can "repair" .NET 4 using the add programs console or downloading it from Microsoft.
    For other causes, please see here

    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


    1 comment
    • This can also happen when the D drive does not have anymore space.

      Comment actions Permalink

    Please sign in to leave a comment.