# Kibana won't up

**URL:** <https://discuss.elastic.co/t/kibana-wont-up/352648>\
**Category:** Elasticsearch\
**Created:** [February 6, 2024, 3:26pm UTC](https://discuss.elastic.co/t/kibana-wont-up/352648 "2024-02-06T15:26:45Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![sanjeev1895](https://avatars.discourse-cdn.com/v4/letter/s/e9a140/32.png) [@sanjeev1895](https://discuss.elastic.co/u/sanjeev1895)\
**Post date:** [February 6, 2024, 3:26pm UTC](https://discuss.elastic.co/t/kibana-wont-up/352648/1 "2024-02-06T15:26:45Z")

</div>

Hi,  
few month back I was configured the elk stack on aws ubuntu instance and it's works fine without any issue. But due to some VPC related reason, I was taken the AMI from that elk stack instance and launched the new instance from that.

After that when I load the site, it shows kibana server not yet ready. can any one help me out this

---

<div class="post-metadata">

**Author:** ![jessgarson](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jessgarson/32/129841_2.png) [@jessgarson](https://discuss.elastic.co/u/jessgarson)\
**Post date:** [February 6, 2024, 7:14pm UTC](https://discuss.elastic.co/t/kibana-wont-up/352648/2 "2024-02-06T19:14:44Z")

</div>

Thanks for reaching out. Have you seen [these steps](https://discuss.elastic.co/t/kibana-server-is-not-ready-yet/241217) to investigate this error? This might be a good starting point here.

---

<div class="post-metadata">

**Author:** ![sanjeev1895](https://avatars.discourse-cdn.com/v4/letter/s/e9a140/32.png) [@sanjeev1895](https://discuss.elastic.co/u/sanjeev1895)\
**Post date:** [February 14, 2024, 4:39am UTC](https://discuss.elastic.co/t/kibana-wont-up/352648/3 "2024-02-14T04:39:47Z")

</div>

@jessgarson  
I found the hostname of the server was changed (internal IP)... due to this when I run this command `curl --cacert /etc/elasticsearch/certs/http_ca.crt -u elastic https://172.30.196.114:9200` I'm getting the below error..

```auto
curl: (60) SSL: no alternative certificate subject name matches target host name '172.30.196.114'
More details here: https://curl.haxx.se/docs/sslcerts.html

curl failed to verify the legitimacy of the server and therefore could not
establish a secure connection to it. To learn more about this situation and
how to fix it, please visit the web page mentioned above.

```

Can you let me know how to fix this error

---

<div class="post-metadata">

**Author:** ![jessgarson](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jessgarson/32/129841_2.png) [@jessgarson](https://discuss.elastic.co/u/jessgarson)\
**Post date:** [February 14, 2024, 4:25pm UTC](https://discuss.elastic.co/t/kibana-wont-up/352648/4 "2024-02-14T16:25:12Z")

</div>

Thanks, @sanjeev1895; there was a similar [forum post](https://discuss.elastic.co/t/elasticsearch-certificate-error-when-access-with-public-ip/315213) to this a little while back that could be helpful. A good next step could be regenerating the HTTP cert to include the subject names / IPs you want. We have some [related documentation](https://www.elastic.co/guide/en/elasticsearch/reference/current/certutil.html).

---

<div class="post-metadata">

**Author:** ![sanjeev1895](https://avatars.discourse-cdn.com/v4/letter/s/e9a140/32.png) [@sanjeev1895](https://discuss.elastic.co/u/sanjeev1895)\
**Post date:** [February 15, 2024, 12:19pm UTC](https://discuss.elastic.co/t/kibana-wont-up/352648/5 "2024-02-15T12:19:49Z")

</div>

@jessgarson Thanks. I will follow up this.

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [March 14, 2024, 12:20pm UTC](https://discuss.elastic.co/t/kibana-wont-up/352648/6 "2024-03-14T12:20:03Z")

</div>

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.