Log not visible on Kibana Interface

This command output is like this

[root@lockout ~]# curl -XGET 'http://localhost:5601/api/status'
curl: (7) Failed connect to localhost:5601; Connection refused

nano /etc/kibana/kibana.yml

server.port: 5601
server.host: "10.**.**.**"
server.ssl.enabled: true
server.ssl.key: /etc/kibana/ssl/_.****.key
server.ssl.certificate:  /etc/kibana/ssl/_.****.crt
#server.ssl.supportedProtocols: [ 'TLSv1.2', 'TLSv1.3' ]
server.name: "lockout.lcwaikiki.local"
elasticsearch.url: "http://127.0.0.1:9200"
elasticsearch.username: "elastic"
elasticsearch.password: "elastic"
xpack.monitoring.elasticsearch.username: "***"
xpack.monitoring.elasticsearch.password: "***"
#xpack.encryptedSavedObjects.encryptionKey: 2d2e4818f028fa5d64e38dfa3fd2763
#xpack.reporting.encryptionKey: c065608433eeeb5f2545635a2e2549a6
#xpack.security.encryptionKey: 9a936b0e053zts230fdeb77cbe64af5
xpack.reporting.enabled: false
logging.dest: "/var/log/kibana/kibana.log"
logging.verbose: true
logging.quiet: false
logging.silent: false

You keep throwing more info into the thread, and I am a bit lost.

The screenshot was for creating an index pattern, not creating an index itself. A pattern like "logstash-*" would probably be fine here.

You can obviously access kibana, so what do you see in the discover screen. What, if any, index patterns do you have already? (top left of the screen)

Yeah, not sure what that was trying to achieve.

Your elasticsearch (pot 9200) config had

xpack.security.enabled: false

so no HTTPS needed

But kibana (port 5601) had

server.ssl.enabled: true

so you need HTTPS in that case.

Please run

curl -X GET "http://localhost:9200/_cat/indices?bytes=b&v"

then wait a few (10) minutes and and run again. And share output from both commands.