First Verify the version of Kibana & elastic serach

Kibana - /usr/share/kibana/bin/kibana --version
Elasticsearch - /usr/share/elasticsearch/bin/elasticsearch --version

and then Check the logs for Kibana

/var/log/kibana/kibana.stderr

Check the logs for Elasticsearch

/var/log/elasticsearch/elasticsearch.log

The main issue for this problem as Elasticsearch is still initializing the kibana index

This behavior is sometimes caused by an existing .kibana index. Kindly delete the .kibana index in elasticsearch using following command

Fixed by using the command as following command

curl -XDELETE http://localhost:9200/.kibana

After deleting the index, restart Kibana.
If the problem still persists, and you dont bother about losing any existing data, you can try deleting all indexes using following command:

curl -XDELETE http://localhost:9200/*

Restart Kibana.

Note: localhost:9200 is the elasticsearch server's host:port, which may be different in your case

If your errors Fixed the the log will generate as shown here

/var/log/kibana/kibana.stdout

{"type":"log","@timestamp":"2019-01-31T13:33:56Z","tags":["status","plugin:cross_cluster_replication@6.6.0","info"],"pid":30204,"state":"green","message":"Status changed from yellow to green - Ready","prevState":"yellow","prevMsg":"Waiting for Elasticsearch"}
{"type":"log","@timestamp":"2019-01-31T13:33:56Z","tags":["info","monitoring-ui","kibana-monitoring"],"pid":30204,"message":"Starting monitoring stats collection"}
{"type":"log","@timestamp":"2019-01-31T13:33:56Z","tags":["status","plugin:security@6.6.0","info"],"pid":30204,"state":"green","message":"Status changed from yellow to green - Ready","prevState":"yellow","prevMsg":"Waiting for Elasticsearch"}
{"type":"log","@timestamp":"2019-01-31T13:33:56Z","tags":["reporting","warning"],"pid":30204,"message":"Generating a random key for xpack.reporting.encryptionKey. To prevent pending reports from failing on restart, please set xpack.reporting.encryptionKey in kibana.yml"}
{"type":"log","@timestamp":"2019-01-31T13:33:56Z","tags":["status","plugin:reporting@6.6.0","info"],"pid":30204,"state":"green","message":"Status changed from uninitialized to green - Ready","prevState":"uninitialized","prevMsg":"uninitialized"}
{"type":"log","@timestamp":"2019-01-31T13:33:56Z","tags":["license","info","xpack"],"pid":30204,"message":"Imported license information from Elasticsearch for the [monitoring] cluster: mode: basic | status: active"}
{"type":"log","@timestamp":"2019-01-31T13:33:57Z","tags":["info","migrations"],"pid":30204,"message":"Creating index .kibana_1."}
{"type":"log","@timestamp":"2019-01-31T13:33:57Z","tags":["info","migrations"],"pid":30204,"message":"Pointing alias .kibana to .kibana_1."}
{"type":"log","@timestamp":"2019-01-31T13:33:57Z","tags":["info","migrations"],"pid":30204,"message":"Finished in 628ms."}
{"type":"log","@timestamp":"2019-01-31T13:33:57Z","tags":["listening","info"],"pid":30204,"message":"Server running at http://192.168.7.7:5601"}
{"type":"log","@timestamp":"2019-01-31T13:33:58Z","tags":["status","plugin:spaces@6.6.0","info"],"pid":30204,"state":"green","message":"Status changed from yellow to green - Ready","prevState":"yellow","prevMsg":"Waiting for Elasticsearch"}

contextoI appreciate what you share in the post. Thanks to your post, I have gained a lot of new and useful knowledge. contextoenter link description here

If your kiabna server is not ready firstly chcek out that you have a propper internet connection because sometimes there are many connectivity issues.

Available here https://chuksdump.com Junk Removal Services in Lynnwood WA

Me, too.
Error:

Kibana did not load properly. Check the server output for more information.

Log:

{"type":"log","@timestamp":"2019-02-07T08:35:35Z","tags":["plugin","warning"],"pid":18066,"path":"/usr/local/Cellar/kibana/6.6.0/src/legacy/core_plugins/ems_util","message":"Skipping non-plugin directory at /usr/local/Cellar/kibana/6.6.0/src/legacy/core_plugins/ems_util"}

Your essay was so good.