# Error setting up Dashboards **URL:** \ **Category:** Elasticsearch\ **Created:** [May 15, 2020, 10:01pm UTC](https://discuss.elastic.co/t/error-setting-up-dashboards/232887 "2020-05-15T22:01:25Z")\ **Posts on this page:** 6\ **Page:** 1
**Author:** ![eemtzc](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/eemtzc/32/54095_2.png) [@eemtzc](https://discuss.elastic.co/u/eemtzc)\ **Post date:** [May 15, 2020, 10:01pm UTC](https://discuss.elastic.co/t/error-setting-up-dashboards/232887/1 "2020-05-15T22:01:26Z")
Hello, I have a 7 node ES cluster based on 3 MN and 4 DN version 7.5, using TLS. The cluster has been working without a problem until this morning when I attempt to install auditbeat on one master node to start testing and getting information. The problem started when I ran auditbeat setup --dashboards in order to setup the dashboards in Kibana. When I ran the mentioned command I get: ```auto auditbeat setup --dashboards Loading dashboards (Kibana must be running and reachable Exiting: error connecting to Kibana: fail to get the Kibana version: HTTP GET request to https://hostname.domain.com:5601/api/status fails: fail to execute the HTTP GET request: Get https://hostname.domain.com:5601/api/status: dial tcp serverip:5601: connect: connection refused. Response: . ``` I already review some of the responses that are on this platform and my configuration is the same. Actually when I typed [https://hostname.domain.com:5601/api/status](https://hostname.domain.com:5601/api/status) on my browser I don't get a response back, but if I remove the 5601 port I get a response back. so I logged in into my Kibana server and added a non-loop back address to the local host 0.0.0.0 IP address, now I am able to see the same response if I type [https://hostname.domain.com:5601/api/status](https://hostname.domain.com:5601/api/status) on the browser including the port but if I ran the setup command to install the dashboards I still get the same error, no matter on what server I am, I already even try a windows server installing a filebeat and trying to import the filebeat dashboards same error. Also tried the solution I saw here about adding the following fields to the auditbeat.yml file ssl.enabled: true ssl.certificate\_authorities: ["/etc/auditbeat/certs/ca.pem"] ssl.verification\_mode: none and still the same. Weird thing is that I was able to started auditbeat without an issue and it was able to import the new index and start adding documents to the cluster. Any ideas? I've been having this issue for 3 days now and nothing, not even ES support has been able to help. Thank you ---
**Author:** ![ropc](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/ropc/32/47022_2.png) [@ropc](https://discuss.elastic.co/u/ropc)\ **Post date:** [May 17, 2020, 4:33am UTC](https://discuss.elastic.co/t/error-setting-up-dashboards/232887/2 "2020-05-17T04:33:07Z")
Hi @eemtzc - I checked your support case and I see that our support engineer provided an update to you. Could you follow-up with our support team in the support case? If you could send the `auditbeat.yml` and `kibana.yml` configuration files in the support case, our support team will review them and provide further guidance. Thank you for your collaboration. ---
**Author:** ![eemtzc](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/eemtzc/32/54095_2.png) [@eemtzc](https://discuss.elastic.co/u/eemtzc)\ **Post date:** [May 18, 2020, 9:31pm UTC](https://discuss.elastic.co/t/error-setting-up-dashboards/232887/3 "2020-05-18T21:31:38Z")
Hello @ropc sorry but I don't see where did the support engineer update the case. If you could point me I will send the files to him. Thank you ---
**Author:** ![ropc](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/ropc/32/47022_2.png) [@ropc](https://discuss.elastic.co/u/ropc)\ **Post date:** [May 19, 2020, 1:31pm UTC](https://discuss.elastic.co/t/error-setting-up-dashboards/232887/4 "2020-05-19T13:31:53Z")
@eemtzc - Let me send you a private message. ---
**Author:** ![eemtzc](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/eemtzc/32/54095_2.png) [@eemtzc](https://discuss.elastic.co/u/eemtzc)\ **Post date:** [May 19, 2020, 9:30pm UTC](https://discuss.elastic.co/t/error-setting-up-dashboards/232887/5 "2020-05-19T21:30:25Z")
Another solution for this same error. Loading dashboards (Kibana must be running and reachable) Exiting: error connecting to Kibana: fail to get the Kibana version: HTTP GET request to h[ttps://kibana.domain:5601/api/status](https://mryt2kb01.languageline.com:5601/api/status) fails: fail to execute the HTTP GET request: Get [https://kibana.domain.com:5601/api/status](https://mryt2kb01.languageline.com:5601/api/status): dial tcp kibanaip:5601: connect: connection refused. Response: . 1. Stop the beat you are trying to setup the dashboards for. 2. Go to kibana server on the Kibana.yml file Change the following ```auto server.host: 0.0.0.0 * Uncomment * #server.ssl.enabled: true * #server.ssl.key: /etc/kibana//.key * #server.ssl.certificate: /etc/kibana//.crt * Restart Kibana Service * Restart the beat service ``` On the beat server: test by running : ```auto curl -v h[ttps://kibana.domain:5601/api/status] (You should see connection establish, probably will show an error but won't be the same error) try: beatname setup --dashboard ``` Dashboards should load Once dashboards load into kibana, return all the settings to the way they were and restart kibana and beat service. ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [June 16, 2020, 9:30pm UTC](https://discuss.elastic.co/t/error-setting-up-dashboards/232887/6 "2020-06-16T21:30:35Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.