Re: Accessing Port 9200 Remotely

2015-01-26 Thread James Carr 
You should bind to 0.0.0.0 not localhost. Then you can hit it remotely.

You can also use a reverse-proxy. It is what we do :-)

On Mon, Jan 26, 2015 at 6:16 PM, Dave Mittner 
wrote:

> I'm binding to "localhost"; nothing else seems to work. I get "Failed to
> bind" errors in the log if I try using the actual hostname.
>
> On Monday, January 26, 2015 at 5:04:34 PM UTC-7, James Carr wrote:
>>
>> * make sure you haven't bound to 127.0.0.1
>> * make sure relevant security groups have been opened.
>>
>> On Mon, Jan 26, 2015 at 5:58 PM, Mark Walkom  wrote:
>>
>>> You don't need the plugin, it can make discovery easier though.
>>>
>>> You haven't bound ES to localhost only have you?
>>>
>>> On 27 January 2015 at 09:42, Dave Mittner  wrote:
>>>
 I'm at a bit of a loss here...

 I have a pretty standard setup of elasticsearch and I'm able to
 curl/telnet to port 9200 locally, but the connection is refused if accessed
 from another server. I'm likewise unable to connect to port 9300. For
 Kibana3 I've also added:

 http.cors.allow-origin: "*"
 http.cors.enabled: true

 Our servers are on Amazon EC2 but we really don't need all the
 automated discovery stuff within the EC2 plugin. The ports are open through
 the security group and there's nothing in IP tables or any other firewalls.
 I also get slightly different behavior once the ports were open so it feels
 like the connection is being refused by the server or elasticsearch, 
 itself.

 Any pointers?
 Is the EC2 plugin a requirement in this case?

 Thanks

 --
 You received this message because you are subscribed to the Google
 Groups "elasticsearch" group.
 To unsubscribe from this group and stop receiving emails from it, send
 an email to elasticsearc...@googlegroups.com.
 To view this discussion on the web visit https://groups.google.com/d/
 msgid/elasticsearch/f8ecd552-336a-408b-9068-6d087d4c48e0%
 40googlegroups.com
 
 .
 For more options, visit https://groups.google.com/d/optout.

>>>
>>>  --
>>> You received this message because you are subscribed to the Google
>>> Groups "elasticsearch" group.
>>> To unsubscribe from this group and stop receiving emails from it, send
>>> an email to elasticsearc...@googlegroups.com.
>>> To view this discussion on the web visit https://groups.google.com/d/
>>> msgid/elasticsearch/CAEYi1X84jXq9GK3AfYjxBNLsoJDJk
>>> sAUZSr-PvNaH%2BBZDkn3gg%40mail.gmail.com
>>> 
>>> .
>>>
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>>
>>  --
> You received this message because you are subscribed to the Google Groups
> "elasticsearch" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to elasticsearch+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/elasticsearch/b05ca44e-a4ad-482c-9f4c-53f845303d9f%40googlegroups.com
> 
> .
>
> For more options, visit https://groups.google.com/d/optout.
>

-- 
You received this message because you are subscribed to the Google Groups 
"elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to elasticsearch+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/elasticsearch/CAJreXKCPhwY7OYpKnOo6ORe5BucnyGMCyDWFgcQHxwB%2BxAig1w%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Accessing Port 9200 Remotely

2015-01-26 Thread Dave Mittner 
I'm binding to "localhost"; nothing else seems to work. I get "Failed to 
bind" errors in the log if I try using the actual hostname.

On Monday, January 26, 2015 at 5:04:34 PM UTC-7, James Carr wrote:
>
> * make sure you haven't bound to 127.0.0.1
> * make sure relevant security groups have been opened. 
>
> On Mon, Jan 26, 2015 at 5:58 PM, Mark Walkom  > wrote:
>
>> You don't need the plugin, it can make discovery easier though.
>>
>> You haven't bound ES to localhost only have you?
>>
>> On 27 January 2015 at 09:42, Dave Mittner > > wrote:
>>
>>> I'm at a bit of a loss here...
>>>
>>> I have a pretty standard setup of elasticsearch and I'm able to 
>>> curl/telnet to port 9200 locally, but the connection is refused if accessed 
>>> from another server. I'm likewise unable to connect to port 9300. For 
>>> Kibana3 I've also added:
>>>
>>> http.cors.allow-origin: "*"
>>> http.cors.enabled: true
>>>
>>> Our servers are on Amazon EC2 but we really don't need all the automated 
>>> discovery stuff within the EC2 plugin. The ports are open through the 
>>> security group and there's nothing in IP tables or any other firewalls. I 
>>> also get slightly different behavior once the ports were open so it feels 
>>> like the connection is being refused by the server or elasticsearch, itself.
>>>
>>> Any pointers?
>>> Is the EC2 plugin a requirement in this case?
>>>
>>> Thanks
>>>
>>> -- 
>>> You received this message because you are subscribed to the Google 
>>> Groups "elasticsearch" group.
>>> To unsubscribe from this group and stop receiving emails from it, send 
>>> an email to elasticsearc...@googlegroups.com .
>>> To view this discussion on the web visit 
>>> https://groups.google.com/d/msgid/elasticsearch/f8ecd552-336a-408b-9068-6d087d4c48e0%40googlegroups.com
>>>  
>>> 
>>> .
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>>
>>  -- 
>> You received this message because you are subscribed to the Google Groups 
>> "elasticsearch" group.
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to elasticsearc...@googlegroups.com .
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/elasticsearch/CAEYi1X84jXq9GK3AfYjxBNLsoJDJksAUZSr-PvNaH%2BBZDkn3gg%40mail.gmail.com
>>  
>> 
>> .
>>
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to elasticsearch+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/elasticsearch/b05ca44e-a4ad-482c-9f4c-53f845303d9f%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Accessing Port 9200 Remotely

2015-01-26 Thread James Carr 
* make sure you haven't bound to 127.0.0.1
* make sure relevant security groups have been opened.

On Mon, Jan 26, 2015 at 5:58 PM, Mark Walkom  wrote:

> You don't need the plugin, it can make discovery easier though.
>
> You haven't bound ES to localhost only have you?
>
> On 27 January 2015 at 09:42, Dave Mittner  wrote:
>
>> I'm at a bit of a loss here...
>>
>> I have a pretty standard setup of elasticsearch and I'm able to
>> curl/telnet to port 9200 locally, but the connection is refused if accessed
>> from another server. I'm likewise unable to connect to port 9300. For
>> Kibana3 I've also added:
>>
>> http.cors.allow-origin: "*"
>> http.cors.enabled: true
>>
>> Our servers are on Amazon EC2 but we really don't need all the automated
>> discovery stuff within the EC2 plugin. The ports are open through the
>> security group and there's nothing in IP tables or any other firewalls. I
>> also get slightly different behavior once the ports were open so it feels
>> like the connection is being refused by the server or elasticsearch, itself.
>>
>> Any pointers?
>> Is the EC2 plugin a requirement in this case?
>>
>> Thanks
>>
>> --
>> You received this message because you are subscribed to the Google Groups
>> "elasticsearch" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to elasticsearch+unsubscr...@googlegroups.com.
>> To view this discussion on the web visit
>> https://groups.google.com/d/msgid/elasticsearch/f8ecd552-336a-408b-9068-6d087d4c48e0%40googlegroups.com
>> 
>> .
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>  --
> You received this message because you are subscribed to the Google Groups
> "elasticsearch" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to elasticsearch+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/elasticsearch/CAEYi1X84jXq9GK3AfYjxBNLsoJDJksAUZSr-PvNaH%2BBZDkn3gg%40mail.gmail.com
> 
> .
>
> For more options, visit https://groups.google.com/d/optout.
>

-- 
You received this message because you are subscribed to the Google Groups 
"elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to elasticsearch+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/elasticsearch/CAJreXKDEaW6AbAHFo4YPn2gVHhK1AEa_rS-BdtvPdCh_eXkGnw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Accessing Port 9200 Remotely

2015-01-26 Thread Mark Walkom 
You don't need the plugin, it can make discovery easier though.

You haven't bound ES to localhost only have you?

On 27 January 2015 at 09:42, Dave Mittner  wrote:

> I'm at a bit of a loss here...
>
> I have a pretty standard setup of elasticsearch and I'm able to
> curl/telnet to port 9200 locally, but the connection is refused if accessed
> from another server. I'm likewise unable to connect to port 9300. For
> Kibana3 I've also added:
>
> http.cors.allow-origin: "*"
> http.cors.enabled: true
>
> Our servers are on Amazon EC2 but we really don't need all the automated
> discovery stuff within the EC2 plugin. The ports are open through the
> security group and there's nothing in IP tables or any other firewalls. I
> also get slightly different behavior once the ports were open so it feels
> like the connection is being refused by the server or elasticsearch, itself.
>
> Any pointers?
> Is the EC2 plugin a requirement in this case?
>
> Thanks
>
> --
> You received this message because you are subscribed to the Google Groups
> "elasticsearch" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to elasticsearch+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/elasticsearch/f8ecd552-336a-408b-9068-6d087d4c48e0%40googlegroups.com
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>

-- 
You received this message because you are subscribed to the Google Groups 
"elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to elasticsearch+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/elasticsearch/CAEYi1X84jXq9GK3AfYjxBNLsoJDJksAUZSr-PvNaH%2BBZDkn3gg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Accessing Port 9200 Remotely

2015-01-26 Thread Dave Mittner 
I'm at a bit of a loss here...

I have a pretty standard setup of elasticsearch and I'm able to curl/telnet 
to port 9200 locally, but the connection is refused if accessed from 
another server. I'm likewise unable to connect to port 9300. For Kibana3 
I've also added:

http.cors.allow-origin: "*"
http.cors.enabled: true

Our servers are on Amazon EC2 but we really don't need all the automated 
discovery stuff within the EC2 plugin. The ports are open through the 
security group and there's nothing in IP tables or any other firewalls. I 
also get slightly different behavior once the ports were open so it feels 
like the connection is being refused by the server or elasticsearch, itself.

Any pointers?
Is the EC2 plugin a requirement in this case?

Thanks

-- 
You received this message because you are subscribed to the Google Groups 
"elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to elasticsearch+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/elasticsearch/f8ecd552-336a-408b-9068-6d087d4c48e0%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.