# Elasticsearch blocks nginx port 80

**URL:** <https://discuss.elastic.co/t/elasticsearch-blocks-nginx-port-80/23718>\
**Category:** Elasticsearch\
**Created:** [May 29, 2015, 3:04am UTC](https://discuss.elastic.co/t/elasticsearch-blocks-nginx-port-80/23718 "2015-05-29T03:04:55Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![stp\_ra](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/stp_ra/32/42073_2.png) [@stp\_ra](https://discuss.elastic.co/u/stp_ra)\
**Post date:** [May 29, 2015, 3:04am UTC](https://discuss.elastic.co/t/elasticsearch-blocks-nginx-port-80/23718/1 "2015-05-29T03:04:55Z")

</div>

We are running into the following issue when we try to run nginx AFTER es is already up & running:

nginx: [emerg] bind() to 0.0.0.0:80 failed (98: Address already in use)

If we start nginx THEN es then everything works. How do I resolve this? We can't always choose the order of services started given we use supervisor.

thx!

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [July 6, 2017, 12:11am UTC](https://discuss.elastic.co/t/elasticsearch-blocks-nginx-port-80/23718/2 "2017-07-06T00:11:00Z")

</div>