Network Management

EOC – HTTP/HTTPS Not Working After Enabling Certificate (403.7 on Login.aspx)

After enabling HTTPS on the EOC web site, the EOC console becomes inaccessible and browsers display HTTP 403.7 (client certificate required) when accessing the site (including /Orion/Login.aspx).

First published date

3/19/2026 3:53 PM

Last published date

3/19/2026 4:25 PM

Overview

Environment

  • Product: SolarWinds Enterprise Operations Console (EOC)

  • Components: EOC Web Console (IIS)

  • Change: HTTP only → HTTP + HTTPS (certificate bound in IIS)

Symptoms

After enabling HTTPS on the EOC web site:

  1. Web console not accessible over HTTPS

    • Browsing to the EOC URL returns a 403 – Forbidden page:

      • Browser shows similar to:
        “Access to <servername> was denied. You don’t have authorization to view this page. HTTP ERROR 403.”

    • IIS logs show status 403.7 for requests like. The error is found in C:\inetpub\logs\LogFiles\W3SVC1 and then look for the latest log file

      2026-03-18 21:41:12 ... GET / - 443 ... 403 7 ...
      2026-03-18 21:45:21 ... GET /Orion/Login.aspx - 443 ... 403 7 ...
      
      • 403.7 = Client certificate required.

       

Product section

Enterprise Operations Console

Cause

Cause

The issue is caused by IIS configuration on the EOC web site:

  1. IIS SSL settings misconfigured when enabling HTTPS

    • In SSL Settings, Client certificates is set to Require.

    • IIS then expects a client certificate on every HTTPS request.

    • Because typical browsers do not send a client certificate, IIS returns 403.7 – Client certificate required, and the SolarWinds login page never loads.

Resolution

Resolution

Follow these steps in order.


Step 1 – Correct IIS SSL settings (remove client certificate requirement)

  1. On the EOC server, open Internet Information Services (IIS) Manager.

  2. In Connections, expand Sites and select the EOC web site (for example, SolarWinds EOC).

  3. In the center pane, double‑click SSL Settings.

  4. Under Client certificates:

    • Change from Require to Ignore (recommended) or Accept.

    • This stops IIS from demanding a TLS client certificate for normal browser access.

  5. Decide whether to enforce HTTPS:

    • If you want HTTPS only:

      • Leave Require SSL checked.

    • If you want HTTP and HTTPS:

      • Uncheck Require SSL and ensure there is a valid http binding.

  6. Click Apply in the Actions pane.

Step 2 – Correct IIS Authentication for the SolarWinds Platform application

  1. In IIS Manager, expand your EOC site and select the SolarWinds Platform application.

  2. In the center pane, double‑click Authentication.

  3. Configure a known‑good baseline:

    • Anonymous AuthenticationEnabled

    • Windows Authentication:

      • Enabled if you use AD/SSO for Orion/EOC

      • Disabled if you only use local SolarWinds Platform/EOC accounts

    • All other methods (Basic, Digest, Forms, ASP.NET Impersonation, etc.) → Disabled, unless specifically required by your security design.

  4. Click Apply.

  5. In the Actions pane, click Restart for the SolarWinds EOC site or run iisreset.

Result: IIS no longer returns 403.7 and requests are allowed to reach /Orion/Login.aspx.