title: Kibana server is not ready yet
body: <p>I have just installed Kibana 7.3 on RHEL 8. The Kibana service is active (running).<br>
  I receive <code>Kibana server is not ready yet</code> message when i curl to <a href="http://localhost:5601" rel="noreferrer">http://localhost:5601</a>.
  My Elasticsearch instance is on another server and it is responding with succes to my requests. I have updated the kibana.yml with that</p>
  
  <blockquote>
    <p>elasticsearch.hosts:["<a href="http://EXTERNAL-IP-ADDRESS-OF-ES:9200" rel="noreferrer">http://EXTERNAL-IP-ADDRESS-OF-ES:9200</a>"]</p>
  </blockquote>
  
  <p>i can reach to elasticsearch from the internet with response:</p>
  
  <pre><code>{
    "name" : "ip-172-31-21-240.ec2.internal",
    "cluster_name" : "elasticsearch",
    "cluster_uuid" : "y4UjlddiQimGRh29TVZoeA",
    "version" : {
      "number" : "7.3.1",
      "build_flavor" : "default",
      "build_type" : "rpm",
      "build_hash" : "4749ba6",
      "build_date" : "2019-08-19T20:19:25.651794Z",
      "build_snapshot" : false,
      "lucene_version" : "8.1.0",
      "minimum_wire_compatibility_version" : "6.8.0",
      "minimum_index_compatibility_version" : "6.0.0-beta1"
    },
    "tagline" : "You Know, for Search"
  }
  </code></pre>
  
  <p>The result of the <code>sudo systemctl status kibana</code>:</p>
  
  <pre><code>● kibana.service - Kibana
     Loaded: loaded (/etc/systemd/system/kibana.service; enabled; vendor preset: disabled)
     Active: active (running) since Thu 2019-09-19 12:22:34 UTC; 24min ago
   Main PID: 4912 (node)
      Tasks: 21 (limit: 4998)
     Memory: 368.8M
     CGroup: /system.slice/kibana.service
             └─4912 /usr/share/kibana/bin/../node/bin/node --no-warnings --max-http-header-size&gt;
  
  Sep 19 12:46:42 ip-172-31-88-39.ec2.internal kibana[4912]: {"type":"log","@timestamp":"2019-0&gt;
  Sep 19 12:46:42 ip-172-31-88-39.ec2.internal kibana[4912]: {"type":"log","@timestamp":"2019-0&gt;
  Sep 19 12:46:43 ip-172-31-88-39.ec2.internal kibana[4912]: {"type":"log","@timestamp":"2019-0&gt;
  Sep 19 12:46:43 ip-172-31-88-39.ec2.internal kibana[4912]: {"type":"log","@timestamp":"2019-0&gt;
  Sep 19 12:46:43 ip-172-31-88-39.ec2.internal kibana[4912]: {"type":"log","@timestamp":"2019-0&gt;
  Sep 19 12:46:44 ip-172-31-88-39.ec2.internal kibana[4912]: {"type":"log","@timestamp":"2019-0
  </code></pre>
  
  <blockquote>
    <p>the result of "sudo journalctl --unit kibana"</p>
  </blockquote>
  
  <pre><code>Sep 19 06:03:53 ip-172-31-88-39.ec2.internal kibana[1356]: {"type":"log","@timestamp":"2019-09-19T06:03:53Z","tags":["warning","elasticsearch","admin"],"pid":1356,"message":"Unable to revive &gt;
  Sep 19 06:03:53 ip-172-31-88-39.ec2.internal kibana[1356]: {"type":"log","@timestamp":"2019-09-19T06:03:53Z","tags":["warning","elasticsearch","admin"],"pid":1356,"message":"No living connect&gt;
  Sep 19 06:03:53 ip-172-31-88-39.ec2.internal kibana[1356]: {"type":"log","@timestamp":"2019-09-19T06:03:53Z","tags":["warning","task_manager"],"pid":1356,"message":"PollError No Living connec&gt;
  Sep 19 06:03:53 ip-172-31-88-39.ec2.internal kibana[1356]: {"type":"log","@timestamp":"2019-09-19T06:03:53Z","tags":["warning","elasticsearch","admin"],"pid":1356,"message":"Unable to revive &gt;
  Sep 19 06:03:53 ip-172-31-88-39.ec2.internal kibana[1356]: {"type":"log","@timestamp":"2019-09-19T06:03:53Z","tags":["warning","elasticsearch","admin"],"pid":1356,"message":"No living connect&gt;
  </code></pre>
  
  <p>Do you have any idea where the problem is?</p>