https://community.splunk.com/t5/Splunk-Search/Curl-Command-SSL-Error-on-Search-Head/m-p/742880#M240975 <P>thank you for the update, all the search head having same pem file.&nbsp;</P> Thu, 27 Mar 2025 22:04:24 GMT harishsplunk7 2025-03-27T22:04:24Z https://community.splunk.com/t5/Splunk-Search/Curl-Command-SSL-Error-on-Search-Head/m-p/742871#M240971 <P><SPAN>We have a total of five search heads, and while four of them are successfully executing the&nbsp;</SPAN>curl<SPAN>&nbsp;command, one search head is encountering an SSL error, specifically a&nbsp;</SPAN>SSLError<SPAN>&nbsp;with a curl status of 408.&nbsp;</SPAN></P><P><SPAN>HTTPSConnectionPool(host='localhost', port=8801): Max retries exceeded with url: /servicesNS/nobody/alert/saved/searches/alert/acl (Caused by SSLError(SSLCertVerificationError(1, '[SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: self signed certificate in certificate chain (_ssl.c:1106)')))</SPAN></P><P><SPAN>what is the&nbsp; next steps to identify and resolve the root cause of this SSL error.&nbsp;</SPAN></P> Thu, 27 Mar 2025 19:57:32 GMT https://community.splunk.com/t5/Splunk-Search/Curl-Command-SSL-Error-on-Search-Head/m-p/742871#M240971 harishsplunk7 2025-03-27T19:57:32Z https://community.splunk.com/t5/Splunk-Search/Curl-Command-SSL-Error-on-Search-Head/m-p/742872#M240972 <P>The cause is in the error message: "certificate verify failed: self signed certificate in certificate chain".&nbsp; Make sure all of the search heads have the same PEM file.</P> Thu, 27 Mar 2025 21:16:28 GMT https://community.splunk.com/t5/Splunk-Search/Curl-Command-SSL-Error-on-Search-Head/m-p/742872#M240972 richgalloway 2025-03-27T21:16:28Z https://community.splunk.com/t5/Splunk-Search/Curl-Command-SSL-Error-on-Search-Head/m-p/742880#M240975 <P>thank you for the update, all the search head having same pem file.&nbsp;</P> Thu, 27 Mar 2025 22:04:24 GMT https://community.splunk.com/t5/Splunk-Search/Curl-Command-SSL-Error-on-Search-Head/m-p/742880#M240975 harishsplunk7 2025-03-27T22:04:24Z