# 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:** [May 15, 2018, 8:26am 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:** 4

<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:** [May 15, 2018, 8:33am UTC](https://meta.discourse.org/t/domain-names-pointing-with-shared-aws-instance/87520/4 "2018-05-15T08:33:43Z")

</div>

I use this guide’s nginx configuration as a baseline for setting up discourse proxying right

> [@Add an offline page to display when Discourse is rebuilding or starting up](https://meta.discourse.org/t/adding-an-offline-page-when-rebuilding/45238):
>
> warning This guide is intended for advanced users, who are already using nginx outside the docker container. By following this guide you make your setup more complicated and will lose some speed benefits like HTTP2 if you’re not running Ubuntu 16.04 or later. Proceed with caution! When Discourse is rebuilding or starting up, your users will usually either see an error message from their browser… …or a not-so-nice 502 error message from Nginx: If you’re a perfectionist …

From there, You may be able to figure out how to add server blocks to nginx to ensure it points to your wordpress as well.

---

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