Submit a ticketCall us

ebook60.pngHow to be a Cisco® ASA ace

Our eBook, Thou Shalt Not Pass…I Think?! can help you overcome the challenges of monitoring and managing Cisco ASA firewalls. This eBook is a great read if you’ve been frustrated with monitoring firewalls, managing ACL configs, and troubleshooting VPN connections.

Get your free eBook.

Home > Success Center > Web Performance Monitor (WPM) > WPM - Knowledgebase Articles > 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