# Port already in use, what to do?

**URL:** <https://meta.discourse.org/t/port-already-in-use-what-to-do/27954>\
**Category:** Self-hosting\
**Created:** [Avril 25, 2015, 5:56 UTC](https://meta.discourse.org/t/port-already-in-use-what-to-do/27954 "2015-04-25T17:56:10Z")\
**Posts on this page:** 1\
**Showing post:** 20

<div class="post-metadata">

**Author:** ![chamunks](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/chamunks/32/73257_2.png) [@chamunks](https://meta.discourse.org/u/chamunks)\
**Post date:** [Mai 29, 2017, 6:00 UTC](https://meta.discourse.org/t/port-already-in-use-what-to-do/27954/20 "2017-05-29T18:00:43Z")

</div>

> [@codinghorror](#):
>
> This error comes up often enough that I think our startup scripts should offer guidance for it. I am getting really sick of reading the “oh no, port 80 is in use” install topics.

Would this be something that might happen at some point? I’m trying to get Discourse to bind to an alt port (9000?) like I recall vaguely that it used to. It seems that there’s always been some ambiguity on how to bind this to other IP’s on the host or even alternate ports.

---

_[View the full topic](https://meta.discourse.org/t/port-already-in-use-what-to-do/27954)._