"Server Error" messages in WebUI while performing searches in SHC

Available Languages

Updated:September 29, 2026
Document ID:SPLK048529

Bias-Free Language

The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.

Applicability

Splunk Enterprise 9.1.5

Description

The following error message appears intermittently in any SHC member in the WebUI while performing searches:

 

Server Error message UI


Investigation

This was a SHC with 5 Search Heads hosted in the AWS Public Cloud, with huge resources and ALBs (Application Load Balancers) routing the traffic to them.

 

The initial theory was that the issue was related to the browser or cache, as it disappeared after refreshing the browser page. The following was suggested:

 

  • Try different browsers
  • Try private browsing
  • Clear SplunkWeb's cache 

 

However, none of these resolved the issue. The user captured a HAR dump when a "Server Error" message occurred. To investigate the dump, Support used the HAR Analyzer tool, which provided the following:

 

  • Request:

Please note that the HTTP Version was http/2.0.

 

  • Server: awselb/2.0

 

  • Response: 
<html>
<head>
<title>502 Bad Gateway</title>
</head>
<body>
<center>
<h1>502 Bad Gateway</h1>
</center>
</body>
</html>
<!-- a padding to disable MSIE and Chrome friendly error page -->
<!-- a padding to disable MSIE and Chrome friendly error page -->
<!-- a padding to disable MSIE and Chrome friendly error page -->
<!-- a padding to disable MSIE and Chrome friendly error page -->
<!-- a padding to disable MSIE and Chrome friendly error page -->
<!-- a padding to disable MSIE and Chrome friendly error page -->

 

This confirmed the issue was on the ALB's side. Upon researching these 502 errors, the following community was found: Fixing 502 errors when front-ending Search Heads with an AWS application load balancer.


Resolution

Disabled HTTP/2.0 on ALB's side. Kindly note that the other configurations mentioned in the community are intended for users experiencing connection timeouts.

Revision History

Revision Publish Date Comments
1.0
29-Sep-2026
Initial Release

Was this Document Helpful?

FeedbackFeedback

Contact Cisco

This Document Applies to These Products

Related Articles