# Kibana server is not ready yet status **URL:** \ **Category:** Elastic Training\ **Created:** [July 1, 2025, 5:07pm UTC](https://discuss.elastic.co/t/kibana-server-is-not-ready-yet-status/379685 "2025-07-01T17:07:00Z")\ **Posts on this page:** 9\ **Page:** 1
**Author:** ![rootkai94](https://avatars.discourse-cdn.com/v4/letter/r/9d8465/32.png) [@rootkai94](https://discuss.elastic.co/u/rootkai94)\ **Post date:** [July 1, 2025, 5:07pm UTC](https://discuss.elastic.co/t/kibana-server-is-not-ready-yet-status/379685/1 "2025-07-01T17:07:00Z")
Hello, I recently enrolled into the Elastic Security SIEM on-demand course and i started the course successfully. But while i reached module 3, i am unable to access Kibana dashboard from Strigo VM's. I keep getting the error server is not ready yet. I have done the following to troubleshoot. 1. Restarted the workspaces 2. Sent a message to Strigo and I was told to contact the course providers. 3. Followed troubleshooting techniques specified in [Kibana server is not ready yet](https://discuss.elastic.co/t/kibana-server-is-not-ready-yet/241217) 4. When I did a curl, I get a message stating upgrade the browser. My browser is up to date and I still get these errors. I have tried using chrome, firefox, edge. Nothing works, all fails. None of the above worked. I would appreciate a quick response as I would like to proceed with the training. ![Screenshot 2025-07-01 at 20.21.54](https://us1.discourse-cdn.com/elastic/original/3X/2/c/2c4b3c6aa7fe2aa86a19dc23111feb4eb2ed7339.png) ---
**Author:** ![Tortoise](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/tortoise/32/147587_2.png) [@Tortoise](https://discuss.elastic.co/u/Tortoise)\ **Post date:** [July 2, 2025, 4:41am UTC](https://discuss.elastic.co/t/kibana-server-is-not-ready-yet-status/379685/2 "2025-07-02T04:41:13Z")
Hello @rootkai94 Welcome to the community. As you have already tried to restart the terminal workspace , after you login to the terminal could you please execute below command `docker ps` What is the status of the elasticsearch/kibana container (is it healthy) ? If not try restarting the container which are not healthy. Are all the containers healthy & you are still receiving error while accessing kibana? Thanks!! ---
**Author:** ![rootkai94](https://avatars.discourse-cdn.com/v4/letter/r/9d8465/32.png) [@rootkai94](https://discuss.elastic.co/u/rootkai94)\ **Post date:** [July 3, 2025, 5:34am UTC](https://discuss.elastic.co/t/kibana-server-is-not-ready-yet-status/379685/3 "2025-07-03T05:34:43Z")
> [@Tortoise](#): > > docker ps Hello @Tortoise, Thanks for the information, when I tried running docker ps, I get the response that docker command is not found. Since this is a lab environment hosted in strigo, I think it is directly hosted on the server without a docker. When I run systemctl directly on the server it shows service running. ![image](https://us1.discourse-cdn.com/elastic/original/3X/6/5/65c03f2fa3b30a4d6d46aaf4801e72e65ff38933.png) Thanks ---
**Author:** ![rootkai94](https://avatars.discourse-cdn.com/v4/letter/r/9d8465/32.png) [@rootkai94](https://discuss.elastic.co/u/rootkai94)\ **Post date:** [July 3, 2025, 7:22am UTC](https://discuss.elastic.co/t/kibana-server-is-not-ready-yet-status/379685/4 "2025-07-03T07:22:56Z")
Hello Community, After a lot of troubleshooting i found that the license was expired and it had nothing to do with CSP or browser upgrade since it worked for me from the start of registration and spinup of Strigo instance. Turns out license expired on the 30th of June 2025. Command to check for license ```auto curl -k -u elastic http://localhost:9200/_license ``` Command to renew trial license ```auto curl -X POST -u elastic http://localhost:9200/_license/start_trial?acknowledge=true ``` This fixed my issue. I want to put it here incase anyone else faces this issue. I think elastic should provide license that does not expire in the middle of the course timeline. ---
**Author:** ![Training](https://avatars.discourse-cdn.com/v4/letter/t/b5e925/32.png) [@Training](https://discuss.elastic.co/u/Training)\ **Post date:** [July 3, 2025, 1:35pm UTC](https://discuss.elastic.co/t/kibana-server-is-not-ready-yet-status/379685/5 "2025-07-03T13:35:11Z")
> [@rootkai94](#): > > with CSP or browser upgrade since it worked for me from the start of registration and spinup of Strigo instance. Turns out license expired on the 30th of June 2025. I just get an empty reply from server. ---
**Author:** ![rootkai94](https://avatars.discourse-cdn.com/v4/letter/r/9d8465/32.png) [@rootkai94](https://discuss.elastic.co/u/rootkai94)\ **Post date:** [July 3, 2025, 5:20pm UTC](https://discuss.elastic.co/t/kibana-server-is-not-ready-yet-status/379685/6 "2025-07-03T17:20:46Z")
> [@rootkai94](#): > > r me from the start of registration and spinup of Str Hello, Did you run the command to check for the license? It should not return an empty response since every instance will have a license embedded on creation. Can you double check the command. You can directly copy paste the first command in the solution I identified to check if you get a response. You could upload a screenshot of the message you get when you check your license status. ---
**Author:** ![Training](https://avatars.discourse-cdn.com/v4/letter/t/b5e925/32.png) [@Training](https://discuss.elastic.co/u/Training)\ **Post date:** [July 3, 2025, 6:20pm UTC](https://discuss.elastic.co/t/kibana-server-is-not-ready-yet-status/379685/7 "2025-07-03T18:20:20Z")
> [@rootkai94](#): > > `curl -k -u elastic http://localhost:9200/_license` Here's a screenshot: ![image](https://us1.discourse-cdn.com/elastic/original/3X/7/8/7817ec8fb233bd7ec425da0ec52c89f32ddc8717.png) ---
**Author:** ![RainTown](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/raintown/32/140206_2.png) [@RainTown](https://discuss.elastic.co/u/RainTown)\ **Post date:** [July 3, 2025, 7:17pm UTC](https://discuss.elastic.co/t/kibana-server-is-not-ready-yet-status/379685/8 "2025-07-03T19:17:22Z")
`empty reply from server` is what you get if you send HTTP to connections expecting HTTPS I don't know these training environments at all but ... might help. ---
**Author:** ![Training](https://avatars.discourse-cdn.com/v4/letter/t/b5e925/32.png) [@Training](https://discuss.elastic.co/u/Training)\ **Post date:** [July 3, 2025, 7:32pm UTC](https://discuss.elastic.co/t/kibana-server-is-not-ready-yet-status/379685/9 "2025-07-03T19:32:02Z")
> `empty reply from server` is what you get if you send HTTP to connections expecting HTTPS That fixed the issue, thank you. Here are the https versions for easy copying for anyone reading later: ```auto curl -k -u elastic https://localhost:9200/_license ``` ```auto curl -k -X POST -u elastic https://localhost:9200/_license/start_trial?acknowledge=true ```