Documentation forWeb Performance Monitor

WPM 2026.2 system requirements

Release date: June 9, 2026

SolarWinds strongly recommends that you install the SolarWinds Platform on a server that is neither public, nor internet-facing. To learn about best practices for configuring your SolarWinds Platform installation securely, see Secure Configuration for the SolarWinds Platform.

Web Performance Monitor 2026.2 runs on the SolarWinds Platform and has the same base requirements as SolarWinds Platform 2026.2.

See the SolarWinds Platform 2026.2 system requirements for details.

Additional requirements specific to Web Performance Monitor 2026.2 are detailed below.

Note the following details about system requirements:

Port requirements

Return to top

The following port requirements apply to the primary WPM installation on the SolarWinds Platform server. For remote machines, see Web Transaction Recorder and WPM Player requirements.

Port # Protocol Service/Process Direction Description Encryption
17781 TCP WPM Playback Player Bidirectional

Used for communication between the SolarWinds Platform server and remote systems that host WPM Players.

 
17782 TCP WPM Playback Player Bidirectional

Used for WPM Player-initiated communications.

 
17783 TCP WPM Playback Player Bidirectional

Used for automatic WPM Player updates.

  
17784 TCP WPM Playback Player Bidirectional

Used for inter-process communication between the WPM Playback Player service running on the SolarWinds Platform server, an APE, or a remote machine, and the following local apps running on systems that host WPM Players:

 

Web Transaction Recorder requirements

When you install the SolarWinds Platform, two different WPM recorders are added to the SolarWinds Platform server automatically. You can also deploy recorders to remote systems.

Here are minimum requirements for remote systems that host a Web Transaction Recorder, which is based on Chromium 138.0.7204.251:

Resource Requirement
CPU 1 GHz or more
Memory 2 GB
OS
  • x64 systems only
  • Windows 10, 11
  • Windows Server 2016 and 2019
    • WPM uses Electron 37.9.0 with Chromium 138.0.7204.251, which support only the operating systems listed above.

    • Keep Windows scale and layout settings set to 100% to support image validation.

The following macOS versions are supported:

  • Sonoma
  • Ventura
  • Monterey
  • Big Sur
  • Catalina
TCP ports
  • 80, for HTTP traffic
  • 443, for HTTPS traffic
  • 445, for automated remote deployment to target systems by the Agent installer via Microsoft-DS SMB file sharing.
  • 17777, for SolarWinds traffic
  • 17774, for outgoing traffic port for SWIS
  • Two random ports between 1024—65535 for inter-process communication between recorders, probes, and drivers

    Configure firewalls to support binding for random ports 127.0.0.1:1024—127.0.0.1:65535.

WPM Player requirements

Return to top

Note the following details about remote systems that host the WPM Player Playback service and play recorded transactions at scheduled intervals:

  • If a system hosts a hypervisor or Virtual Machine Monitor (VMM) that runs other servers (such as print or file servers), consider hosting the WPM Player elsewhere.
  • To manage loads on systems that host WPM Players, see Scalability Engine Guidelines for SolarWinds Platform Products. You can also check the Player Load Percentage widget.
  • The WPM Player Playback service is based on Chromium 138.0.7204.251.
  • If not already installed, you may be prompted to verify the installation of:
    • Microsoft Visual C++ 2015-2019 x86 Redistributable
    • Microsoft Visual C++ 2015-2019 x64 Redistributable

The following requirements apply to remote systems that host WPM Players:

Resource Requirement
CPU Quad core processor or better
Memory 3 GB
.NET Framework .NET 4.8 or later
Operating system
  • Windows 10*, 11*
  • Windows Server 2016* and 2019*

WPM uses Electron.js 37.9.0 with Chromium 138.0.7204.251, which support only the operating systems listed above.

*Steps with certificate validation may interrupt playback, as described here.

Do not install WPM on domain controllers, or on Microsoft SharePoint, Microsoft Exchange, or BlackBerry servers.

Accounts and security
TCP ports
  • 80, for outbound HTTP traffic
  • 135, for executing remote code during WPM Player deployment
  • 443, for outbound HTTPS traffic
  • 445, for automated remote deployment to target systems by the Agent installer via Microsoft-DS SMB file sharing.
  • 17777, for outbound SolarWinds traffic
  • 17781, for bidirectional, server-initiated (passive) communication mode
  • 17782, for bidirectional, player-initiated (active) communication mode
  • 17783, for bidirectional, automatic WPM Player updates
  • 17784, for bidirectional, inter-process communication between:

In addition, allow a random port between 1024 and 65535 for inter-process communication between WPM players, probes, and drivers.

Configure firewalls to support the binding of a random port, between 127.0.0.1:1024 and 127.0.0.1:65535.
Windows settings

The following settings are updated during WPM Player deployment:

  • Net.Tcp Port Sharing Service: The Startup Type is set to Manual on the SolarWinds Platform server and any Additional Polling Engines (APEs). On remote systems, the Startup Type is set to Automatic.
  • SolarWinds WPM Playback Player service: A dependency with the Net.Tcp Port Sharing Service is added.
Web browser

Internet Explorer 11

If your organization requires an earlier IE version, use IE 11 Document Mode to emulate earlier versions.