# Help With - Kibana server is not ready yet

**URL:** <https://discuss.elastic.co/t/help-with-kibana-server-is-not-ready-yet/358381>\
**Category:** Kibana\
**Created:** [April 28, 2024, 8:35pm UTC](https://discuss.elastic.co/t/help-with-kibana-server-is-not-ready-yet/358381 "2024-04-28T20:35:15Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![tikoretech](https://avatars.discourse-cdn.com/v4/letter/t/e19b73/32.png) [@tikoretech](https://discuss.elastic.co/u/tikoretech)\
**Post date:** [April 28, 2024, 8:35pm UTC](https://discuss.elastic.co/t/help-with-kibana-server-is-not-ready-yet/358381/1 "2024-04-28T20:35:15Z")

</div>

Please help me...

I dont start my kibana

```auto
server {
      server_name dmarc.koretech.com.br;

      access_log /var/log/nginx/dmarc.access;
      error_log /var/log/nginx/dmarc.error;

      add_header X-Frame-Options SAMEORIGIN;
      add_header X-Content-Type-Options nosniff;

      location / {
         proxy_pass http://127.0.0.1:5601;
         proxy_set_header Host $host;
         proxy_set_header X-Real-IP $remote_addr;
         proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
      }

    listen [::]:443 ssl ipv6only=on; # managed by Certbot
    listen 443 ssl; # managed by Certbot
    ssl_certificate /etc/letsencrypt/live/dmarc.koretech.com.br/fullchain.pem; # managed by Certbot
    ssl_certificate_key /etc/letsencrypt/live/dmarc.koretech.com.br/privkey.pem; # managed by Certbot
    include /etc/letsencrypt/options-ssl-nginx.conf; # managed by Certbot
    ssl_dhparam /etc/letsencrypt/ssl-dhparams.pem; # managed by Certbot

    add_header Strict-Transport-Security "max-age=31536000" always; # managed by Certbot

    ssl_trusted_certificate /etc/letsencrypt/live/dmarc.koretech.com.br/chain.pem; # managed by Certbot
    ssl_stapling on; # managed by Certbot
    ssl_stapling_verify on; # managed by Certbot
    auth_basic "Login required";
    auth_basic_user_file /etc/nginx/htpasswd;
}
server {

```

---

<div class="post-metadata">

**Author:** ![carly.richmond](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/carly.richmond/32/104935_2.png) [@carly.richmond](https://discuss.elastic.co/u/carly.richmond)\
**Post date:** [April 29, 2024, 9:04am UTC](https://discuss.elastic.co/t/help-with-kibana-server-is-not-ready-yet/358381/2 "2024-04-29T09:04:49Z")

</div>

Hi @tikoretech,

There are a few reasons for this error. Can you try following the troubleshooting steps available in [this common issues post](https://discuss.elastic.co/t/kibana-server-is-not-ready-yet/241217). If you are still encountering the error place share your Kibana and Elasticsearch versions and logs as the post advises.

Hope that helps!

---

<div class="post-metadata">

**Author:** ![tikoretech](https://avatars.discourse-cdn.com/v4/letter/t/e19b73/32.png) [@tikoretech](https://discuss.elastic.co/u/tikoretech)\
**Post date:** [April 29, 2024, 12:06pm UTC](https://discuss.elastic.co/t/help-with-kibana-server-is-not-ready-yet/358381/3 "2024-04-29T12:06:13Z")

</div>

I follow this instructions:

> **[Configuração de SSL, TLS e HTTPS para proteger o Elasticsearch, o Kibana, o...](https://www.elastic.co/pt/blog/configuring-ssl-tls-and-https-to-secure-elasticsearch-kibana-beats-and-logstash#step-2-4)**
>
> Sente-se inseguro quanto à segurança do Elastic Stack? Leia instruções passo a passo para configurar a criptografia TLS e o https no Elasticsearch, no Kibana, no Logstash e no Beats para aumentar as d...

Now the pages don't even open... and I don't know what it could be...

---

<div class="post-metadata">

**Author:** ![carly.richmond](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/carly.richmond/32/104935_2.png) [@carly.richmond](https://discuss.elastic.co/u/carly.richmond)\
**Post date:** [April 30, 2024, 1:22pm UTC](https://discuss.elastic.co/t/help-with-kibana-server-is-not-ready-yet/358381/4 "2024-04-30T13:22:18Z")

</div>

Hi @tikoretech,

Did the above solve your issue? It is a post from 2019 so steps may have changed in that time. I see it's been marked as resolved but you comment suggests an issue following along.

If you're still having an issue do share any errors you see in the logs.