# Error conecting to kibana **URL:** \ **Category:** Beats\ **Tags:** winlogbeat\ **Created:** [July 9, 2019, 10:31am UTC](https://discuss.elastic.co/t/error-conecting-to-kibana/189521 "2019-07-09T10:31:55Z")\ **Posts on this page:** 8\ **Page:** 1
**Author:** ![sarahmech](https://avatars.discourse-cdn.com/v4/letter/s/b487fb/32.png) [@sarahmech](https://discuss.elastic.co/u/sarahmech)\ **Post date:** [July 9, 2019, 10:31am UTC](https://discuss.elastic.co/t/error-conecting-to-kibana/189521/1 "2019-07-09T10:31:55Z")
Hi ! i can't cnnecting to kibana, can you help me thank you ![image](https://us1.discourse-cdn.com/elastic/original/3X/c/1/c1e450279a454ecd529547fb603487c786e27b5d.png) my winlogbeat.yml winlogbeat.event\_logs: - name: Application - name: Security - name: System output.elasticsearch: hosts: - localhost:9200 output.elasticsearch: hosts: "IP:9200" setup.kibana: host: "IP:5601" logging.to\_files: true logging.files: path: C:\Programmes Files\Winlogbeat\Logs logging.level: info setup.dashboards.enabled: true ---
**Author:** ![andrewkroh](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/andrewkroh/32/3784_2.png) [@andrewkroh](https://discuss.elastic.co/u/andrewkroh)\ **Post date:** [July 10, 2019, 1:33am UTC](https://discuss.elastic.co/t/error-conecting-to-kibana/189521/2 "2019-07-10T01:33:12Z")
If you try the same URL shown in the error message from your web browser on the Windows machine running Winlogbeat do you get back a status response from Kibana? Is Kibana configured to listen outside of localhost? Try setting `server.host: 0.0.0.0`. [https://www.elastic.co/guide/en/kibana/current/settings.html](https://www.elastic.co/guide/en/kibana/current/settings.html) ---
**Author:** ![sarahmech](https://avatars.discourse-cdn.com/v4/letter/s/b487fb/32.png) [@sarahmech](https://discuss.elastic.co/u/sarahmech)\ **Post date:** [July 10, 2019, 7:31am UTC](https://discuss.elastic.co/t/error-conecting-to-kibana/189521/3 "2019-07-10T07:31:30Z")
hi, thank you for your reply, it's inaccessible, and yes the server.host is 0.0.0.0, ---
**Author:** ![andrewkroh](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/andrewkroh/32/3784_2.png) [@andrewkroh](https://discuss.elastic.co/u/andrewkroh)\ **Post date:** [July 11, 2019, 4:13pm UTC](https://discuss.elastic.co/t/error-conecting-to-kibana/189521/4 "2019-07-11T16:13:05Z")
On the kibana host you can double check the listening port with `netstat -an | grep 5601`. You should see a listening socket bound to 0.0.0.0. If that's in working as expected then I would check to see if there are any firewalls. ---
**Author:** ![andrewkroh](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/andrewkroh/32/3784_2.png) [@andrewkroh](https://discuss.elastic.co/u/andrewkroh)\ **Post date:** [July 11, 2019, 4:14pm UTC](https://discuss.elastic.co/t/error-conecting-to-kibana/189521/5 "2019-07-11T16:14:36Z")
I also notice that your config is showing two `output.elasticsearch.hosts` settings. You should remove one of them. But this should be affecting the setup connection to Kibana. ---
**Author:** ![sarahmech](https://avatars.discourse-cdn.com/v4/letter/s/b487fb/32.png) [@sarahmech](https://discuss.elastic.co/u/sarahmech)\ **Post date:** [July 12, 2019, 7:27am UTC](https://discuss.elastic.co/t/error-conecting-to-kibana/189521/6 "2019-07-12T07:27:35Z")
[root@localhost ~]# netstat -an | grep 5601 tcp 0 0 127.0.0.1:5601 0.0.0.0:\* LISTEN PS F:\Winlogbeat\winlogbeat-7.2.0-windows-x86\_64\> .\winlogbeat.exe test output -c .\winlogbeat.yml -e 2019-07-12T09:23:49.283+0200 INFO instance/beat.go:606 Home path: [F:\Winlogbeat\winlogbeat-7.2.0-windows-x86\_6 4] Config path: [F:\Winlogbeat\winlogbeat-7.2.0-windows-x86\_64] Data path: [F:\Winlogbeat\winlogbeat-7.2.0-windows-x86\_6 4\data] Logs path: [F:\Winlogbeat\winlogbeat-7.2.0-windows-x86\_64\logs] 2019-07-12T09:23:49.360+0200 INFO instance/beat.go:614 Beat ID: 3a696b66-ed6e-41ba-97ec-93e0ed5fd49f 2019-07-12T09:23:49.360+0200 INFO [index-management] idxmgmt/std.go:178 Set output.elasticsearch.index t o 'winlogbeat-7.2.0' as ILM is enabled. 2019-07-12T09:23:49.360+0200 INFO elasticsearch/client.go:166 Elasticsearch url: [http://192.168.1.X:9200](http://192.168.1.X:9200) elasticsearch: [http://192.168.1.178:9200](http://192.168.1.178:9200)... parse url... OK connection... parse host... OK dns lookup... OK addresses: 192.168.1.X dial up... ERROR dial tcp 192.168.1.X:9200: connectex: Une tentative de connexion a échoué car le parti connecté n 'a pas répondu convenablement au-delà d'une certaine durée ou une connexion établie a échoué car l'hôte de connexion n'a pas répondu. I delete one output.elasticsearch.hosts, its inaccessible ☹ ---
**Author:** ![sarahmech](https://avatars.discourse-cdn.com/v4/letter/s/b487fb/32.png) [@sarahmech](https://discuss.elastic.co/u/sarahmech)\ **Post date:** [July 17, 2019, 1:02pm UTC](https://discuss.elastic.co/t/error-conecting-to-kibana/189521/7 "2019-07-17T13:02:46Z")
Hi Andrew, I solve the problem that i had. ![image](https://us1.discourse-cdn.com/elastic/original/3X/f/8/f89386af21bbc909900f11b3fe40037a212d179c.png) But, i have this error now ! Can you help me please. ![image](https://us1.discourse-cdn.com/elastic/original/3X/9/0/90238b7c55c63ca1dd4869e155c1235fc75f7402.png) thank you. ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [August 14, 2019, 1:02pm UTC](https://discuss.elastic.co/t/error-conecting-to-kibana/189521/8 "2019-08-14T13:02:46Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.