You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Warning: C:\users\xxx.curlrc:2: warning: 'compressed' the
Warning: installed libcurl version doesn't support this
{"cluster_name":"elk1-cluster","status":"green","timed_out":false,"number_of_nodes":3,"number_of_data_nodes":3,"active_primary_shards":13,"active_shards":26,"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}
The text was updated successfully, but these errors were encountered:
Hi, I'm trying to get basic GET request working but no matter what, I seem to get
Running: es-execute-request-dwim (C-c C-c)
Issuing GET against https://elastic:password@localhost:9200/_cluster/health
REQUEST [error] Error (error) while connecting to https://elastic:password@localhost:9200/_cluster/health.
Response: Status: nil Content-Type: nil (nil bytes)
(note: password above is naturally the real password).
For installation of the ELK stack I've followed the guide here:
https://www.elastic.co/guide/en/elasticsearch/reference/current/docker.html
Possibly worth mentioning is that I run emacs under windows, and I can get the JSON as successful response from 'curl' on the cmd.exe line:
curl https://elastic:password@localhost:9200/_cluster/health
Warning: C:\users\xxx.curlrc:2: warning: 'compressed' the
Warning: installed libcurl version doesn't support this
{"cluster_name":"elk1-cluster","status":"green","timed_out":false,"number_of_nodes":3,"number_of_data_nodes":3,"active_primary_shards":13,"active_shards":26,"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}
The text was updated successfully, but these errors were encountered: