https://community.splunk.com/t5/Splunk-Enterprise/splunk-always-starts-at-127-0-0-1-8000/m-p/187969#M9172 <P>thank you<BR /> i cant telnet in either port,<BR /><BR /> i changed web port and splunkd port to 80 89, still get this:</P> <P>Checking prerequisites...<BR /> Checking http port [80]: open<BR /> Checking mgmt port [89]: open<BR /> Checking appserver port [127.0.0.1:8065]: open<BR /> Checking kvstore port [8191]: open<BR /> Checking configuration... Done.<BR /> Checking critical directories... Done<BR /> Checking indexes...<BR /> Validated: _audit _blocksignature _internal _introspection _thefishbucket history main summary<BR /> Done<BR /> Checking filesystem compatibility... Done<BR /> Checking conf files for problems...<BR /> Done<BR /> All preliminary checks passed.</P> <P>Starting splunk server daemon (splunkd)...<BR /><BR /> Done<BR /> [ OK ]</P> <P>Waiting for web server at <A href="http://127.0.0.1:80">http://127.0.0.1:80</A> to be available... Done </P> <P>........telnet ip-addr:22 successful</P> Thu, 30 Oct 2014 03:45:54 GMT crazyeva 2014-10-30T03:45:54Z https://community.splunk.com/t5/Splunk-Enterprise/splunk-always-starts-at-127-0-0-1-8000/m-p/187965#M9168 <P>I have a problem<BR /> Splunk always start at <A href="http://127.0.0.1:8000">http://127.0.0.1:8000</A> and ignor the interface IP address<BR /> it is newly installed in a virtual machine, RHEL 7, IP is set as 192.168.100.1<BR /> i access the machine with SSH, i mean the interface is alive, can be access to remotely<BR /> but it seems SPLUNK can not recognise it</P> Wed, 29 Oct 2014 02:46:06 GMT https://community.splunk.com/t5/Splunk-Enterprise/splunk-always-starts-at-127-0-0-1-8000/m-p/187965#M9168 crazyeva 2014-10-29T02:46:06Z https://community.splunk.com/t5/Splunk-Enterprise/splunk-always-starts-at-127-0-0-1-8000/m-p/187966#M9169 <P>check if you can telnet in port 8000 and 8089 from remote machine if not then these ports are blocked/not accessible.un-block them</P> Wed, 29 Oct 2014 08:05:14 GMT https://community.splunk.com/t5/Splunk-Enterprise/splunk-always-starts-at-127-0-0-1-8000/m-p/187966#M9169 kml_uvce 2014-10-29T08:05:14Z https://community.splunk.com/t5/Splunk-Enterprise/splunk-always-starts-at-127-0-0-1-8000/m-p/187967#M9170 <P>you can use the SPLUNK_BINDIP to start splunkd on a specific port<BR /> export SPLUNK_BINDIP=your-ip-addr<BR /> do a splunk start <BR /> you should see the splunk services binding to only the above IP<BR /> to make it permanent put this in etc/splunk-launch.conf</P> Mon, 28 Sep 2020 17:58:05 GMT https://community.splunk.com/t5/Splunk-Enterprise/splunk-always-starts-at-127-0-0-1-8000/m-p/187967#M9170 ithangasamy_spl 2020-09-28T17:58:05Z https://community.splunk.com/t5/Splunk-Enterprise/splunk-always-starts-at-127-0-0-1-8000/m-p/187968#M9171 <P>thank you for helping<BR /> Splunk does start with the ip SPLUNK_BINDIP specified, but i still cant not access to splunk web through ip-addr:8000<BR /> after started, ip-addr:8089 ip-addr:8000 are listening, but can not telnet in from outside.</P> Thu, 30 Oct 2014 03:34:55 GMT https://community.splunk.com/t5/Splunk-Enterprise/splunk-always-starts-at-127-0-0-1-8000/m-p/187968#M9171 crazyeva 2014-10-30T03:34:55Z https://community.splunk.com/t5/Splunk-Enterprise/splunk-always-starts-at-127-0-0-1-8000/m-p/187969#M9172 <P>thank you<BR /> i cant telnet in either port,<BR /><BR /> i changed web port and splunkd port to 80 89, still get this:</P> <P>Checking prerequisites...<BR /> Checking http port [80]: open<BR /> Checking mgmt port [89]: open<BR /> Checking appserver port [127.0.0.1:8065]: open<BR /> Checking kvstore port [8191]: open<BR /> Checking configuration... Done.<BR /> Checking critical directories... Done<BR /> Checking indexes...<BR /> Validated: _audit _blocksignature _internal _introspection _thefishbucket history main summary<BR /> Done<BR /> Checking filesystem compatibility... Done<BR /> Checking conf files for problems...<BR /> Done<BR /> All preliminary checks passed.</P> <P>Starting splunk server daemon (splunkd)...<BR /><BR /> Done<BR /> [ OK ]</P> <P>Waiting for web server at <A href="http://127.0.0.1:80">http://127.0.0.1:80</A> to be available... Done </P> <P>........telnet ip-addr:22 successful</P> Thu, 30 Oct 2014 03:45:54 GMT https://community.splunk.com/t5/Splunk-Enterprise/splunk-always-starts-at-127-0-0-1-8000/m-p/187969#M9172 crazyeva 2014-10-30T03:45:54Z https://community.splunk.com/t5/Splunk-Enterprise/splunk-always-starts-at-127-0-0-1-8000/m-p/187970#M9173 <P>thank you very much<BR /> that is my fault: firewall !<BR /> RHEL 7, "iptables off" is not effictive...<BR /> "systemctl disable firewalld" to shutdown firewall <BR /> By the way, splunk 6.2 does not support IE 11 !</P> Thu, 30 Oct 2014 04:20:43 GMT https://community.splunk.com/t5/Splunk-Enterprise/splunk-always-starts-at-127-0-0-1-8000/m-p/187970#M9173 crazyeva 2014-10-30T04:20:43Z https://community.splunk.com/t5/Splunk-Enterprise/splunk-always-starts-at-127-0-0-1-8000/m-p/187971#M9174 <P>Was there a solution for this at the end ? I'm having the same issue.. Splunk is only binding to locahost </P> Thu, 06 Jul 2017 19:52:57 GMT https://community.splunk.com/t5/Splunk-Enterprise/splunk-always-starts-at-127-0-0-1-8000/m-p/187971#M9174 stuxnet23 2017-07-06T19:52:57Z https://community.splunk.com/t5/Splunk-Enterprise/splunk-always-starts-at-127-0-0-1-8000/m-p/187972#M9175 <P>I found the issue.. It was with permissions.. I kept executing the restart command under root <BR /> As soon as I changed user it worked </P> Thu, 06 Jul 2017 20:14:09 GMT https://community.splunk.com/t5/Splunk-Enterprise/splunk-always-starts-at-127-0-0-1-8000/m-p/187972#M9175 stuxnet23 2017-07-06T20:14:09Z