today i couldnt access my ELK page, only getting 502 bad gateway from nginx. i havent changed anything in nginx, but after some research and testing i found out that it has something to do with 5601. i did a netstat -tapen | grep ":5601" to see who was listening on port 5601 and it didnt return anyt…

ELK returns 502 bad gateway, kibana4 not listening on port 5601

magnusbaeck (Magnus Bäck) June 1, 2015, 1:09pm 5

If you have replicas, drop them to regain disk space. Once you've fixed the disk space issue you can re-enable the replicas.

Topic		Replies	Views
Unable to connect to Kibana Kibana	18	4337	September 4, 2020
Kibana not starting Kibana	4	2045	July 6, 2017
Kibana doesn't bind to port 5601 Kibana	2	5424	July 6, 2017
Can't load kibana on 5601 Kibana	10	43335	July 6, 2017
Fail to connect to kibana, nginx issue? Kibana	2	668	July 6, 2017

Elasticsearch is a trademark of Elasticsearch BV, registered in the U.S. and in other countries
Trademarks
Terms
Privacy
Brand
Code of Conduct

Apache, Apache Lucene, Apache Hadoop, Hadoop, HDFS and the yellow elephant logo are trademarks of the Apache Software Foundation in the United States and/or other countries.

ELK returns 502 bad gateway, kibana4 not listening on port 5601

Related topics