Kibana Server is not ready yet

Hi Team,

We are not able to login to kibana application as it throws an error "Kibana server is not ready yet. we recently renewed ssl certificate for kibana and we done sanity check at that time it works fine. can let us know it causes due to certificate issue. if yes please share the steps to renew kibana ssl certificate. Attached the screenshot

we use window server for kibana and elasticsearch. we also verified kibana and elasticsearch is running in services. Verified event viewer logs as well not found any error.

Welcome to our community! :smiley:

Please share your Kibana logs and config.

i dont see any option to attach an file. Please assist.

You need to paste the contents, please make sure you use code formatting for it as well.

Will share

Below is Kibana Config file:

Kibana is served by a back end server. This setting specifies the port to use.

server.port: 5601

Specifies the address to which the Kibana server will bind. IP addresses and host names are both valid values.

The default is 'localhost', which usually means remote machines will not be able to connect.

To allow connections from remote users, set this parameter to a non-loopback address. "localhost"

Enables you to specify a path to mount Kibana at if you are running behind a proxy.

Use the server.rewriteBasePath setting to tell Kibana if it should remove the basePath

from requests it receives, and to prevent a deprecation warning at startup.

This setting cannot end in a slash.

server.basePath: "/kibana"

Specifies the public URL at which Kibana is available for end users. If

server.basePath is configured this URL should end with the same basePath.

server.publicBaseUrl: ""

Specifies whether Kibana should rewrite requests that are prefixed with

server.basePath or require that they are rewritten by your reverse proxy.

This setting was effectively always false before Kibana 6.3 and will

default to true starting in Kibana 7.0.

server.rewriteBasePath: true

The maximum payload size in bytes for incoming server requests.

#server.maxPayloadBytes: 1048576

The Kibana server's name. This is used for display purposes. "rpadevwebws102"

The URLs of the Elasticsearch instances to use for all your queries.

elasticsearch.hosts: [""]
elasticsearch.ssl.certificateAuthorities: /Applications/Elasticsearch/config/certs/botlogsdevca.cer
elasticsearch.ssl.verificationMode: certificate "botlogs-dev" "4997536c-017a-417a-a27d-7660f3373e8f"

When this setting's value is true Kibana uses the hostname specified in the

setting. When the value of this setting is false, Kibana uses the hostname of the host

that connects to this Kibana instance.

#elasticsearch.preserveHost: true

Kibana uses an index in Elasticsearch to store saved searches, visualizations and

dashboards. Kibana creates a new index if the index doesn't already exist.

#kibana.index: ".kibana"

The default application to load.

#kibana.defaultAppId: "home"

If your Elasticsearch is protected with basic authentication, these settings provide

the username and password that the Kibana server uses to perform maintenance on the Kibana

index at startup. Your Kibana users still need to authenticate with Elasticsearch, which

is proxied through the Kibana server.

elasticsearch.username: "kibana"
elasticsearch.password: "XXXXX"

Enables SSL and paths to the PEM-format SSL certificate and SSL key files, respectively.

These settings enable SSL for outgoing requests from the Kibana server to the browser.

#server.ssl.enabled: false
#server.ssl.certificate: /path/to/your/server.crt
#server.ssl.key: /path/to/your/server.key

Optional settings that provide the paths to the PEM-format SSL certificate and key files.

These files validate that your Elasticsearch backend uses the same key files.

#elasticsearch.ssl.certificate: /path/to/your/client.crt
#elasticsearch.ssl.key: /path/to/your/client.key

Optional setting that enables you to specify a path to the PEM file for the certificate

authority for your Elasticsearch instance.

#elasticsearch.ssl.certificateAuthorities: [ "/path/to/your/CA.pem" ]

To disregard the validity of SSL certificates, change this setting's value to 'none'.

#elasticsearch.ssl.verificationMode: full

Time in milliseconds to wait for Elasticsearch to respond to pings. Defaults to the value of

the elasticsearch.requestTimeout setting.

#elasticsearch.pingTimeout: 1500

Time in milliseconds to wait for responses from the back end or Elasticsearch. This value

must be a positive integer.

#elasticsearch.requestTimeout: 30000

List of Kibana client-side headers to send to Elasticsearch. To send no client-side

headers, set this value to (an empty list).

#elasticsearch.requestHeadersWhitelist: [ authorization ]

Header names and values that are sent to Elasticsearch. Any custom headers cannot be overwritten

by client-side headers, regardless of the elasticsearch.requestHeadersWhitelist configuration.

#elasticsearch.customHeaders: {}

Time in milliseconds for Elasticsearch to wait for responses from shards. Set to 0 to disable.

#elasticsearch.shardTimeout: 30000

Time in milliseconds to wait for Elasticsearch at Kibana startup before retrying.

#elasticsearch.startupTimeout: 5000

Logs queries sent to Elasticsearch. Requires logging.verbose set to true.

#elasticsearch.logQueries: false

Specifies the path where Kibana creates the process ID file.

#pid.file: /var/run/

Enables you specify a file where Kibana stores log output.

logging.dest: /Applications/Elasticsearch/logs/kibana.log

Set the value of this setting to true to suppress all logging output.

#logging.silent: false

Set the value of this setting to true to suppress all logging output other than error messages.

#logging.quiet: false

Set the value of this setting to true to log all events, including system usage information

and all requests.

#logging.verbose: false

Set the interval in milliseconds to sample system and process performance

metrics. Minimum is 100ms. Defaults to 5000.

#ops.interval: 5000

Specifies locale to be used for all localizable strings, dates and number formats.

#i18n.locale: "en"

This is the recent log we have

[2023-01-10T01:49:02,370][INFO ][o.e.x.m.MlDailyMaintenanceService] [RPADEVWEBWS102] triggering scheduled [ML] maintenance tasks
[2023-01-10T01:49:02,386][INFO ][o.e.x.m.a.TransportDeleteExpiredDataAction] [RPADEVWEBWS102] Deleting expired data
[2023-01-10T01:49:02,386][INFO ][o.e.x.m.j.r.UnusedStatsRemover] [RPADEVWEBWS102] Successfully deleted [0] unused stats documents
[2023-01-10T01:49:02,386][INFO ][o.e.x.m.a.TransportDeleteExpiredDataAction] [RPADEVWEBWS102] Completed deletion of expired ML data
[2023-01-10T01:49:02,386][INFO ][o.e.x.m.MlDailyMaintenanceService] [RPADEVWEBWS102] Successfully completed [ML] maintenance task: triggerDeleteExpiredDataTask
[2023-01-10T08:00:07,416][DEBUG][o.e.a.a.i.c.AutoCreateAction] [RPADEVWEBWS102] Auto-creating index .monitoring-es-7-2023.01.10
[2023-01-10T08:00:07,416][INFO ][o.e.c.m.MetadataCreateIndexService] [RPADEVWEBWS102] [.monitoring-es-7-2023.01.10] creating index, cause [auto(bulk api)], templates [zeroreplicas, .monitoring-es], shards [1]/[0]
[2023-01-10T08:00:07,634][INFO ][o.e.c.r.a.AllocationService] [RPADEVWEBWS102] Cluster health status changed from [YELLOW] to [GREEN] (reason: [shards started [[.monitoring-es-7-2023.01.10][0]]]).
[2023-01-10T09:00:02,129][INFO ][o.e.x.m.e.l.LocalExporter] [RPADEVWEBWS102] cleaning up [1] old indices
[2023-01-10T09:00:02,129][INFO ][o.e.c.m.MetadataDeleteIndexService] [RPADEVWEBWS102] [.monitoring-es-7-2023.01.03/N1qcfDtZQjaivavp8MZ_pQ] deleting index
[2023-01-10T09:30:02,132][INFO ][o.e.x.s.SnapshotRetentionTask] [RPADEVWEBWS102] starting SLM retention snapshot cleanup task
[2023-01-10T09:30:02,132][INFO ][o.e.x.s.SnapshotRetentionTask] [RPADEVWEBWS102] there are no repositories to fetch, SLM retention snapshot cleanup task complete

Please format your code/logs/config using the </> button, or markdown style back ticks. It helps to make things easy to read which helps us help you :slight_smile:

I dont get what you mean can explain in brief please

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.