502 Bad Gateway nginx/1.10.2 Dashboard Error

Elastic Stack Kibana
1

Hello,

Could you please help to fix 502 Bad Gateway nginx/1.10.2 Dashboard Error.

I can able to login with credentials in kibana once login the page displayed like 502 Bad Gateway nginx/1.10.2 Dashboard Error.

Thanks,

Vijay S

2

additional information,

There is no Cluster its standalone ELK server with enough disk space.

Attached Screen shot of Nginx Error logs,

Nginx Error Logs.JPG1350×129 60.9 KB

3

There could be a lot of reasons for this.

  1. Start by checking the Kibana logs to make sure startup was successful. If you've recently installed a plugin in Kibana or changed any settings that control whether a plugin or feature is enabled, startup will take an extra amount of time for the browser resources to be re-bundled (this is called re-optimization)

  2. Make sure Kibana is actually up and running by trying to connect to it without going through the proxy. A simple curl command to localhost run from the Kibana host might be the easiest way to verify:

$ curl -i http://localhost:5601
HTTP/1.1 200 OK
kbn-name: kibana
kbn-version: 5.2.0
cache-control: no-cache
content-type: text/html; charset=utf-8
content-length: 217
accept-ranges: bytes
Date: Mon, 13 Feb 2017 22:37:40 GMT
Connection: keep-alive
...

  1. Make sure the host name for Kibana is configured correctly in the nginx proxy section.

  2. Make sure the proxy host is actually able to see Kibana on the network.

If you've verified step 1 and 2, the problem really comes down to an issue with the proxy configuration.

4

Thanks Tim,

Step 2:
I executed command the below output

curl -i http://localhost:5601
curl: (7) Failed connect to localhost:5601; Connection refused

5

Check the logs to see if there is an error revealing why Kibana couldn't start up. This is your best bet. It could be due to an incorrect config setting, and the log file will tell you.

If the log file doesn't show anything wrong, check the kibana.yml and see if there are server.host, server.port, or server.ssl settings which would mean that you need to use a different hostname other than localhost, a different port, or the HTTPS protocol to connect. You can also try netstat -l to figure out if there is an open TCP connection created by Kibana.

6

Kibana configuration looks good kibana.yml.

Iam unable to see those logs in kibana logs path but its configured in the path /var/log/kibana

seems to be logs are not generating in the above said path.

I tried netstat -l to see any open connection created by kibana on its own but its not.

Iam really struck here can you please guide me to proceed further on troubleshooting towards the fix.

~VJ

7

It sounds like Kibana was just never started.

What method are you using to start it? See https://www.elastic.co/guide/en/kibana/current/rpm.html

8

No kibana was running without any issues.

[root@elk-500g-ssd conf.d]# service kibana4 status
Redirecting to /bin/systemctl status kibana4.service
● kibana4.service
Loaded: loaded (/etc/systemd/system/kibana4.service; enabled; vendor preset: disabled)
Active: active (running) since Tue 2017-02-14 18:35:03 CST; 19h ago
Main PID: 17042 (node)
CGroup: /system.slice/kibana4.service
└─17042 /opt/kibana/bin/../node/bin/node /opt/kibana/bin/../src/bin/kibana.js

Feb 15 14:21:58 elk-500g-ssd kibana4[17042]: {"@timestamp":"2017-02-15T20:21:58.493Z","level":"info","message":"Elasticsearch is still initializing the kib...oduction"}
Feb 15 14:22:01 elk-500g-ssd kibana4[17042]: {"@timestamp":"2017-02-15T20:22:01.007Z","level":"info","message":"Elasticsearch is still initializing the kib...oduction"}
Feb 15 14:22:03 elk-500g-ssd kibana4[17042]: {"@timestamp":"2017-02-15T20:22:03.511Z","level":"info","message":"Elasticsearch is still initializing the kib...oduction"}
Feb 15 14:22:06 elk-500g-ssd kibana4[17042]: {"@timestamp":"2017-02-15T20:22:06.016Z","level":"info","message":"Elasticsearch is still initializing the kib...oduction"}
Feb 15 14:22:08 elk-500g-ssd kibana4[17042]: {"@timestamp":"2017-02-15T20:22:08.521Z","level":"info","message":"Elasticsearch is still initializing the kib...oduction"}
Feb 15 14:22:11 elk-500g-ssd kibana4[17042]: {"@timestamp":"2017-02-15T20:22:11.026Z","level":"info","message":"Elasticsearch is still initializing the kib...oduction"}
Feb 15 14:22:13 elk-500g-ssd kibana4[17042]: {"@timestamp":"2017-02-15T20:22:13.530Z","level":"info","message":"Elasticsearch is still initializing the kib...oduction"}
Feb 15 14:22:16 elk-500g-ssd kibana4[17042]: {"@timestamp":"2017-02-15T20:22:16.035Z","level":"info","message":"Elasticsearch is still initializing the kib...oduction"}
Feb 15 14:22:18 elk-500g-ssd kibana4[17042]: {"@timestamp":"2017-02-15T20:22:18.539Z","level":"info","message":"Elasticsearch is still initializing the kib...oduction"}
Feb 15 14:22:21 elk-500g-ssd kibana4[17042]: {"@timestamp":"2017-02-15T20:22:21.044Z","level":"info","message":"Elasticsearch is still initializing the kib...oduction"}
Hint: Some lines were ellipsized, use -l to show in full.

9

Is there any update still we have same issue.

please help!

10

Can you provide your kibana.yml and nginx config?

11

Another thing, try to set up the system without the proxy in place first, to eliminate that complexity. Once Kibana can be confirmed working without the proxy, then add the proxy to the system.

12

Thanks. I will try kibana with out proxy and update you.

1 Like
13

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