Open chancecardona opened 3 years ago
Upon further research it was found that this bug occurred even when using only the Reqwest code above if elasticsearch-rs was a dependency. This is due to native-tls being imported by default with elasticsearch-rs, which causes the conflict. Setting default-features=false
for the elasticsearch crate fixes this problem. Still though, a more helpful error message would be appreciated.
Thanks for opening @chancecardona. Would need to investigate to see if there's a more informative error message that can be provided.
Describe the bug I'm not sure if this is a true bug or if I'm merely doing something wrong. When attempting to create a client using the transport builder with some certificate files, I continuously get the error
Cert(reqwest::Error { kind: Builder, source: "incompatible TLS identity type" })
. I've tested these certificates with the exact same server using reqwest directly, which works precisely as intended. If this isn't a bug, it would be very helpful to have some more documentation providing the differences between these two and how to use certificates with elasticsearch.To Reproduce Steps to reproduce the behavior: Using an elasticsearch server configured to use credentials and tls certificates, this code yields the error:
Expected behavior I would expect this to behave like Reqwest does when doing it manually, as such:
Environment (please complete the following information):