Versions (relevant - OpenSearch/Dashboard/Server OS/Browser):
opensearch-dashboards 2.11 or 2.17
Describe the issue:
We’re running an opensearch 2.11 cluster without TLS.
It’s at http://localhost:9200
I’ve apt installed the opensearch-dashboards-2.11 dpkg. on the same server.
node is running and listening on 5601
If I tunnel an ssh connection from my desktop to 5601 on the opensearch server I get the message:
OpenSearch Dashboards server is not ready yet
I can run all manner of curl to http://localhost:9200 with no issues.
Here’s a bit more information:
The opensearch cluster is set up with no ssl and no authentication.
opensearch_dashboards.yml has the following active lines:
opensearch.hosts: [https://localhost:9200]
opensearch.ssl.verificationMode: none
opensearch.username: kibanaserver
opensearch.password: kibanaserver
opensearch.requestHeadersWhitelist: [authorization, securitytenant]
opensearch_security.multitenancy.enabled: true
opensearch_security.multitenancy.tenants.preferred: [Private, Global]
opensearch_security.readonly_mode.roles: [kibana_read_only]
server.ssl.enabled: false
opensearch_security.cookie.secure: false
An strace of the node application shows this initial communication to the opensearch server. (FD 21 is the connection to the server)
write(21, “\26\3\1\1j\1\0\1f\3\3+$\3\242\373\224\20S\240\237\36\334F\365\314\215\237K\17rR”…, 367) = 367
read(21, “HTTP/1.0 400 Bad Request\r\nconten”…, 65536) = 299
This looks to me like the application is sending some kind of encrypted message to the server, which the server does not know how to handle.