# Discourse not showing up at specified hostname

**URL:** https://meta.discourse.org/t/discourse-not-showing-up-at-specified-hostname/27969
**Category:** Self-hosting
**Created:** [April 26, 2015, 3:43am UTC](https://meta.discourse.org/t/discourse-not-showing-up-at-specified-hostname/27969 "2015-04-26T03:43:43Z")
**Posts on this page:** 1
**Showing post:** 2

<div class="post-metadata">

### Author: ![elberet](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/elberet/32/122404_2.png) [@elberet](https://meta.discourse.org/u/elberet)
#### Post date: [April 26, 2015, 3:54am UTC](https://meta.discourse.org/t/discourse-not-showing-up-at-specified-hostname/27969/2 "2015-04-26T03:54:40Z")

</div>

> [@PopsRocker](#):
>
> the default splash page when I set up a new website.

Is another webserver already running on your server? Keep in mind that only one process at a time can listen on the HTTP port. If you’re already running e.g. Apache with name-based virtual hosts, you’ll have to configure your existing Apache to act as a reverse proxy for Discourse and change Discourse’s config to expose itself on some unused port, ideally bound to `localhost`.

There are a few topics on meta covering this, e.g. [Run Discourse with or alongside existing Apache sites?](https://meta.discourse.org/t/run-discourse-with-or-alongside-existing-apache-sites/19514) and the howto [Running other websites on the same machine as Discourse](https://meta.discourse.org/t/running-other-websites-on-the-same-machine-as-discourse/17247) (which focuses on using `nginx` as the global frontend server).

Also, mind that Apache in its typical default configuration isn’t well suited to host Discourse. You absolutely should run with `mpm_event` and a large `AsyncRequestWorkerFactor` setting or Apache won’t handle Discourse’s many long-running polling connections very well.

---

_[View the full topic](https://meta.discourse.org/t/discourse-not-showing-up-at-specified-hostname/27969)._