# Site goes down at the same time every day in memory-constrained environment

**URL:** <https://meta.discourse.org/t/site-goes-down-at-the-same-time-every-day-in-memory-constrained-environment/76358>\
**Category:** Support\
**Created:** [2017年十二月18日 22:57 UTC](https://meta.discourse.org/t/site-goes-down-at-the-same-time-every-day-in-memory-constrained-environment/76358 "2017-12-18T22:57:22Z")\
**Posts on this page:** 1\
**Showing post:** 26

<div class="post-metadata">

**Author:** ![axfelix](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/axfelix/32/65166_2.png) [@axfelix](https://meta.discourse.org/u/axfelix)\
**Post date:** [2017年十二月20日 23:01 UTC](https://meta.discourse.org/t/site-goes-down-at-the-same-time-every-day-in-memory-constrained-environment/76358/26 "2017-12-20T23:01:15Z")

</div>

Yeah, still happening ☹

To everyone’s knowledge, _should_ a dropped-in `real_ip_header X-Forwarded-For;` in the discourse {} block of the container’s `nginx/conf.d/discourse.conf` suffice for IP forwarding, and therefore might something else be going wrong if that’s not working? And is it strange that the discourse app _has_ been able to detect requester IPs (e.g. for banning purposes) in the past with these same configs, if the container’s `/var/log/nginx/access.log` definitely can’t tell them apart now, no matter where I insert that config line?

---

_[View the full topic](https://meta.discourse.org/t/site-goes-down-at-the-same-time-every-day-in-memory-constrained-environment/76358)._