Here, I provide the Procedure what I follow to setup a Elastic Search and Kibana on GCP Vm's: Created a 2 Vm's of Es and Kibana with Reserved Internal and External Ip's. Successfully Deployed Es and Kibana Debian packages On respective Vm's. Successfully Reconfigured the YAML files for both ES and…

After changing the default network to Custom VPC(Virtual Private Cloud) for an instance and also changed some configuration settings in YAML files. So, successfully browse the Kibana. Thanks for your support

Hi @ram_222 Welcome to the community! I formatted your post because it was very difficult to read. Please try to format in the future. [image] ram_222: curl -XGET "https://Internal_Ip Addr of Kibana:5601" Kibana is most likely running on http not https according to your configurations.

@stephenb I tried with http but it throws same error curl -XGET "http://10.x.x.x:5601" curl: (7) Failed to connect to 10.x.x.x port 5601: Connection refused

try curl-v -XGET "http://10.x.x.x:5601" Looks like a connectivity issue... OR kibana is not running at all. How did you start Kibana? Did you check the logs? what is the result of systemctl status kibana What do the logs show... tail -f /var/log/kibana/kibana.log

@stephenb First Checked the status of Kibana root@kibana:~# sudo systemctl status kibana.service ● kibana.service - Kibana Loaded: loaded (/usr/lib/systemd/system/kibana.service; enabled; vendor preset: enabled) Active: active (running) since Mon 2023-04-17 15:13:40 UTC; 13s ago Docs: …

Looks like a connectivity issue to me... You might need to look back further into the logs but at first look looks like kibana to be running... do you see kibana listening on 5601

The Kibana Port isn't listening in Kibana Instance netstat -anpe | grep LISTEN output: tcp 0 0 127.0.0.53:53 0.0.0.0:* LISTEN 101 22012 1241/systemd-resolv tcp 0 0 0.0.0.0:22 0.0.0.0:* LISTEN 0 …

You need to look further at the kibana logs. Stop Kibana Remove the Log file. Start kibana and look at the entire logs Not sure what the issue is You can try setting in kibana.yml server.host: 0.0.0.0

First I tried what you say Stop Kibana Remove the Log file. Start kibana and look at the entire logs So at that time the logs is be: {"service":{"node":{"roles":["background_tasks","ui"]}},"ecs":{"version":"8.6.0"},"@timestamp":"2023-04-18T05:14:41.967+00:00","message":"Kibana process configure…

Hello @stephenb....can you please look at the issue

[image] ram_222: Hello @stephenb....can you please look at the issue Please be patient There are many questions on this forum and yours is no more important than anyone else's. There's no SLA. This is a community forum and we are not all in the same time zone. I do not know what's happening…

Curl: (7) Failed to connect to 10.x.x.x port 5601: Connection refused

Elastic Stack Kibana

stephenb (Stephen Brown) April 17, 2023, 2:04pm 2

Hi @ram_222 Welcome to the community! I formatted your post because it was very difficult to read. Please try to format in the future.

Kibana is most likely running on http not https according to your configurations.

Topic		Replies	Views
Curl: (7) Failed to connect to 1.x.x.x port 5601: Connection refused Kibana	5	17408	August 31, 2018
Cannot connect to kibana through port 5601 Kibana	4	10328	June 29, 2021
I have Kibana Running and Elasticsearch also running but I can not get to the Kibana URL Kibana	4	748	December 29, 2022
Kibana 6.2.3: localhost port 5061: Connection refused Kibana	2	4119	March 25, 2018
New installation - Unable to connect to kibana 7.9.2 Kibana	4	1160	November 30, 2020

Curl: (7) Failed to connect to 10.x.x.x port 5601: Connection refused

Related topics