-
Notifications
You must be signed in to change notification settings - Fork 68
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Elasticsearch Throws Certificate Error #25
Comments
@leshibily Did you ever find a solution? I am having the same problem. |
The issue was that self-signed certificate authority was replaced by the let's encrypt in the setup.sh script. I commented the replacing part (line 129-141) and re-run the steps mentioned in the official doc and everything worked like charm. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hello,
When I follow the Letsencrypt Walthrough document, elasticsearch throws the following error.
elasticsearch | {"type": "server", "timestamp": "2022-01-18T03:03:17,545Z", "level": "WARN", "component": "o.e.x.s.t.n.SecurityNetty4HttpServerTransport", "cluster.name": "elk-tls-cluster", "node.name": "elasticsearch", "message": "http client did not trust this server's certificate, closing connection Netty4HttpChannel{localAddress=/172.19.0.2:9200, remoteAddress=/172.19.0.5:51048}", "cluster.uuid": "DsG__rYzS4GNZ69miZs_Fg", "node.id": "l9xk4d7BSECjE9QYPfDOEg" }
Elasticsearch doesn't come up at all and hence when I access https://kibana.example.com, I see
Kibana server is not ready yet
.Logs from kibana container:
kibana | {"type":"log","@timestamp":"2022-01-18T03:02:57+00:00","tags":["error","savedobjects-service"],"pid":1220,"message":"Unable to retrieve version information from Elasticsearch nodes. unable to verify the first certificate"}
I am not sure why I need to run
docker-compose -f docker-compose.setup.yml run --rm certs
multiple times, that is confusing..env
docker version
docker-compose version
elk-tls-docker version - 1.3.0
I tried with both options
SUBDOMAIN
andSUBFOLDER
, only to end up in similar errors. Any help here would be appreciated.The text was updated successfully, but these errors were encountered: