# Monitoring Web Server Metrics training: issue to connect to kibana **URL:** \ **Category:** Elastic Training\ **Created:** [April 16, 2019, 9:51am UTC](https://discuss.elastic.co/t/monitoring-web-server-metrics-training-issue-to-connect-to-kibana/177049 "2019-04-16T09:51:59Z")\ **Posts on this page:** 13\ **Page:** 1
**Author:** ![Thibaut\_M](https://avatars.discourse-cdn.com/v4/letter/t/d6d6ee/32.png) [@Thibaut\_M](https://discuss.elastic.co/u/Thibaut_M)\ **Post date:** [April 16, 2019, 9:51am UTC](https://discuss.elastic.co/t/monitoring-web-server-metrics-training-issue-to-connect-to-kibana/177049/1 "2019-04-16T09:51:59Z")
Hello, I follow the course " Monitoring Web Server Metrics" but i can't connect to Kibana and therefore cannot pursue the Lab and training. I'm blocked in Lab 2 question 3. Could yo help me to setup Kibana. I don't know why this doesn't work Thank you ---
**Author:** ![abdon](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/abdon/32/9195_2.png) [@abdon](https://discuss.elastic.co/u/abdon)\ **Post date:** [April 16, 2019, 10:59pm UTC](https://discuss.elastic.co/t/monitoring-web-server-metrics-training-issue-to-connect-to-kibana/177049/2 "2019-04-16T22:59:25Z")
Hi Thibaut, Can you please try the following? Open a new terminal tab in the Strigo virtual lab environment, and stop Kibana: ```auto kill $(ps aux | grep '[k]ibana' | awk '{print $2}') ``` Next, start Kibana in the foreground: ```auto ./kibana/bin/kibana ``` And post the output here? (Just the output that's visibile in the terminal should be enough) ---
**Author:** ![Thibaut\_M](https://avatars.discourse-cdn.com/v4/letter/t/d6d6ee/32.png) [@Thibaut\_M](https://discuss.elastic.co/u/Thibaut_M)\ **Post date:** [April 17, 2019, 8:26am UTC](https://discuss.elastic.co/t/monitoring-web-server-metrics-training-issue-to-connect-to-kibana/177049/3 "2019-04-17T08:26:29Z")
Hi Abdon, I can't even connect to the lab now... Preparing workstation is displayed since 10 minutes. ![image](https://us1.discourse-cdn.com/elastic/original/3X/2/3/237c4b9a6d2ff6e3e5f126a72709ee1b15b2d3e4.png) ---
**Author:** ![abdon](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/abdon/32/9195_2.png) [@abdon](https://discuss.elastic.co/u/abdon)\ **Post date:** [April 17, 2019, 8:55am UTC](https://discuss.elastic.co/t/monitoring-web-server-metrics-training-issue-to-connect-to-kibana/177049/4 "2019-04-17T08:55:08Z")
Hi Thibaut, I have restarted your VM. Hopefully you are able to access it now. You will now have to start with lab 2 from the beginning. I recommend running Elasticsearch and Kibana in the foreground. Step 2, start Elasticsearch like this: ```auto ./elasticsearch/bin/elasticsearch ``` Step 3, open a new terminal and start Kibana like this: ```auto ./kibana/bin/kibana ``` If after that you are still unable to access Kibana, please post the output of the Kibana terminal here. ---
**Author:** ![Thibaut\_M](https://avatars.discourse-cdn.com/v4/letter/t/d6d6ee/32.png) [@Thibaut\_M](https://discuss.elastic.co/u/Thibaut_M)\ **Post date:** [April 17, 2019, 9:33am UTC](https://discuss.elastic.co/t/monitoring-web-server-metrics-training-issue-to-connect-to-kibana/177049/5 "2019-04-17T09:33:17Z")
Hi Abdon, Still can't acces to the lab, same as the screenshot above. ---
**Author:** ![abdon](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/abdon/32/9195_2.png) [@abdon](https://discuss.elastic.co/u/abdon)\ **Post date:** [April 17, 2019, 9:36am UTC](https://discuss.elastic.co/t/monitoring-web-server-metrics-training-issue-to-connect-to-kibana/177049/6 "2019-04-17T09:36:12Z")
Sorry about the problems you're experiencing. I have now completely replaced your lab environment with a new one. Could you try again to see if that has resolved the issue? ---
**Author:** ![Thibaut\_M](https://avatars.discourse-cdn.com/v4/letter/t/d6d6ee/32.png) [@Thibaut\_M](https://discuss.elastic.co/u/Thibaut_M)\ **Post date:** [April 17, 2019, 12:13pm UTC](https://discuss.elastic.co/t/monitoring-web-server-metrics-training-issue-to-connect-to-kibana/177049/7 "2019-04-17T12:13:12Z")
The lab is working but still can't access kibana. But the logs seems good : ![image](https://us1.discourse-cdn.com/elastic/original/3X/2/0/20515981b39302ccd97a3fa62329df26d78fe0fc.png) But i got "This page isn't working" : ![image](https://us1.discourse-cdn.com/elastic/original/3X/4/9/49e4450280e09dddef02693e7024bc359c05f116.png) ---
**Author:** ![Thibaut\_M](https://avatars.discourse-cdn.com/v4/letter/t/d6d6ee/32.png) [@Thibaut\_M](https://discuss.elastic.co/u/Thibaut_M)\ **Post date:** [April 17, 2019, 12:33pm UTC](https://discuss.elastic.co/t/monitoring-web-server-metrics-training-issue-to-connect-to-kibana/177049/8 "2019-04-17T12:33:01Z")
Nevermind, this a problem on my side, I need to open 5601 Thank you for your help Thibaut ---
**Author:** ![abdon](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/abdon/32/9195_2.png) [@abdon](https://discuss.elastic.co/u/abdon)\ **Post date:** [April 17, 2019, 12:36pm UTC](https://discuss.elastic.co/t/monitoring-web-server-metrics-training-issue-to-connect-to-kibana/177049/9 "2019-04-17T12:36:06Z")
Yeah, I was just thinking the same. Glad you figured it out! You could also run Kibana on a different port: ```auto kibana/bin/kibana --port 8080 ``` ---
**Author:** ![Thibaut\_M](https://avatars.discourse-cdn.com/v4/letter/t/d6d6ee/32.png) [@Thibaut\_M](https://discuss.elastic.co/u/Thibaut_M)\ **Post date:** [April 17, 2019, 12:46pm UTC](https://discuss.elastic.co/t/monitoring-web-server-metrics-training-issue-to-connect-to-kibana/177049/10 "2019-04-17T12:46:44Z")
I made a request to open 5601 I tried to specify port 8080 but still can't connect to kibana... Also is it normal to have this as bound\_adresses? : ![image](https://us1.discourse-cdn.com/elastic/original/3X/0/1/0159202d5d7b869595c9b9aea80e7c01b2d96f0c.png) ---
**Author:** ![abdon](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/abdon/32/9195_2.png) [@abdon](https://discuss.elastic.co/u/abdon)\ **Post date:** [April 17, 2019, 12:53pm UTC](https://discuss.elastic.co/t/monitoring-web-server-metrics-training-issue-to-connect-to-kibana/177049/11 "2019-04-17T12:53:40Z")
Yeah, that's not a problem, for Elasticsearch. You could try some other ports for Kibana. 443 is also a port that's commonly open. ---
**Author:** ![Thibaut\_M](https://avatars.discourse-cdn.com/v4/letter/t/d6d6ee/32.png) [@Thibaut\_M](https://discuss.elastic.co/u/Thibaut_M)\ **Post date:** [April 17, 2019, 1:03pm UTC](https://discuss.elastic.co/t/monitoring-web-server-metrics-training-issue-to-connect-to-kibana/177049/12 "2019-04-17T13:03:33Z")
Ok thank you, Don't work either ☹ ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [May 15, 2019, 1:17pm UTC](https://discuss.elastic.co/t/monitoring-web-server-metrics-training-issue-to-connect-to-kibana/177049/13 "2019-05-15T13:17:52Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.