unable to connect with shield enabled

[etfeet]

When I try to connect with shield enabled the cluster health shows not connected. However, If i go to info it shows that it can connect to the cluster. Clicking status, node stats, and cluster nodes does nothing.

elasticsearch.yml: http.cors.allow-origin: "/.*/" http.cors.enabled: true http.cors.allow-credentials: true shield.ssl.keystore.path: /usr/share/elasticsearch/es.jks shield.ssl.keystore.password: XXX shield.ssl.keystore.key_password: XXX

turning ssl on or off doesn't change the behavior.

I've tried connecting using http://user:pass@nodename:9200 in the head address bar However, that doesn't work either.

I'm running elasticsearch 1.5.2 on centos 7.1.1503 from the elastic yum repo.

[hgfischer]

It's the same with a common HTTP proxy asking for HTTP AUTH.

[ptahchiev]

Same here.

[qiao-meng-zefr]

Same here. Using elasticsearch 2.4.0, kibana 2.4.0 and shield 2.4.0

[philipskokoh]

Have you tried this: https://github.com/mobz/elasticsearch-head#url-parameters

your elasticsearch.yml needs to be changed. * for http.cors.allow-origin is not allowed for credentialed requests.

[nan008]

I have the same problem connecting to ES 5.2 with elasticsearch-readonlyrest-plugin 1.14.0, my elasticsearch-head is webserver/filesystem. I need to provide a cert with the request. something similar I have with Logstash

ssl => true cacert => ["/etc/logstash/Logstash_cert.pem"]

Even when I will go with the basic authorization like @philipskokoh suggested. i am getting this response in ES log

[2017-03-15T12:34:01,231][ERROR][o.e.p.r.SSLTransportNetty4] [4DfeseL] exception in SSL transport: javax.net.ssl.SSLException: Received fatal alert: unknown_ca

Any suggestions where can indicate in elasticsearch-head that I am sending a cert?

[pallenod]

Was this ever resolved ? @nan008