We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
My ES 7.0.1 clusters each use a self-signed TLS cert to serve client requests.
$ curl -ks https://localhost:9202/_cluster/health?pretty { "cluster_name" : "transcriptions-cluster1", "status" : "green", "timed_out" : false, "number_of_nodes" : 5, "number_of_data_nodes" : 5, "active_primary_shards" : 100, "active_shards" : 200, "relocating_shards" : 0, "initializing_shards" : 0, "unassigned_shards" : 0, "delayed_unassigned_shards" : 0, "number_of_pending_tasks" : 0, "number_of_in_flight_fetch" : 0, "task_max_waiting_in_queue_millis" : 0, "active_shards_percent_as_number" : 100.0 }
I am unable to connect to these clusters using the head plugin.
Can I get the head module tolerate "Insecure"/aka self-signed server certificates?
The text was updated successfully, but these errors were encountered:
i would like to to know this too, does anyone found a solution?
Sorry, something went wrong.
No branches or pull requests
My ES 7.0.1 clusters each use a self-signed TLS cert to serve client requests.
I am unable to connect to these clusters using the head plugin.
Can I get the head module tolerate "Insecure"/aka self-signed server certificates?
The text was updated successfully, but these errors were encountered: