# Como identificar falha do discourse upstream dentro do container resultando em 502 Bad Gateway

**URL:** https://meta.discourse.org/t/how-to-track-down-failure-of-discourse-upstream-inside-container-resulting-in-502-bad-gateway/256099
**Category:** Self-hosting
**Created:** [23 Fevereiro , 2023 18:54 UTC](https://meta.discourse.org/t/how-to-track-down-failure-of-discourse-upstream-inside-container-resulting-in-502-bad-gateway/256099 "2023-02-23T18:54:30Z")
**Posts on this page:** 1
**Showing post:** 3

<div class="post-metadata">

### Author: ![david](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/david/32/157490_2.png) [@david](https://meta.discourse.org/u/david)
#### Post date: [23 Fevereiro , 2023 19:22 UTC](https://meta.discourse.org/t/how-to-track-down-failure-of-discourse-upstream-inside-container-resulting-in-502-bad-gateway/256099/3 "2023-02-23T19:22:03Z")

</div>

Dado o momento, é muito provável que isso esteja relacionado a uma alteração no data-explorer que causou alguns problemas. Nós a revertemos, então se você tentar a reconstrução novamente, ela deve funcionar melhor

> [@Data explorer taking instance down on rebuild](https://meta.discourse.org/t/data-explorer-taking-instance-down-on-rebuild/256078/15?u=david):
>
> I see that has been reverted: I’ve been able to successfully rebuild now - thank you for getting onto that so promptly!

---

_[View the full topic](https://meta.discourse.org/t/how-to-track-down-failure-of-discourse-upstream-inside-container-resulting-in-502-bad-gateway/256099)._