The client is unable to verify that the server is Elasticsearch due to an unsuccessful product check call

Elastic Stack Elasticsearch
1

Invalid NEST response built from a unsuccessful () low level call on HEAD: /indexname
Audit trail of this API call:

  • [1] ProductCheckOnStartup: Took:
  • [2] ProductCheckFailure: Node:

OriginalException: Elasticsearch.Net.ElasticsearchClientException: The client is unable to verify that the server is Elasticsearch due to an unsuccessful product check call. Some functionality may not be compatible if the server is running an unsupported product. Call: Status code unknown from: GET /

---> Elasticsearch.Net.PipelineException: The client is unable to verify that the server is Elasticsearch due to an unsuccessful product check call. Some functionality may not be compatible if the server is running an unsupported product.
---> System.Net.Http.HttpRequestException: The SSL connection could not be established, see inner exception.
---> System.IO.IOException: Cannot determine the frame size or a corrupted frame was received.
here is my settings
var settings = new ConnectionSettings(new Uri(elasticsearchServerUrl))
.DefaultIndex(indexName);
var client = new ElasticClient(settings);

2

Hi @GRK. Could you provide some more context about what code you are trying to run, and what your client and server infrastructure look like? We're generally not able to offer advice without more contextual information.

3

Hii Nigel_Small Thankyou for your quick response, I am using elasticsearch 7.17.5 and nest 7.17.5 versions and .net 5.0

4

The code worked fine until elasticsearch is connected with localhost, issue is with connecting other elasticsearch instance hosted elsewhere.

5

Are you attempting to connect via a secure connection? Can you check whether both your client and server agree on that? Are you making a secure connection to a plaintext port, for example?

6

I was using https and I changed it to http now the exception is Invalid NEST response built from a successful (404) low level call on HEAD: /distibutionsummarydaoes202011

Server indicated deprecations:

7

So that indicates that the client and server can successfully communicate at least. We would generally recommend following the advice in that embedded link to set up a secure authenticated service. Without that, you are likely to see warnings. Once that is set up, you should then be able to switch back to https.

8

Thanks for your Help, I will enable the security feautures and try again .

1 Like
9

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.