# Blank pages, 500 errors and no logs

**URL:** https://meta.discourse.org/t/blank-pages-500-errors-and-no-logs/96413
**Category:** Support
**Created:** [9월 5, 2018, 1:35오후 UTC](https://meta.discourse.org/t/blank-pages-500-errors-and-no-logs/96413 "2018-09-05T13:35:09Z")
**Posts on this page:** 1
**Showing post:** 6

<div class="post-metadata">

### Author: ![gerhard](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/gerhard/32/119479_2.png) [@gerhard](https://meta.discourse.org/u/gerhard)
#### Post date: [9월 5, 2018, 2:15오후 UTC](https://meta.discourse.org/t/blank-pages-500-errors-and-no-logs/96413/6 "2018-09-05T14:15:29Z")

</div>

There’s a nginx server running on port 80 inside the container. Your reverse proxy would have to do all the stuff nginx is doing since you are connecting to port 3000. I don’t recommend doing that. There’s too much that can go wrong and you are experiencing that right now.

My recommendation:

1. Read [Run other websites on the same machine as Discourse](https://meta.discourse.org/t/running-other-websites-on-the-same-machine-as-discourse/17247)

2. Expose the container’s nginx on a different port by editing your `app.yml`. E.g.:

3. Configure your reverse proxy to connect to the container via the port exposed in `app.yml` (e.g. 8080) and make sure your reverse proxy sends the required headers. See [Run other websites on the same machine as Discourse](https://meta.discourse.org/t/running-other-websites-on-the-same-machine-as-discourse/17247) for more information on that.

---

_[View the full topic](https://meta.discourse.org/t/blank-pages-500-errors-and-no-logs/96413)._