Submit a ticketCall us

Solarwinds & Cisco Live! Barcelona
Join us from the 29th of January to the 2nd of February at Cisco Live 2018 in Barcelona, where we will continue to show how monitoring the network with SolarWinds will keep you ahead of the game. At our booth (WEP 1A), we will demonstrate how SolarWinds network solutions can help. As a bonus, we are also hosting a pre-event webinar - Blame the Network, Hybrid IT Edition with our SolarWinds Head Geek™, Patrick Hubbard on January 24th - GMT (UTC+0): 10:00 a.m. to 11:00 a.m. There's still time to RSVP.

Home > Success Center > Web Performance Monitor (WPM) > Transaction down with Bad Gateway error: StatusCode HTTP_STATUS_BAD_GATEWAY

Transaction down with Bad Gateway error: StatusCode HTTP_STATUS_BAD_GATEWAY

Updated July 18, 2017


This article addresses the issue where a WPM Transaction report is down with a Bad Gateway error. The following error is found in the WPM AgentWorker_v2_2_XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX_[XXXX].log file (default location: C:\ProgramData\Solarwinds\Logs\SEUM on the agent):

[SolarWinds.SEUM.Agent.Worker.exe][UI Thread] WARN  SolarWinds.SEUM.Browser.EventProcessors.BrowserEventProcessor - Navigate error: URL: https://SomeSiteToBeMonitored.local/...AndInformation, StatusCode: HTTP_STATUS_BAD_GATEWAY, TargetFrame:


All WPM versions


The HTTP_STATUS_BAD_GATEWAY error is an HTTP protocol error with error number 502. The server, while acting as a gateway or proxy, received an invalid response from the upstream server it accessed in attempting to fulfill the request. This is generally passed from a proxy to WPM.

If this error has been detected there is likely an issue between the proxy and the site being monitored which needs investigation.


Review the proxy and determine the cause of the invalid response. If you are unable to determine the root cause between the proxy and the remote server, remove the need to use the proxy.



Last modified