# 502 error on nginx

**URL:** <https://meta.discourse.org/t/502-error-on-nginx/160592>\
**Category:** Self-hosting\
**Created:** [August 12, 2020, 6:05am UTC](https://meta.discourse.org/t/502-error-on-nginx/160592 "2020-08-12T06:05:04Z")\
**Posts on this page:** 1\
**Showing post:** 3

<div class="post-metadata">

**Author:** ![elopio](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/elopio/32/218413_2.png) [@elopio](https://meta.discourse.org/u/elopio)\
**Post date:** [August 12, 2020, 12:38pm UTC](https://meta.discourse.org/t/502-error-on-nginx/160592/3 "2020-08-12T12:38:39Z")

</div>

Thanks @itsbhanusharma.

I’ve run `./launcher restart app` and monitored the load with top, and it’s well under 10%.

I think the CPU should be enough to handle the load:

```plaintext
$ cat /proc/cpuinfo | grep 'name' | uniq
model name : Intel(R) Xeon(R) CPU E5-1650 v3 @ 3.50GHz
$ cat /proc/cpuinfo | grep process | wc -l
4

```

Is there a better way to debug the start up of the container?  
Any other ideas?

---

_[View the full topic](https://meta.discourse.org/t/502-error-on-nginx/160592)._