Error: Not Found - commons.bundle.js

Elastic Stack Kibana
1

Hey

I have set up elaticsearch+kibana+logstash+filebeat on Ubuntu 18.04.3 (using nginx as proxy_pass) with OpenJDK11.

Everything with Kabana seems to work as expected except the "Discover" tab.
When clicking "Discover" button in the left hand toolbar I get the following error:

kibana1

kibana3
kibana3799×354 22.3 KB

Any tips about this error would be great. Thank you

2

Hi @jonare77, what version of Elasticsearch, Kibana and Logstash are you using?
Thanks.

3

Its all 7.5.2 with OpenJDK 11.

4

Thanks, those are supported versions, so it should work.

@tylersmalley any clue why we would get this error?

5

Hello,

Did you get a solution? I have a similar challenge and I wonder how to go about it.

6

No solution, had no clue how to get it fixed either. So I went with docker and fired up ELK there.
I would be nice to get It working, maybe I will try a new reinstall and see.

7

Hi @jonare77

Sorry for delay, I setup nginx for Kibana and was not able to reproduce.
Can you share your configuration for nginx? I can try to reproduce what you have. Thanks.

8

server {
listen 443;
ssl on;
ssl_certificate /etc/nginx/ssl/server.crt;
ssl_certificate_key /etc/nginx/ssl/server.key;

server_name [name];

auth_basic "Restricted Access";
auth_basic_user_file /etc/nginx/htpasswd.users;

location / {
    proxy_pass http://localhost:5601;
    proxy_http_version 1.1;
    proxy_set_header Upgrade $http_upgrade;
    proxy_set_header Connection 'upgrade';
    proxy_set_header Host $host;
    proxy_cache_bypass $http_upgrade;
}

}

9

Thanks @jonare77, I was not able to reproduce the error described above, I am thinking it has more to do with the data than the nginx setup. I was going to recommend you file an issue and found you did already here: https://github.com/elastic/kibana/issues/56375 -- so I guess the issue has to do with an empty index pattern on discover and changing that index pattern from default fixed it? Hopefully that was it, looks like the issue will get routed to the right team for closer analysis. If there is anything else, please let us know. Thanks!

@Musa - check out the issue linked above and see if it also fixes what you are seeing.

10

It also been reported on Github, https://github.com/elastic/kibana/issues/56375

11

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