Submit a ticketCall us

Have You Auto Renewed? If not, you're missing out.
The SolarWinds Renewal Program comes with a host of benefits including the most recent product updates, 24/7 technical support, virtual instructor-led training and more. Experience all of this with the convenience of Auto Renewal, and never worry about missing any of these great benefits. Learn More.

Home > Success Center > Patch Manager > HTTP 404 error when adding WSUS server to Patch Manager Console

HTTP 404 error when adding WSUS server to Patch Manager Console

Updated July 19, 2017


The following error is displayed when testing the connection after adding WSUS using the Add or Configure WSUS server option on the Patch Manager Web Console:

Could not connect to server: [server name]

Exception occurred at MM/DD/YYY: The request failed with HTTP status 404: Not Found.

WSUSConnection::Unable to connect to the WSUS Server [server name] using the account: [account name].

The request failed with HTTP status 404: Not Found.


All Patch Manager versions
Note: In this case, Patch Manager and WSUS are installed on the same server.


The Network Service permission is not added on the WSUS administration website in IIS Manager.

The error describes that WSUS is connecting using HTTP ports 80 and 8530 and port 80 is already used by the default website in IIS Manager.


  1. Open IIS Manager.
  2. Click Sites > WSUS Administration > Bindings, and then add HTTP 8530.
    Note: WSUS on Windows Server 2012 defaults to port 8530 (HTTP). WSUS on Windows Server 2008 R2 defaults to port 80 (HTTP).
  3. Click Application Pool, and then disable the default website.

   3. Right-click WSUS Administration, select Edit Permission > Add Network Service.


Disclaimer: Please note, any content posted herein is provided as a suggestion or recommendation to you for your internal use. This is not part of the SolarWinds software or documentation that you purchased from SolarWinds, and the information set forth herein may come from third parties. Your organization should internally review and assess to what extent, if any, such custom scripts or recommendations will be incorporated into your environment.  You elect to use third party content at your own risk, and you will be solely responsible for the incorporation of the same, if any.


Last modified