# The client is unable to verify that the server is Elasticsearch due to an unsuccessful product check call
**URL:** https://discuss.elastic.co/t/the-client-is-unable-to-verify-that-the-server-is-elasticsearch-due-to-an-unsuccessful-product-check-call/348635
**Category:** Elasticsearch
**Tags:** language-clients
**Created:** [December 5, 2023, 11:58am UTC](https://discuss.elastic.co/t/the-client-is-unable-to-verify-that-the-server-is-elasticsearch-due-to-an-unsuccessful-product-check-call/348635 "2023-12-05T11:58:38Z")
**Posts on this page:** 9
**Page:** 1
### Author:  [@GRK](https://discuss.elastic.co/u/GRK)
#### Post date: [December 5, 2023, 11:58am UTC](https://discuss.elastic.co/t/the-client-is-unable-to-verify-that-the-server-is-elasticsearch-due-to-an-unsuccessful-product-check-call/348635/1 "2023-12-05T11:58:38Z")
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);
---
### Author:  [@Nigel\_Small](https://discuss.elastic.co/u/Nigel_Small)
#### Post date: [December 5, 2023, 12:03pm UTC](https://discuss.elastic.co/t/the-client-is-unable-to-verify-that-the-server-is-elasticsearch-due-to-an-unsuccessful-product-check-call/348635/2 "2023-12-05T12:03:33Z")
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.
---
### Author:  [@GRK](https://discuss.elastic.co/u/GRK)
#### Post date: [December 5, 2023, 12:11pm UTC](https://discuss.elastic.co/t/the-client-is-unable-to-verify-that-the-server-is-elasticsearch-due-to-an-unsuccessful-product-check-call/348635/3 "2023-12-05T12:11:21Z")
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
---
### Author:  [@GRK](https://discuss.elastic.co/u/GRK)
#### Post date: [December 5, 2023, 12:16pm UTC](https://discuss.elastic.co/t/the-client-is-unable-to-verify-that-the-server-is-elasticsearch-due-to-an-unsuccessful-product-check-call/348635/4 "2023-12-05T12:16:50Z")
The code worked fine until elasticsearch is connected with localhost, issue is with connecting other elasticsearch instance hosted elsewhere.
---
### Author:  [@Nigel\_Small](https://discuss.elastic.co/u/Nigel_Small)
#### Post date: [December 5, 2023, 12:19pm UTC](https://discuss.elastic.co/t/the-client-is-unable-to-verify-that-the-server-is-elasticsearch-due-to-an-unsuccessful-product-check-call/348635/5 "2023-12-05T12:19:15Z")
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?
---
### Author:  [@GRK](https://discuss.elastic.co/u/GRK)
#### Post date: [December 5, 2023, 12:22pm UTC](https://discuss.elastic.co/t/the-client-is-unable-to-verify-that-the-server-is-elasticsearch-due-to-an-unsuccessful-product-check-call/348635/6 "2023-12-05T12:22:36Z")
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:
- 299 Elasticsearch-7.17.5-8d61b4f7ddf931f219e3745f295ed2bbc50c8e84 "Elasticsearch built-in security features are not enabled. Without authentication, your cluster could be accessible to anyone. See [Set up minimal security for Elasticsearch | Elasticsearch Guide [7.17] | Elastic](https://www.elastic.co/guide/en/elasticsearch/reference/7.17/security-minimal-setup.html) to enable security."
---
### Author:  [@Nigel\_Small](https://discuss.elastic.co/u/Nigel_Small)
#### Post date: [December 5, 2023, 12:26pm UTC](https://discuss.elastic.co/t/the-client-is-unable-to-verify-that-the-server-is-elasticsearch-due-to-an-unsuccessful-product-check-call/348635/7 "2023-12-05T12:26:28Z")
So that indicates that the client and server can successfully communicate at least. We would generally recommend following the advice in that embedded [link](https://www.elastic.co/guide/en/elasticsearch/reference/7.17/security-minimal-setup.html) 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.
---
### Author:  [@GRK](https://discuss.elastic.co/u/GRK)
#### Post date: [December 5, 2023, 12:29pm UTC](https://discuss.elastic.co/t/the-client-is-unable-to-verify-that-the-server-is-elasticsearch-due-to-an-unsuccessful-product-check-call/348635/8 "2023-12-05T12:29:19Z")
Thanks for your Help, I will enable the security feautures and try again .
---
### Author:  [@system](https://discuss.elastic.co/u/system)
#### Post date: [January 2, 2024, 12:30pm UTC](https://discuss.elastic.co/t/the-client-is-unable-to-verify-that-the-server-is-elasticsearch-due-to-an-unsuccessful-product-check-call/348635/9 "2024-01-02T12:30:12Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.