Submit a ticketCall us

whitepaperYour VM Perplexities Called, and They Need You to Read This.

Virtualization can give you enormous flexibility with future workloads and can be a key enabler for other areas, like cloud computing and disaster recovery. So, how can you get a handle on the performance challenges in your virtual environment and manage deployments without erasing the potential upside? Learn the four key areas you need to be focusing on to help deliver a healthy and well-performing data center.

Get your free white paper.

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

Overview

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:

Environment

All WPM versions

Cause 

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.

Resolution

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

Tags

Classifications

Public