kibana-own-home icon indicating copy to clipboard operation
kibana-own-home copied to clipboard

Bad Gateway - unable to get issuer certificate

Open apathare23 opened this issue 6 years ago • 1 comments

Hi,

I have configured Own Home with ElasticSearch and Kibana on same system for testing and its working fine.

However I am facing issues when I tried to configure with AWS ElasticSearch and Kibana on EC2 instance.

I am getting following error in Kibana.log: "tags":["status","plugin:[email protected]","error"],"pid":xxxx,"state":"red","message":"Status changed from red to red - Bad Gateway","prevState":"red","prevMsg":"Unable to connect to Elasticsearch at https://localhost:19200."}

CURL test output: curl -s -k https://127.0.0.1:19200 {"statusCode":502,"error":"Bad Gateway","message":"unable to get issuer certificate"}

Kibana UI: ui settings - Elasticsearch plugin is red plugin:[email protected] - Bad Gateway plugin:[email protected] - Ready

Kibana.yml

server.port: 5601 server.host: "localhost" elasticsearch.url: https://localhost:19200 server.ssl.enabled: true server.ssl.certificate: /crt/localhost.cert.pem server.ssl.key: /crt/localhost.key.pem elasticsearch.ssl.verificationMode: none #elasticsearch.ssl.certificateAuthorities: elasticsearch.requestHeadersWhitelist: [ x-proxy-user, cookie ] own_home.proxy_user_header: x-proxy-user own_home.ssl.certificate: /crt/localhost.cert.pem
own_home.ssl.key: /crt/localhost.key.pem own_home.elasticsearch.url: https://search-xxxxxxx.us-east-1.es.amazonaws.com:443 own_home.elasticsearch.ssl.certificateAuthorities: /crt/amazones.pem own_home.session.secretkey: the-password-must-be-at-least-32-characters-long own_home.local.groups: [ public, sandbox ]

[AWS ES + Kibana on EC2 is working without Own Home plugin]

apathare23 avatar Jun 11 '18 20:06 apathare23

Could you check this article? And check your elasticsearch.ssl.certificateAuthorities and own_home.elasticsearch.ssl.certificateAuthorities options.

wtakase avatar Jul 05 '18 03:07 wtakase