SSL configurations causing Splunk Add-ons Input page loading error - Request failed with status code 500

Available Languages

Updated:September 29, 2026
Document ID:SPLK045990

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

Description

With SSL fully enabled.

$SPLUNK_HOME/etc/system/local/server.conf

[sslConfig]
sslPassword = xxxxxxxx
enableSplunkdSSL = True

the following error appears when trying to load the inputs page of any Technical Add-on (TA)

Screen Shot 2022-12-10 at 11.15.14 am.png
 

 
 
 

Investigation

It was observed that if SSL is disabled, the issue does not appear, and the TA input page  works as expected.

$SPLUNK_HOME/etc/system/local/server.conf
 

[sslConfig]
sslPassword = xxxxxxxx
enableSplunkdSSL = false

 

Example from AWS TA

 

 

image.png

 
 

Resolution

The issue is related to the  uppercase "T" in the $SPLUNK_HOME/etc/system/local/server.conf

As per SSL/TLS Configuration details change the following in $SPLUNK_HOME/etc/system/local/server.conf 

From 

[sslConfig]
sslPassword = xxxxxxxx
enableSplunkdSSL = True

To

[sslConfig]
sslPassword = xxxxxxxx
enableSplunkdSSL = true


 


SSL TLS Configurations

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