# Elastiseach not avalable in port 9200

**URL:** <https://discuss.elastic.co/t/elastiseach-not-avalable-in-port-9200/29873>\
**Category:** Elasticsearch\
**Created:** [September 23, 2015, 9:22pm UTC](https://discuss.elastic.co/t/elastiseach-not-avalable-in-port-9200/29873 "2015-09-23T21:22:01Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![Arunv](https://avatars.discourse-cdn.com/v4/letter/a/3be4f8/32.png) [@Arunv](https://discuss.elastic.co/u/Arunv)\
**Post date:** [September 23, 2015, 9:22pm UTC](https://discuss.elastic.co/t/elastiseach-not-avalable-in-port-9200/29873/1 "2015-09-23T21:22:01Z")

</div>

Installed elasticsearch-1.4.4 in linux and I see the process running. But I when I try to access [http://localhost:9200](http://localhost:9200), I am getting "Page note available". Does this mean elastisearch is listening on some other port? I did not change any default settings.

In the logs I am getting this exception:  
[2015-09-23 16:06:33,437][WARN][transport.netty] [Sage] exception caught on transport layer [[id: 0x2e727dc4, /10.221.22.14:8995 =\> /10.210.12.104:9300]], closing connection  
java.io.StreamCorruptedException: invalid internal transport message format, got (47,45,54,20)  
at org.elasticsearch.transport.netty.SizeHeaderFrameDecoder.decode(SizeHeaderFrameDecoder.java:47)  
at org.elasticsearch.common.netty.handler.codec.frame.FrameDecoder.callDecode(FrameDecoder.java:425)  
at org.elasticsearch.common.netty.handler.codec.frame.FrameDecoder.messageReceived(FrameDecoder.java:303)  
at org.elasticsearch.common.netty.channel.SimpleChannelUpstreamHandler.handleUpstream(SimpleChannelUpstreamHandler.java:70)  
at org.elasticsearch.common.netty.channel.DefaultChannelPipeline.sendUpstream(DefaultChannelPipeline.java:564)  
at org.elasticsearch.common.netty.channel.DefaultChannelPipeline$DefaultChannelHandlerContext.sendUpstream(DefaultChannelPipeline.java:791)  
at org.elasticsearch.common.netty.OpenChannelsHandler.handleUpstream(OpenChannelsHandler.java:74)  
at org.elasticsearch.common.netty.channel.DefaultChannelPipeline.sendUpstream(DefaultChannelPipeline.java:564)  
at org.elasticsearch.common.netty.channel.DefaultChannelPipeline.sendUpstream(DefaultChannelPipeline.java:559)  
at org.elasticsearch.common.netty.channel.Channels.fireMessageReceived(Channels.java:268)  
at org.elasticsearch.common.netty.channel.Channels.fireMessageReceived(Channels.java:255)  
at org.elasticsearch.common.netty.channel.socket.nio.NioWorker.read(NioWorker.java:88)  
at org.elasticsearch.common.netty.channel.socket.nio.AbstractNioWorker.process(AbstractNioWorker.java:108)  
at org.elasticsearch.common.netty.channel.socket.nio.AbstractNioSelector.run(AbstractNioSelector.java:318)  
at org.elasticsearch.common.netty.channel.socket.nio.AbstractNioWorker.run(AbstractNioWorker.java:89)  
at org.elasticsearch.common.netty.channel.socket.nio.NioWorker.run(NioWorker.java:178)  
at org.elasticsearch.common.netty.util.ThreadRenamingRunnable.run(ThreadRenamingRunnable.java:108)  
at org.elasticsearch.common.netty.util.internal.DeadLockProofWorker$1.run(DeadLockProofWorker.java:42)  
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)  
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)  
at java.lang.Thread.run(Thread.java:745)  
[2015-09-23 16:06:33,443][WARN][transport.netty] [Sage] exception caught on transport layer [[id: 0x2e727dc4, /10.221.22.14:8995 :\> /10.210.12.104:9300]], closing connection  
java.io.StreamCorruptedException: invalid internal transport message format, got (47,45,54,20)

---

<div class="post-metadata">

**Author:** ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)\
**Post date:** [September 23, 2015, 9:48pm UTC](https://discuss.elastic.co/t/elastiseach-not-avalable-in-port-9200/29873/2 "2015-09-23T21:48:38Z")

</div>

That error usually means you are trying to send a HTTP request to port 9300.

However check your logs, it should mention on startup what port it binds to.

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [July 5, 2017, 11:48pm UTC](https://discuss.elastic.co/t/elastiseach-not-avalable-in-port-9200/29873/3 "2017-07-05T23:48:25Z")

</div>