Splunk Enterprise

WARNING: Cannot decrypt private key

rayar
Contributor

Getting the below  on Splunk restart 

 

Waiting for web server at https://127.0.0.1:8000 to be available...............................WARNING: Cannot decrypt private key in "/opt/splunk/etc/auth/splunkweb/illinsplunkprd01.corp.amdocs.com.key.pem" without a password. Network communication with splunkweb may fail or hang. Consider using an unencrypted private key for splunkweb's SSL certificate.

 

Labels (1)
0 Karma

thambisetty
SplunkTrust
SplunkTrust

if you just have below 

should I leave the below only ? 

[splunk@illinsplunkprd01 etc]$ cat ./system/local/web.conf
[settings]
httpport = 8000

then ssl will not be enabled.

if you want to enable SSL, you need to follow the procedure I mentioned in my first answer.

————————————
If this helps, give a like below.
0 Karma

thambisetty
SplunkTrust
SplunkTrust

NOTE: secret key should be removed from mySplWebPrivKey.key before creating CSR and signing the CSR.

web.conf

 

[settings]
httpport = 8443
enableSplunkWebSSL = true
privKeyPath = $SPLUNK_HOME/etc/auth/directory/mySplWebPrivKey.key
serverCert = $SPLUNK_HOME/etc/auth/directory/es_web_ssl.pem

 

# Remove passphrase as Splunk Web doesn't support cert with passphrase
openssl rsa -in mySplWebPrivKey.key -out mySplWebPrivKey.key

————————————
If this helps, give a like below.

rayar
Contributor

Thanks for your inputs 

This is my web.conf 

 

[splunk@illinsplunkprd01 etc]$ cat ./system/local/web.conf
[settings]
httpport = 8000

#SSL configuration
enableSplunkWebSSL = true
privKeyPath = /opt/splunk/etc/auth/splunkweb/illinsplunkprd01.corp.amdocs.com.key.pem
serverCert = /opt/splunk/etc/auth/splunkweb/illinsplunkprd01.corp.amdocs.com.cer.pem
[splunk@illinsplunkprd01 etc]$

 

should I leave the below only ? 

[splunk@illinsplunkprd01 etc]$ cat ./system/local/web.conf
[settings]
httpport = 8000

and run the below steps  ? 

openssl x509 -enddate -noout -in /opt/splunk/etc/auth/server.pem

 rename /opt/splunk/etc/auth/server.pem to server.pem.back and restart splunkd.

./splunk restart

0 Karma
Get Updates on the Splunk Community!

Detecting Brute Force Account Takeover Fraud with Splunk

This article is the second in a three-part series exploring advanced fraud detection techniques using Splunk. ...

Buttercup Games: Further Dashboarding Techniques (Part 9)

This series of blogs assumes you have already completed the Splunk Enterprise Search Tutorial as it uses the ...

Buttercup Games: Further Dashboarding Techniques (Part 8)

This series of blogs assumes you have already completed the Splunk Enterprise Search Tutorial as it uses the ...