Access Elasticsearch 2.2 outside not work on iPad/iPhone


I installed Elasticsearch 2.2 on VPS Debian.
I configured to in elasticsearch.yml file.
I created a web site where I connect to elasticsearch to get data.
It works on Desktop but I received this error Can't connect to server on iPad or iPhone.
I don't understand why it works on Desktop and not on mobile devices.
If someone can help me ?

Best regards,


Can you access any other web service on the VPS from the iPad / iPhone? Is it only Elasticsearch?

The weird thing is it works on my personal iPhone but not on my other devices like my iPad Mini.
In my elasticsearch.yml, I have this
index.number_of_replicas: 0
http.cors.enabled : true
http.cors.allow-origin : "*"
http.cors.allow-methods : OPTIONS, HEAD, GET, POST, PUT, DELETE
http.cors.allow-headers : X-Requested-With,X-Auth-Token,Content-Type, Content-Length
http.jsonp.enable: true
index.mapper.dynamic: false

I think I don't use any other web service yet on my VPS.

But before I upgrade my elasticsearch, I added only two IPs to access my cluster, my personal desktop IP on particular wifi and my personal iPhone IP on particular Wifi.
My upgrade failed and I removed manually Elasticsearch to reinstall the last one.
Maybe I didn't clean well elasticsearch and it always use my old configuration ? (However, my brother can access to the cluster on his personal desktop.)

Where did you add this two IPs?

In my old elasticsearch.yml (before I install the new elasticsearch 2.2) in the network.bind_host parameter

But now I haven't it in the new configuration file under /etc/elasticsearch/elasticsearch.yml

Seems to be not related to an ES configuration issue then. Maybe just start a webserver on the VPS and check if you can connect to it with the iPad.

But I can access and see my angular website content so I can access to the vps no ?
Web console just said "Failed to load resource: Could not connect to the server.
" when I execute a search on my elasticsearch cluster.

You don't happen to have old rules set in the firewall (iptables) for the VPS?

iptables --list will list current firewall rules

I would suggest you control access through a reverse proxy such as Nginx or using the firewall instead of dealing with this in the Elasticsearch configuration directly. That kind of general access rules is better to control on server/OS level instead of in particular applications since you will have more options available and more control.