Help With - Kibana server is not ready yet

Elastic Stack Kibana
1

Please help me...

I dont start my kibana

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 {
2

Hi @tikoretech,

There are a few reasons for this error. Can you try following the troubleshooting steps available in this common issues post. If you are still encountering the error place share your Kibana and Elasticsearch versions and logs as the post advises.

Hope that helps!

3

I follow this instructions:

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

4

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.