# New install can't access http port 9200 **URL:** \ **Category:** Elasticsearch\ **Created:** [May 17, 2017, 1:50pm UTC](https://discuss.elastic.co/t/new-install-cant-access-http-port-9200/86114 "2017-05-17T13:50:33Z")\ **Posts on this page:** 6\ **Page:** 1
**Author:** ![kevinp512](https://avatars.discourse-cdn.com/v4/letter/k/49beb7/32.png) [@kevinp512](https://discuss.elastic.co/u/kevinp512)\ **Post date:** [May 17, 2017, 1:50pm UTC](https://discuss.elastic.co/t/new-install-cant-access-http-port-9200/86114/1 "2017-05-17T13:50:33Z")
I am doing my first ever install of elastic search and I appear to have hit an issue right out of the gate. I can't seem to get to http://:9200 from a browser. I performed an rpm install of version 5.4 on my CentOS 7 vm and the only config change I have made so far is to set the network.host to my IP. It appears that ES is running based on: [root@supelk elasticsearch]# curl -XGET '10.2.22.169:9200/\_cat/health?v&pretty' epoch timestamp cluster status node.total node.data shards pri relo init unassign pending\_tasks max\_task\_wait\_time active\_shards\_percent 1495028823 08:47:03 elasticsearch green 1 1 0 0 0 0 0 0 - 100.0% [root@supelk elasticsearch]# and I believe the host is seeing traffic because when I try to connect from a browser, this is what see on a tcpdump: [root@supelk elasticsearch]# tcpdump -i ens160 tcp port 9200 tcpdump: verbose output suppressed, use -v or -vv for full protocol decode listening on ens160, link-type EN10MB (Ethernet), capture size 65535 bytes 08:48:57.528125 IP 10.2.19.16.50512 \> supelk.wap-wsp: Flags [SEW], seq 3052757200, win 65535, options [mss 1348,nop,wscale 5,nop,nop,TS val 1127708011 ecr 0,sackOK,eol], length 0 08:48:57.529082 IP 10.2.19.16.50513 \> supelk.wap-wsp: Flags [S], seq 1001362015, win 65535, options [mss 1348,nop,wscale 5,nop,nop,TS val 1127708011 ecr 0,sackOK,eol], length 0 Have I missed something obvious here? Any help would be greatly appreciated. ---
**Author:** ![bobby259](https://avatars.discourse-cdn.com/v4/letter/b/9de053/32.png) [@bobby259](https://discuss.elastic.co/u/bobby259)\ **Post date:** [May 17, 2017, 2:01pm UTC](https://discuss.elastic.co/t/new-install-cant-access-http-port-9200/86114/2 "2017-05-17T14:01:01Z")
I am installing 5.4 today and I see the same issue. Port 9200 is active when I set network.host: localhost But, when I set network.host: , I see curl: (7) Failed to connect to port 9200: Connection refused. Can someone explain what's going on here? I have installed 5.3 very recently but never faced this kind of issue. ---
**Author:** ![tim0xF](https://avatars.discourse-cdn.com/v4/letter/t/ce73a5/32.png) [@tim0xF](https://discuss.elastic.co/u/tim0xF)\ **Post date:** [May 17, 2017, 3:22pm UTC](https://discuss.elastic.co/t/new-install-cant-access-http-port-9200/86114/3 "2017-05-17T15:22:46Z")
Also running into this with ES 5.4 on Ubuntu 16.04. elasticsearch service is running, however netstat -l does not show 9200 listening ---
**Author:** ![bobby259](https://avatars.discourse-cdn.com/v4/letter/b/9de053/32.png) [@bobby259](https://discuss.elastic.co/u/bobby259)\ **Post date:** [May 17, 2017, 4:02pm UTC](https://discuss.elastic.co/t/new-install-cant-access-http-port-9200/86114/4 "2017-05-17T16:02:58Z")
Guys, Please let me know if you figure out a way out of this. @dadoonet could you please look into this issue? ---
**Author:** ![kevinp512](https://avatars.discourse-cdn.com/v4/letter/k/49beb7/32.png) [@kevinp512](https://discuss.elastic.co/u/kevinp512)\ **Post date:** [May 17, 2017, 4:42pm UTC](https://discuss.elastic.co/t/new-install-cant-access-http-port-9200/86114/5 "2017-05-17T16:42:06Z")
Turns out all I had to do to get out of this was turn off iptables firewall. iptables -F and now I can get the page. ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [June 14, 2017, 4:42pm UTC](https://discuss.elastic.co/t/new-install-cant-access-http-port-9200/86114/6 "2017-06-14T16:42:21Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.