https://community.splunk.com/t5/Splunk-Dev/After-accidentally-running-another-web-server-on-the-same-port/m-p/212053#M2811 <P>I accidentally ran another web server on the same port as the Splunk Web server (8000) and since then, I've been unable to start Splunk. The start process gets stuck at <CODE>"Waiting for webserver at <A href="http://127.0.0.1:8000&quot;" target="test_blank">http://127.0.0.1:8000"</A>;</CODE> and I am left unable to access the web UI.</P> <P>What I've tried:</P> <UL> <LI>I've stopped the other web server</LI> <LI>I've changed Splunk web and Splunkd to a variety of different ports, no difference</LI> <LI>I've checked my local firewall, there are no rules which could affect this</LI> <LI>I've tried with and without SSL</LI> <LI>I've restarted several times</LI> <LI>Splunk says the http port is open during startup</LI> <LI>There's nothing else on the ports I've tried</LI> </UL> <P>All I've done for this to happen is run something on the same port, but that should have stopped being an issue as soon as I stopped the other listener, or certainly after having changed Splunk to different ports.</P> Tue, 03 Nov 2015 11:53:43 GMT dwood023 2015-11-03T11:53:43Z https://community.splunk.com/t5/Splunk-Dev/After-accidentally-running-another-web-server-on-the-same-port/m-p/212053#M2811 <P>I accidentally ran another web server on the same port as the Splunk Web server (8000) and since then, I've been unable to start Splunk. The start process gets stuck at <CODE>"Waiting for webserver at <A href="http://127.0.0.1:8000&quot;" target="test_blank">http://127.0.0.1:8000"</A>;</CODE> and I am left unable to access the web UI.</P> <P>What I've tried:</P> <UL> <LI>I've stopped the other web server</LI> <LI>I've changed Splunk web and Splunkd to a variety of different ports, no difference</LI> <LI>I've checked my local firewall, there are no rules which could affect this</LI> <LI>I've tried with and without SSL</LI> <LI>I've restarted several times</LI> <LI>Splunk says the http port is open during startup</LI> <LI>There's nothing else on the ports I've tried</LI> </UL> <P>All I've done for this to happen is run something on the same port, but that should have stopped being an issue as soon as I stopped the other listener, or certainly after having changed Splunk to different ports.</P> Tue, 03 Nov 2015 11:53:43 GMT https://community.splunk.com/t5/Splunk-Dev/After-accidentally-running-another-web-server-on-the-same-port/m-p/212053#M2811 dwood023 2015-11-03T11:53:43Z https://community.splunk.com/t5/Splunk-Dev/After-accidentally-running-another-web-server-on-the-same-port/m-p/212054#M2812 <P>Fixed it, I checked web_service.log and found python syntax errors - I forgot I had previously changed my python env variables to a Python 3 installation, the webserver was trying to run Python 2 with that Python 3 interpreter and failed to start as a result.</P> Tue, 03 Nov 2015 12:14:03 GMT https://community.splunk.com/t5/Splunk-Dev/After-accidentally-running-another-web-server-on-the-same-port/m-p/212054#M2812 dwood023 2015-11-03T12:14:03Z