Strigo lab error in ElasticSearch Engineer 1 ondemand class lab 1.3

I am currently undertaking ES Engineer 1 on demand course and working in Strigo to conduct the labs.
In Lab 1.3 I am looking to start Kibana in a second server tab, with the first running ES. The Kibana launcher errors and closes after a number of errors being reported.

As the failure of Kibana prevents this lab and later ones I am looking for any help in correcting the environment.
The Kibana logs are showing comms issues in communicating to the Elastic cluster:

log [10:24:31.490] [info][status][plugin:encrypted_saved_objects@7.3.1] Status changed from uninitialized to green - Ready
log [10:24:31.500] [info][status][plugin:snapshot_restore@7.3.1] Status changed from uninitialized to yellow - Waiting for Elasticsearch
log [10:24:31.508] [info][status][plugin:actions@7.3.1] Status changed from uninitialized to green - Ready
log [10:24:31.515] [info][status][plugin:alerting@7.3.1] Status changed from uninitialized to green - Ready
log [10:24:31.518] [info][status][plugin:data@7.3.1] Status changed from uninitialized to green - Ready
log [10:24:31.658] [info][status][plugin:timelion@7.3.1] Status changed from uninitialized to green - Ready
log [10:24:31.662] [info][status][plugin:ui_metric@7.3.1] Status changed from uninitialized to green - Ready
log [10:24:31.665] [info][status][plugin:visualizations@7.3.1] Status changed from uninitialized to green - Ready
log [10:24:32.128] [info][status][plugin:elasticsearch@7.3.1] Status changed from yellow to green - Ready
log [10:24:32.138] [error][status][plugin:xpack_main@7.3.1] Status changed from yellow to red - [data] Elasticsearch cluster did not respond with license information.
log [10:24:32.139] [error][status][plugin:graph@7.3.1] Status changed from yellow to red - [data] Elasticsearch cluster did not respond with license information.
log [10:24:32.140] [error][status][plugin:spaces@7.3.1] Status changed from yellow to red - [data] Elasticsearch cluster did not respond with license information.
log [10:24:32.141] [error][status][plugin:searchprofiler@7.3.1] Status changed from yellow to red - [data] Elasticsearch cluster did not respond with license information.
log [10:24:32.142] [error][status][plugin:ml@7.3.1] Status changed from yellow to red - [data] Elasticsearch cluster did not respond with license information.
log [10:24:32.142] [error][status][plugin:tilemap@7.3.1] Status changed from yellow to red - [data] Elasticsearch cluster did not respond with license information.
log [10:24:32.143] [error][status][plugin:watcher@7.3.1] Status changed from yellow to red - [data] Elasticsearch cluster did not respond with license information.
log [10:24:32.144] [error][status][plugin:grokdebugger@7.3.1] Status changed from yellow to red - [data] Elasticsearch cluster did not respond with license information.
log [10:24:32.144] [error][status][plugin:logstash@7.3.1] Status changed from yellow to red - [data] Elasticsearch cluster did not respond with license information.
log [10:24:32.145] [error][status][plugin:beats_management@7.3.1] Status changed from yellow to red - [data] Elasticsearch cluster did not respond with license information.
log [10:24:32.145] [error][status][plugin:maps@7.3.1] Status changed from yellow to red - [data] Elasticsearch cluster did not respond with license information.
log [10:24:32.145] [error][status][plugin:index_management@7.3.1] Status changed from yellow to red - [data] Elasticsearch cluster did not respond with license information.
log [10:24:32.146] [error][status][plugin:index_lifecycle_management@7.3.1] Status changed from yellow to red - [data] Elasticsearch cluster did not respond with license information.
log [10:24:32.146] [error][status][plugin:rollup@7.3.1] Status changed from yellow to red - [data] Elasticsearch cluster did not respond with license information.
log [10:24:32.147] [error][status][plugin:remote_clusters@7.3.1] Status changed from yellow to red - [data] Elasticsearch cluster did not respond with license information.
log [10:24:32.147] [error][status][plugin:cross_cluster_replication@7.3.1] Status changed from yellow to red - [data] Elasticsearch cluster did not respond with license information.
log [10:24:32.147] [error][status][plugin:file_upload@7.3.1] Status changed from yellow to red - [data] Elasticsearch cluster did not respond with license information.
log [10:24:32.148] [error][status][plugin:snapshot_restore@7.3.1] Status changed from yellow to red - [data] Elasticsearch cluster did not respond with license information.
log [10:24:32.738] [warning][browser-driver][reporting] Enabling the Chromium sandbox provides an additional layer of protection.
log [10:24:32.755] [warning][reporting] Generating a random key for xpack.reporting.encryptionKey. To prevent pending reports from failing on restart, please set xpack.reporting.encryptionKey in kibana.yml
log [10:24:32.760] [error][status][plugin:reporting@7.3.1] Status changed from uninitialized to red - [data] Elasticsearch cluster did not respond with license information.
log [10:24:32.788] [error][status][plugin:security@7.3.1] Status changed from green to red - [data] Elasticsearch cluster did not respond with license information.
^C
[elastic@server1 ~]$

Thank you for raising this issue.

My guess is that you did not start Elasticsearch with the right parameters as specified in the last question of the lab 1.2. To solve this issue:

  1. Shut down Kibana
  2. Shut down your Elasticsearch node
  3. Start Elasticsearch using the following command: ./elasticsearch-7.3.1/bin/elasticsearch -E node.name=node1 -E http.host="localhost","server1"
  4. Start Kibana using the following command line: ./kibana-7.3.1-linux-x86_64/bin/kibana --host=0.0.0.0

This should fix your issue. If it doesn't would you be able to add information relative to the log on the Elasticsearch side?

Thanks that worked ok.

Looking at the next step to load the SQL data I do not see the dataset folder on the server, is it possible to restore it?

Good to hear that it helped.

Regarding the datasets folder, it should be in server1. I can restore it but by doing so it will reinitialize the whole lab environment. Send me your email address in a private message if you want me to move forward with this option.