Kibana with Nginx have intermittent Kibana did not load properly. Check the server output for more information errors

Elastic Stack Kibana
1

ES, Logstash, Kibana Version: 6.2.4

We are running Kibana behind nginx. Once we launch the page, we receive the dialog box to enter the credentials and post submitting, we are receiving the "kibana did not load properly" error message. And this error is intermittent. We have looked at Kibana logs and found nothing.

Also, we have x-pack basic license installed. And have defined the following settings in kibana.yml:
xpack.security.enabled: false
xpack.monitoring.report_stats: false
xpack.apm.ui.enabled: false

This sort of behavior is creating bad impression of the QOS provided.

I am sure that we missing some minor thing.

Any help in this would be appreciable.

2

Hi Myerasi,

I think you need to have xpack.security.enabled: true, in which case you'll be presented with the usual Kibana login screen.

See the docs here: Security settings in Kibana | Kibana Guide [8.11] | Elastic, specifically:

Do not set this to false .

Best,
Chris

3

HI Chris,

Thanks for the reply. I should have mentioned this earlier. We are using x-pack basic license and thus set it to false. Correct me if I am wrong.

4

Chris/someone,

Can you guys have a look at this issue please. We have launched our Elasticstack and it is ingesting production logs now. So, we would like to get this resolved ASAP to rule out the negative impression among the users.

Thanks,
Mahen

5

Any suggestion/direction on this would be of great help.

Thanks,
Mahen

6

Since you're running Kibana behind Nginx, you should check its (Nginx's) logs and see if there are any errors being logged when you get the "kibana did not load properly" message.
You should also try bypassing Nginx and working with your Kibana instance directly: that way you'll know if this has anything to do with Nginx at all.

7

Thanks for the response KBuev. The issue was with one of the LDAP server (which resides in a different data center) network connectivity. We had two LDAP authentications defined in nginx config. Deleting the config for the problematic LDAP server in the nginx configuration has fixed the issue.

8

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