# Bursts of 502 Service Unavailable, pointers to debug

**URL:** https://meta.discourse.org/t/bursts-of-502-service-unavailable-pointers-to-debug/80571
**Category:** Self-hosting
**Created:** [February 14, 2018, 9:10pm UTC](https://meta.discourse.org/t/bursts-of-502-service-unavailable-pointers-to-debug/80571 "2018-02-14T21:10:12Z")
**Posts on this page:** 1
**Showing post:** 7

<div class="post-metadata">

### Author: ![mpalmer](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/mpalmer/32/45740_2.png) [@mpalmer](https://meta.discourse.org/u/mpalmer)
#### Post date: [February 17, 2018, 1:03am UTC](https://meta.discourse.org/t/bursts-of-502-service-unavailable-pointers-to-debug/80571/7 "2018-02-17T01:03:28Z")

</div>

I can’t think of anything I’ve written that covers tracing a request through the layers. I’d suggest starting with @Sam’s topic on [where the wild logs are](https://meta.discourse.org/t/where-are-all-the-discourse-logs/58022) and working from the outside in – find a failing request in the logs for the outermost proxy (either nginx in the container, or the host’s nginx/apache if it’s setup that way), then find the corresponding entry at the next hop (unicorn, or container nginx), and so on.

---

_[View the full topic](https://meta.discourse.org/t/bursts-of-502-service-unavailable-pointers-to-debug/80571)._