https://community.splunk.com/t5/Monitoring-Splunk/Splunk-Enterprise-HTTPSConnectionPool-socket-error-Connection/m-p/474233#M8300 <P>Found solution...</P> <P>Run below two commands on newly created VM after Splunk installtion.</P> <P>sudo firewall-cmd --zone=public --add-port=8000/tcp --permanent<BR /> sudo firewall-cmd --reload</P> <P>After this I am able to open Splunk Web URL.</P> Tue, 07 Jan 2020 05:25:05 GMT kishor_pinjarka 2020-01-07T05:25:05Z https://community.splunk.com/t5/Monitoring-Splunk/Splunk-Enterprise-HTTPSConnectionPool-socket-error-Connection/m-p/474232#M8299 <P>1) Installed Splunk Enterprise on server 1:<BR /> VERSION=7.2.0<BR /> BUILD=8c86330ac18<BR /> PRODUCT=splunk<BR /> PLATFORM=Linux-x86_64</P> <P>2) Restarting splunkd: </P> <P>Stopping splunkd...<BR /> Shutting down. Please wait, as this may take a few minutes.<BR /> .. [ OK ]<BR /> Stopping splunk helpers...<BR /> [ OK ]<BR /> Done.</P> <P>Splunk&gt; Be an IT superhero. Go home early.</P> <P>Checking prerequisites...<BR /> Checking http port [8000]: open<BR /> Checking mgmt port [8089]: 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 _internal _introspection _telemetry _thefishbucket history main summary<BR /> Done<BR /> Checking filesystem compatibility... Done<BR /> Checking conf files for problems...<BR /> Done<BR /> Checking default conf files for edits...<BR /> Validating installed files against hashes from '/opt/splunk/splunk-7.2.0-8c86330ac18-linux-2.6-x86_64-manifest'<BR /> All installed files intact.<BR /> Done<BR /> All preliminary checks passed.</P> <P>Starting splunk server daemon (splunkd)...<BR /> Done<BR /> [ OK ]</P> <P>Waiting for web server at <A href="https://127.0.0.1:8000" target="_blank">https://127.0.0.1:8000</A> to be available.. Done</P> <P>If you get stuck, we're here to help.<BR /> Look for answers here: <A href="http://docs.splunk.com" target="_blank">http://docs.splunk.com</A></P> <P>The Splunk web interface is at ***:8000</P> <P>3) Port 8000 is already opened from server1 to server2.</P> <P>4) Trying to access Web URL from server 2: ***:8000<BR /> Not able to open Web URL.</P> <P>5) Checked splunkd logs:<BR /> 01-02-2020 03:01:30.767 -0800 ERROR ApplicationUpdater - Error checking for update, URL=<A href="https://apps.splunk.com/api/apps:resolve/checkforupgrade:" target="_blank">https://apps.splunk.com/api/apps:resolve/checkforupgrade:</A> Connect Timeout<BR /> 01-02-2020 03:03:48.066 -0800 ERROR ExecProcessor - message from "python /opt/splunk/etc/apps/splunk_instrumentation/bin/instrumentation.py" HTTPSConnectionPool(host='e1345286.api.splkmobile.com', port=443): Max retries exceeded with url: /1.0/e1345286/6b0c90ec-af87-5382-ae54-e94d7b316c04/1/0?hash=none (Caused by : [Errno 110] Connection timed out)</P> <P>What I have to do?</P> Wed, 30 Sep 2020 03:30:42 GMT https://community.splunk.com/t5/Monitoring-Splunk/Splunk-Enterprise-HTTPSConnectionPool-socket-error-Connection/m-p/474232#M8299 kishor_pinjarka 2020-09-30T03:30:42Z https://community.splunk.com/t5/Monitoring-Splunk/Splunk-Enterprise-HTTPSConnectionPool-socket-error-Connection/m-p/474233#M8300 <P>Found solution...</P> <P>Run below two commands on newly created VM after Splunk installtion.</P> <P>sudo firewall-cmd --zone=public --add-port=8000/tcp --permanent<BR /> sudo firewall-cmd --reload</P> <P>After this I am able to open Splunk Web URL.</P> Tue, 07 Jan 2020 05:25:05 GMT https://community.splunk.com/t5/Monitoring-Splunk/Splunk-Enterprise-HTTPSConnectionPool-socket-error-Connection/m-p/474233#M8300 kishor_pinjarka 2020-01-07T05:25:05Z