-
Notifications
You must be signed in to change notification settings - Fork 886
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
Temporal can't connect to Elasticsearch with enabled TLS #4695
Comments
Hi all! Seems like the client library that you're using, doesn't have actual support for 8 version of Elasticsearch and not maintained anymore olivere/elastic#1533. |
Did you set up the certs correctly? Are they from a known issuer? |
I do requests to the Elasticsearch API from my host with the same credentials and everything works.
Yes, I used Let's Encrypt for certificate request |
Can you share your config? Does it look like this?
|
Unfortanly I destroyed a test environment with the setup. If it would help, I'll spin up the env later and give you debug info.
Yes, it is. |
I followed these steps to setup ES with certs and authentication, and it worked. In those instructions, it uses the ES tool to generate certs which are not from a known issuer, so I had to set a custom http client to Temporal Server that skip this check. Something like this:
|
I also confirm that works! Would be helpful to mention the ability to define a custom HTTP client for Elasticsearch in server-opritons on docs.temporal.io |
Expected Behavior
Temporal cluster establishes connection with Elasticsearch.
Actual Behavior
"no ElasticSearch node available"
Steps to Reproduce the Problem
scheme: "https"
in Temporal server configSpecifications
The text was updated successfully, but these errors were encountered: