# Kibana server is not ready yet **URL:** \ **Category:** Kibana\ **Created:** [March 16, 2022, 2:46pm UTC](https://discuss.elastic.co/t/kibana-server-is-not-ready-yet/299872 "2022-03-16T14:46:35Z")\ **Posts on this page:** 8\ **Page:** 1
**Author:** ![juliano.maciel](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/juliano.maciel/32/100169_2.png) [@juliano.maciel](https://discuss.elastic.co/u/juliano.maciel)\ **Post date:** [March 16, 2022, 2:46pm UTC](https://discuss.elastic.co/t/kibana-server-is-not-ready-yet/299872/1 "2022-03-16T14:46:36Z")
Hi, i'am tring to conifg Elastic Stack 7.16.2 with a windows server. My configs: Elasticsearch ![image](https://us1.discourse-cdn.com/elastic/original/3X/7/5/754a018c41d0b2cf9039ae036a8ba5d132c1fd49.png) ![image](https://us1.discourse-cdn.com/elastic/original/3X/c/b/cb9d790ff8639a543b6d9a1ddcfd69769fa33ad4.png) APM-server ![image](https://us1.discourse-cdn.com/elastic/original/3X/1/c/1c90ef6ff47fe972ade68487aba6096c541e87d8.png) ![image](https://us1.discourse-cdn.com/elastic/original/3X/f/8/f81f849df68a7e33f69b50db59adeaff70ada3c2.png) Kibana ![image](https://us1.discourse-cdn.com/elastic/original/3X/a/9/a915ae8a84b60281c89c06311b387958c881869f.png) When i try to acess Kibana, is show the message at the browser ![image](https://us1.discourse-cdn.com/elastic/original/3X/0/8/085ae9974de508dfb908a6e7d2f1bbe9105e2b7d.png) ---
**Author:** ![juliano.maciel](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/juliano.maciel/32/100169_2.png) [@juliano.maciel](https://discuss.elastic.co/u/juliano.maciel)\ **Post date:** [March 16, 2022, 2:50pm UTC](https://discuss.elastic.co/t/kibana-server-is-not-ready-yet/299872/2 "2022-03-16T14:50:42Z")
Security protocols are not configured as it is a PoC. ---
**Author:** ![hitnalli\_praveen](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/hitnalli_praveen/32/117794_2.png) [@hitnalli\_praveen](https://discuss.elastic.co/u/hitnalli_praveen)\ **Post date:** [March 16, 2022, 2:59pm UTC](https://discuss.elastic.co/t/kibana-server-is-not-ready-yet/299872/3 "2022-03-16T14:59:49Z")
Hi @juliano.maciel, Elasticsearch by default runs on :9200 port and Kibana runs on port :5601. Just a suggestion. Can you update your Elasticsearch.yml and Kibana.yml files to those respective ports, restart your Elasticsearch and kibana services and check again? Please lemme know if you can get the Kibana dashboard atleast after that. ---
**Author:** ![juliano.maciel](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/juliano.maciel/32/100169_2.png) [@juliano.maciel](https://discuss.elastic.co/u/juliano.maciel)\ **Post date:** [March 16, 2022, 3:10pm UTC](https://discuss.elastic.co/t/kibana-server-is-not-ready-yet/299872/4 "2022-03-16T15:10:16Z")
Hi, @hitnalli_praveen , i'am change the ports as they may be using an no production server I have some infrastructure limitations in the IT sector and allowed me access through these ports. I will check the possibility of releasing the default ports, but the policy should be applied tonight. ---
**Author:** ![hitnalli\_praveen](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/hitnalli_praveen/32/117794_2.png) [@hitnalli\_praveen](https://discuss.elastic.co/u/hitnalli_praveen)\ **Post date:** [March 16, 2022, 3:41pm UTC](https://discuss.elastic.co/t/kibana-server-is-not-ready-yet/299872/5 "2022-03-16T15:41:48Z")
Hi @juliano.maciel , Well, I get your point now. So if I understand your point correctly, you are hosting Elastic and Kibana on Production server ? If server is related to linux OS, by default ports :9200 and :5601 would be blocked due to firewall. Ya, may be once policy is applied you can give it a shot. Anyway, please keep me posted even after you get the solutions. I had faced exact issue what you are facing now. But my condition to trigger that issue of 'Kibana server not yet ready' due to some other issues. I want to hear in your case what was the issue and what solved for you 🙂 ---
**Author:** ![juliano.maciel](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/juliano.maciel/32/100169_2.png) [@juliano.maciel](https://discuss.elastic.co/u/juliano.maciel)\ **Post date:** [March 16, 2022, 5:08pm UTC](https://discuss.elastic.co/t/kibana-server-is-not-ready-yet/299872/6 "2022-03-16T17:08:01Z")
Hey @hitnalli_praveen , I found the solution, I stopped all windows services, Elasticsearch, apm-server and kibana, deleted the default node folder ..\Elastic Stack 7.16.2\Elasticsearch-7.16.2\data\nodes, and restarted the services. For some reason when consulting Elasticsearch health check its status was red with several unassigned shards ---
**Author:** ![hitnalli\_praveen](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/hitnalli_praveen/32/117794_2.png) [@hitnalli\_praveen](https://discuss.elastic.co/u/hitnalli_praveen)\ **Post date:** [March 16, 2022, 8:10pm UTC](https://discuss.elastic.co/t/kibana-server-is-not-ready-yet/299872/7 "2022-03-16T20:10:15Z")
@juliano.maciel , Great to hear that you could find the solution. Ok, restarting the services basically helped here. Thanks for letting know me your solution. ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [April 13, 2022, 8:11pm UTC](https://discuss.elastic.co/t/kibana-server-is-not-ready-yet/299872/8 "2022-04-13T20:11:05Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.