Bug Description
When trying to connect to an Elasticsearch instance from DBCode, the connection fails immediately with ProductNotSupportedError.
DBCode reports that the server is not Elasticsearch and does not support this unknown product, even though the target endpoint returns a valid Elasticsearch-style GET / response with version information and the standard "You Know, for Search" tagline.
Repro steps
- Open Cursor with DBCode installed.
- Create or use an existing Elasticsearch connection.
- Try to connect to the Elasticsearch server.
- See the connection failure with
ProductNotSupportedError.
Expected Behavior
DBCode should successfully connect to the Elasticsearch server, or at least provide a more specific error explaining why the server is considered unsupported.
Actual Behavior
The connection fails immediately with the following error:
ProductNotSupportedError: The client noticed that the server is not Elasticsearch and we do not support this unknown product.
At the same time, sending GET / to the same endpoint returns a valid Elasticsearch-style response like this:
{
"name": "es-cn-xxxxxx",
"cluster_name": "es-cn-xxxxxxxx",
"cluster_uuid": "xxxxxxxxxx",
"version": {
"number": "7.4.0",
"build_flavor": "default",
"build_type": "tar",
"build_hash": "xxxxxxxxxxxx",
"build_date": "2019-09-27T08:36:48.569419Z",
"build_snapshot": false,
"lucene_version": "8.2.0",
"minimum_wire_compatibility_version": "6.8.0",
"minimum_index_compatibility_version": "6.0.0-beta1"
},
"tagline": "You Know, for Search"
}
This makes it look like DBCode or the underlying Elasticsearch client may be rejecting the server based on product validation logic or missing/unexpected response headers.
Environment
DBCode version: 1.28.13
VS Code (or fork) version: Cursor 2.7.0-pre.31.patch.0 (Universal)
VS Code base version: 1.105.1
OS: macOS 15.3.0 (Darwin arm64 25.3.0)
Database: Elasticsearch 7.4.0
Connection: direct
Error Meesages (if applicable)
2026-03-08 00:46:24.051 [error] Connection: 'test-env' failed: ProductNotSupportedError: The client noticed that the server is not Elasticsearch and we do not support this unknown product.
at Am._request (/Users/staff/.cursor/extensions/dbcode.dbcode-1.28.13-universal/out/vendor/@elastic/elasticsearch.js:11:106909)
at process.processTicksAndRejections (node:internal/process/task_queues:105:5)
at async /Users/staff/.cursor/extensions/dbcode.dbcode-1.28.13-universal/out/vendor/@elastic/elasticsearch.js:11:110506
at async Am.request (/Users/staff/.cursor/extensions/dbcode.dbcode-1.28.13-universal/out/vendor/@elastic/elasticsearch.js:11:110383)
at async n.IFe [as info] (/Users/staff/.cursor/extensions/dbcode.dbcode-1.28.13-universal/out/vendor/@elastic/elasticsearch.js:160:267220)
at async sDe.getServerInfo (/Users/staff/.cursor/extensions/dbcode.dbcode-1.28.13-universal/out/extension/extension.js:1:5853034)
at async sDe.connect (/Users/staff/.cursor/extensions/dbcode.dbcode-1.28.13-universal/out/extension/extension.js:1:5840702)
at async pn (/Users/staff/.cursor/extensions/dbcode.dbcode-1.28.13-universal/out/extension/extension.js:1:12858422)
at async Timeout._onTimeout (/Users/staff/.cursor/extensions/dbcode.dbcode-1.28.13-universal/out/extension/extension.js:1:12955090)
2026-03-08 00:46:31.540 [info] API 'POST:jwt' OK
Bug Description
When trying to connect to an Elasticsearch instance from DBCode, the connection fails immediately with
ProductNotSupportedError.DBCode reports that the server is not Elasticsearch and does not support this unknown product, even though the target endpoint returns a valid Elasticsearch-style
GET /response with version information and the standard"You Know, for Search"tagline.Repro steps
ProductNotSupportedError.Expected Behavior
DBCode should successfully connect to the Elasticsearch server, or at least provide a more specific error explaining why the server is considered unsupported.
Actual Behavior
The connection fails immediately with the following error:
ProductNotSupportedError: The client noticed that the server is not Elasticsearch and we do not support this unknown product.At the same time, sending
GET /to the same endpoint returns a valid Elasticsearch-style response like this:{ "name": "es-cn-xxxxxx", "cluster_name": "es-cn-xxxxxxxx", "cluster_uuid": "xxxxxxxxxx", "version": { "number": "7.4.0", "build_flavor": "default", "build_type": "tar", "build_hash": "xxxxxxxxxxxx", "build_date": "2019-09-27T08:36:48.569419Z", "build_snapshot": false, "lucene_version": "8.2.0", "minimum_wire_compatibility_version": "6.8.0", "minimum_index_compatibility_version": "6.0.0-beta1" }, "tagline": "You Know, for Search" }This makes it look like DBCode or the underlying Elasticsearch client may be rejecting the server based on product validation logic or missing/unexpected response headers.
Environment
DBCode version: 1.28.13
VS Code (or fork) version: Cursor 2.7.0-pre.31.patch.0 (Universal)
VS Code base version: 1.105.1
OS: macOS 15.3.0 (Darwin arm64 25.3.0)
Database: Elasticsearch 7.4.0
Connection: direct
Error Meesages (if applicable)