# Domain names pointing with shared AWS instance

**URL:** <https://meta.discourse.org/t/domain-names-pointing-with-shared-aws-instance/87520>\
**Category:** Self-hosting\
**Created:** [15 mei 2018 om 08:26 UTC](https://meta.discourse.org/t/domain-names-pointing-with-shared-aws-instance/87520 "2018-05-15T08:26:53Z")\
**Posts on this page:** 1\
**Showing post:** 8

<div class="post-metadata">

**Author:** ![itsbhanusharma](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/itsbhanusharma/32/180717_2.png) [@itsbhanusharma](https://meta.discourse.org/u/itsbhanusharma)\
**Post date:** [15 mei 2018 om 14:01 UTC](https://meta.discourse.org/t/domain-names-pointing-with-shared-aws-instance/87520/8 "2018-05-15T14:01:53Z")

</div>

> [@jwtan](#):
>
> I can’t seem to get Wordpress working in nginx.

In my setup, both, wordpress and discourse live under the same nginx happily.

> [@jwtan](#):
>
> Can I have both nginx and httpd running at the same time?

If you’re technically sound, you may want to run httpd on port 81 and then internally proxy it from nginx but I wonder what performance benifit would it bring. However, what kind of issue you’re having may help you find your solution better.

> [@jwtan](#):
>
> While nginx listen to Discourse traffic and httpd listen to Wordpress site traffic.

That is totally doable but why do you want to add another variable in the form of httpd when nginx can happily handle both discourse and wordpress at the same time.

---

_[View the full topic](https://meta.discourse.org/t/domain-names-pointing-with-shared-aws-instance/87520)._
