<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Splunk Http Event Collector Socket Error in Security</title>
    <link>https://community.splunk.com/t5/Security/Splunk-Http-Event-Collector-Socket-Error/m-p/502876#M11469</link>
    <description>&lt;P&gt;I've been trying for a few days now to setup a HEC on a Splunk Heavy Forwarder and having issues with the splunkd process binding to the default tcp/8088 port.&lt;/P&gt;

&lt;P&gt;I can see this error within the splunkd.log&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;FATAL HTTPServer - Could not bind to port 8088
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;However, I can verify that my localhost is listening on the port &lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;netstat -tulpn | grep 8088
tcp      129      0 0.0.0.0:8088            0.0.0.0:*               LISTEN      13924/splunkd
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;Also you can notice the queue filling up on that port &lt;/P&gt;

&lt;P&gt;I've configured the Splunk HEC global settings on the Splunk Web UI already and enabled the http input in the inputs.conf file already.&lt;BR /&gt;
I've configured to accept connections over SSL and enabled those settings also within the inputs.conf file as well &lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;[http]
enableSSL = 1
#requireClientCert = false
#privKeyPath = /opt/splunk/etc/auth/splunk-certs/splunkforwarder.key
serverCert = /opt/splunk/etc/auth/splunk-certs/splunkforwarder.pem
#rootCA = /opt/splunk/etc/auth/splunk-certs/ca-chain.pem
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;Any help would be greatly appreciated!&lt;/P&gt;</description>
    <pubDate>Mon, 09 Dec 2019 21:26:48 GMT</pubDate>
    <dc:creator>mcirrici</dc:creator>
    <dc:date>2019-12-09T21:26:48Z</dc:date>
    <item>
      <title>Splunk Http Event Collector Socket Error</title>
      <link>https://community.splunk.com/t5/Security/Splunk-Http-Event-Collector-Socket-Error/m-p/502876#M11469</link>
      <description>&lt;P&gt;I've been trying for a few days now to setup a HEC on a Splunk Heavy Forwarder and having issues with the splunkd process binding to the default tcp/8088 port.&lt;/P&gt;

&lt;P&gt;I can see this error within the splunkd.log&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;FATAL HTTPServer - Could not bind to port 8088
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;However, I can verify that my localhost is listening on the port &lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;netstat -tulpn | grep 8088
tcp      129      0 0.0.0.0:8088            0.0.0.0:*               LISTEN      13924/splunkd
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;Also you can notice the queue filling up on that port &lt;/P&gt;

&lt;P&gt;I've configured the Splunk HEC global settings on the Splunk Web UI already and enabled the http input in the inputs.conf file already.&lt;BR /&gt;
I've configured to accept connections over SSL and enabled those settings also within the inputs.conf file as well &lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;[http]
enableSSL = 1
#requireClientCert = false
#privKeyPath = /opt/splunk/etc/auth/splunk-certs/splunkforwarder.key
serverCert = /opt/splunk/etc/auth/splunk-certs/splunkforwarder.pem
#rootCA = /opt/splunk/etc/auth/splunk-certs/ca-chain.pem
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;Any help would be greatly appreciated!&lt;/P&gt;</description>
      <pubDate>Mon, 09 Dec 2019 21:26:48 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Security/Splunk-Http-Event-Collector-Socket-Error/m-p/502876#M11469</guid>
      <dc:creator>mcirrici</dc:creator>
      <dc:date>2019-12-09T21:26:48Z</dc:date>
    </item>
    <item>
      <title>Re: Splunk Http Event Collector Socket Error</title>
      <link>https://community.splunk.com/t5/Security/Splunk-Http-Event-Collector-Socket-Error/m-p/502877#M11470</link>
      <description>&lt;P&gt;I'm like 90% sure it has to do with a SSL issue, I just can't seem to pinpoint where to look.&lt;/P&gt;</description>
      <pubDate>Tue, 10 Dec 2019 19:49:16 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Security/Splunk-Http-Event-Collector-Socket-Error/m-p/502877#M11470</guid>
      <dc:creator>mcirrici</dc:creator>
      <dc:date>2019-12-10T19:49:16Z</dc:date>
    </item>
  </channel>
</rss>

