HTTP Event Collector (HEC) SSL certificates not working

Available Languages

Updated:September 28, 2026
Document ID:SPLK044380

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

After configuring SSL certificates for HEC on Heavy Forwarders (HFs), Splunk still takes the default certificates, not the ones created.


Investigation

Things to consider:

  • SSL is currently configured only in web.conf. Configure SSL for HEC separately.
  • Use self-signed certificates, not web certificates.
  • Web certificates remove private key passwords, but self-signed certificates used for HEC  keep the password.
    How to self-sign certificates  private key uses the password
    How to self-sign certificates

    Self-sign certificates for Splunk Web when creating a new private certificate for Splunk Web remove the password.
    Self-signcertificatesforSplunkWeb
     

Resolution

The SSL certificate for HEC configured on web.conf file has a private key without a password,
Follow the following document steps to generate a private key with a password to resolve the issue.
Generate a key for your server certificate




Revision History

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

Was this Document Helpful?

FeedbackFeedback

Contact Cisco

This Document Applies to These Products

Related Articles