docker-elk: Kibana server is not ready yet

Client: Docker Engine - Community
 Version:           20.10.12
 API version:       1.41
 Go version:        go1.16.12
 Git commit:        e91ed57
 Built:             Mon Dec 13 11:45:41 2021
 OS/Arch:           linux/amd64
 Context:           default
 Experimental:      true

Server: Docker Engine - Community
 Engine:
  Version:          20.10.12
  API version:      1.41 (minimum version 1.12)
  Go version:       go1.16.12
  Git commit:       459d0df
  Built:            Mon Dec 13 11:44:05 2021
  OS/Arch:          linux/amd64
  Experimental:     false
 containerd:
  Version:          1.4.13
  GitCommit:        9cc61520f4cd876b86e77edfeb88fbcd536d1f9d
 runc:
  Version:          1.0.3
  GitCommit:        v1.0.3-0-gf46b6ba
 docker-init:
  Version:          0.19.0
  GitCommit:        de40ad0
docker-compose version 1.29.2, build 5becea4c
docker-py version: 5.0.0
CPython version: 3.7.10
OpenSSL version: OpenSSL 1.1.0l  10 Sep 2019

Followed the instructions exactly, but just got the error Kibana server is not ready yet. At the same time, the following prompt “Configuration missing” appears in the lower right corner

server.publicBaseUrl is missing and should be configured when running in a production environment. Some features may not behave correctly. See the documentation.”
Add server.publicBaseUrl="xxx" to kibana/config/kibana.yml, there is no prompt in the lower right corner, but the error Kibana server is not ready yet is still prompted。
# docker logs elk_kibana_1
[2022-03-10T10:00:56.888+00:00][ERROR][elasticsearch-service] Unable to retrieve version information from Elasticsearch nodes. security_exception: [security_exception] Reason: unable to authenticate user [kibana_system] for REST request [/_nodes?filter_path=nodes.*.version%2Cnodes.*.http.publish_address%2Cnodes.*.ip]

edit: formatting (@antoineco)

About this issue

  • Original URL
  • State: closed
  • Created 2 years ago
  • Comments: 16

Most upvoted comments

@fictioner to me it seems like the stack was already started in the past, with another password, and that password is still persisted inside Elasticsearch’s data volume (removing the repository is not enough, you also need to remove Docker volumes, as indicated in the README).

The simplest solution for you is to run docker-compose down -v and try again.