# Elastic search will not bind to port 80 (no web server is running)

**URL:** <https://discuss.elastic.co/t/elastic-search-will-not-bind-to-port-80-no-web-server-is-running/284658>\
**Category:** Elasticsearch\
**Created:** [September 20, 2021, 7:59pm UTC](https://discuss.elastic.co/t/elastic-search-will-not-bind-to-port-80-no-web-server-is-running/284658 "2021-09-20T19:59:31Z")\
**Posts on this page:** 8\
**Page:** 1

<div class="post-metadata">

**Author:** ![lsnwebmaster](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/lsnwebmaster/32/94814_2.png) [@lsnwebmaster](https://discuss.elastic.co/u/lsnwebmaster)\
**Post date:** [September 20, 2021, 7:59pm UTC](https://discuss.elastic.co/t/elastic-search-will-not-bind-to-port-80-no-web-server-is-running/284658/1 "2021-09-20T19:59:31Z")

</div>

I am trying elasticsearch as a standalone search for WordPress. I created a new server on Ubuntu 20.04 LTS with nothing but elasticsearch. I did nothing to the config file, accepting all defaults. It started fine on port 9200. The WordPress plugin needs port 80 (silly thing), so I modifed the yml file to use http.port = 80. There is _no_ web server running on port 80. Netstat proves it. Yet elasticsearch fails to start with bind permission denied. It starts fine on port 9200.

Why? What can be done?

---

<div class="post-metadata">

**Author:** ![dadoonet](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/dadoonet/32/137187_2.png) [@dadoonet](https://discuss.elastic.co/u/dadoonet)\
**Post date:** [September 20, 2021, 8:17pm UTC](https://discuss.elastic.co/t/elastic-search-will-not-bind-to-port-80-no-web-server-is-running/284658/2 "2021-09-20T20:17:17Z")

</div>

Welcome!

I think that on some linux machine you need some super user powers to run a service on a port like 80.

Are you sure that you can't configure the plugin to use the 9200 port?

---

<div class="post-metadata">

**Author:** ![lsnwebmaster](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/lsnwebmaster/32/94814_2.png) [@lsnwebmaster](https://discuss.elastic.co/u/lsnwebmaster)\
**Post date:** [September 22, 2021, 3:22pm UTC](https://discuss.elastic.co/t/elastic-search-will-not-bind-to-port-80-no-web-server-is-running/284658/3 "2021-09-22T15:22:30Z")

</div>

I have full root access but it just will not run on port 80. No idea why.

---

<div class="post-metadata">

**Author:** ![zx8086](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/zx8086/32/94917_2.png) [@zx8086](https://discuss.elastic.co/u/zx8086)\
**Post date:** [September 22, 2021, 3:59pm UTC](https://discuss.elastic.co/t/elastic-search-will-not-bind-to-port-80-no-web-server-is-running/284658/4 "2021-09-22T15:59:39Z")

</div>

What address are you using to bind that port ? 0.0.0.0:80 or 127.0.0.1:80 or something else like 192.168.0.1:80 as an example ?

Also when you do an nmap or netstat on the machine, so you see anything binded to that port ?

---

<div class="post-metadata">

**Author:** ![lsnwebmaster](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/lsnwebmaster/32/94814_2.png) [@lsnwebmaster](https://discuss.elastic.co/u/lsnwebmaster)\
**Post date:** [September 22, 2021, 6:13pm UTC](https://discuss.elastic.co/t/elastic-search-will-not-bind-to-port-80-no-web-server-is-running/284658/5 "2021-09-22T18:13:28Z")

</div>

I already did the obvious, using netstat to ensure nothing is running on port 80. Besides, this is a brand new VPS and web server software is not even installed at all. At this point I am just dealing with using port 9200 and do not have the time to spend on this debugging.

---

<div class="post-metadata">

**Author:** ![zx8086](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/zx8086/32/94917_2.png) [@zx8086](https://discuss.elastic.co/u/zx8086)\
**Post date:** [September 22, 2021, 6:36pm UTC](https://discuss.elastic.co/t/elastic-search-will-not-bind-to-port-80-no-web-server-is-running/284658/6 "2021-09-22T18:36:51Z")

</div>

Maybe sharing your Elasticsearch.yml file in the meanwhile might indicate where the problem is?

it's either a network binding issue or a configuration issue. If it works on the default configuration, that rules out the software at least.

---

<div class="post-metadata">

**Author:** ![stephenb](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/stephenb/32/40856_2.png) [@stephenb](https://discuss.elastic.co/u/stephenb)\
**Post date:** [September 22, 2021, 7:30pm UTC](https://discuss.elastic.co/t/elastic-search-will-not-bind-to-port-80-no-web-server-is-running/284658/7 "2021-09-22T19:30:55Z")

</div>

@lsnwebmaster Welcome to the community.

Exactly How are you starting Elasticsearch? What Command? systemctl?

---

<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:** [October 20, 2021, 7:31pm UTC](https://discuss.elastic.co/t/elastic-search-will-not-bind-to-port-80-no-web-server-is-running/284658/8 "2021-10-20T19:31:06Z")

</div>

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