https://community.splunk.com/t5/Security/SSL-Error-for-Connection-between-Forwarder-and-Indexer/m-p/328060#M8429 <P>Hi All</P> <P>Below are the Errors I see in Splunkd.log of Forwarder and Indexer.<BR /> &amp; trying to figure out how to fix these.</P> <P>Indexer:<BR /> <STRONG>04-11-2018 23:17:41.461 +0000 ERROR TcpInputProc - Error encountered for connection from src=FORWARDERIP:xxxx. error:140890C7:SSL routines:ssl3_get_client_certificate:peer did not return a certificate</STRONG></P> <P>Forwarder:</P> <P><STRONG>04-11-2018 16:23:44.127 -0700 ERROR TcpOutputFd - Read error. Connection reset by peer<BR /> 04-11-2018 16:23:44.137 -0700 ERROR TcpOutputFd - Read error. Connection reset by peer<BR /> 04-11-2018 16:23:44.137 -0700 WARN TcpOutputProc - Applying quarantine to ip=INDEXERIP port=9997 _numberOfFailures=2<BR /> 04-11-2018 16:24:26.550 -0700 WARN TcpOutputProc - Tcpout Processor: The TCP output processor has paused the data flow. Forwarding to output group splunk-app-infra-autolb-group has been blocked for 100 seconds. This will probably stall the data flow towards indexing and other network outputs. Review the receiving system's health in the Splunk Monitoring Console. It is probably not accepting data.<BR /> 04-11-2018 16:25:13.704 -0700 INFO TcpOutputProc - Removing quarantine from idx=INDEXERIP:9997</STRONG></P> <P>Thanks All</P> Tue, 29 Sep 2020 18:58:59 GMT PowerPacked 2020-09-29T18:58:59Z https://community.splunk.com/t5/Security/SSL-Error-for-Connection-between-Forwarder-and-Indexer/m-p/328060#M8429 <P>Hi All</P> <P>Below are the Errors I see in Splunkd.log of Forwarder and Indexer.<BR /> &amp; trying to figure out how to fix these.</P> <P>Indexer:<BR /> <STRONG>04-11-2018 23:17:41.461 +0000 ERROR TcpInputProc - Error encountered for connection from src=FORWARDERIP:xxxx. error:140890C7:SSL routines:ssl3_get_client_certificate:peer did not return a certificate</STRONG></P> <P>Forwarder:</P> <P><STRONG>04-11-2018 16:23:44.127 -0700 ERROR TcpOutputFd - Read error. Connection reset by peer<BR /> 04-11-2018 16:23:44.137 -0700 ERROR TcpOutputFd - Read error. Connection reset by peer<BR /> 04-11-2018 16:23:44.137 -0700 WARN TcpOutputProc - Applying quarantine to ip=INDEXERIP port=9997 _numberOfFailures=2<BR /> 04-11-2018 16:24:26.550 -0700 WARN TcpOutputProc - Tcpout Processor: The TCP output processor has paused the data flow. Forwarding to output group splunk-app-infra-autolb-group has been blocked for 100 seconds. This will probably stall the data flow towards indexing and other network outputs. Review the receiving system's health in the Splunk Monitoring Console. It is probably not accepting data.<BR /> 04-11-2018 16:25:13.704 -0700 INFO TcpOutputProc - Removing quarantine from idx=INDEXERIP:9997</STRONG></P> <P>Thanks All</P> Tue, 29 Sep 2020 18:58:59 GMT https://community.splunk.com/t5/Security/SSL-Error-for-Connection-between-Forwarder-and-Indexer/m-p/328060#M8429 PowerPacked 2020-09-29T18:58:59Z https://community.splunk.com/t5/Security/SSL-Error-for-Connection-between-Forwarder-and-Indexer/m-p/328061#M8430 <P>Can you try adding <CODE>requireClientCert= false</CODE> to inputs.conf to use splunk default certificate if you didn't set any custom certificate. <BR /> Refer below docs:<BR /> <A href="https://docs.splunk.com/Documentation/Splunk/7.0.3/Security/ConfigureSplunkforwardingtousethedefaultcertificate">https://docs.splunk.com/Documentation/Splunk/7.0.3/Security/ConfigureSplunkforwardingtousethedefaultcertificate</A></P> Thu, 12 Apr 2018 06:49:33 GMT https://community.splunk.com/t5/Security/SSL-Error-for-Connection-between-Forwarder-and-Indexer/m-p/328061#M8430 p_gurav 2018-04-12T06:49:33Z