# 502: Bad Gateway after web update

**URL:** <https://meta.discourse.org/t/502-bad-gateway-after-web-update/136221>\
**Category:** Product Support\
**Created:** [December 16, 2019, 3:13pm UTC](https://meta.discourse.org/t/502-bad-gateway-after-web-update/136221 "2019-12-16T15:13:51Z")\
**Posts on this page:** 1\
**Showing post:** 1

<div class="post-metadata">

**Author:** ![chuckh\_nnyln](https://avatars.discourse-cdn.com/v4/letter/c/ce7236/32.png) [@chuckh\_nnyln](https://meta.discourse.org/u/chuckh_nnyln)\
**Post date:** [December 16, 2019, 3:13pm UTC](https://meta.discourse.org/t/502-bad-gateway-after-web-update/136221/1 "2019-12-16T15:13:52Z")

</div>

So ran updates this morning from the web interface and during the update of Discourse (not docker) it said that the update failed. I look at the log display but it really doesn’t mean much to me. I then ssh in and ran ‘cd /var/discourse’ then ‘git pull’ and ‘./launcher rebuild app’. After everything completed the site resolves with a 502 Bad Gateway. ([http://forums.nyheritage.org/](http://forums.nyheritage.org/) btw). I’ve read through the similar topics but didn’t find anything that seemed to suggest a course of action on this.

I’d attach the Discourse Doctor output expect new users can’t upload documents and I can’t quote it because new users can only post 2 links. So the link to the server location is here: [http://forums.nyheritage.org/NjliZDRlYzE3NTZlZTU0.txt](http://forums.nyheritage.org/NjliZDRlYzE3NTZlZTU0.txt) Hopefully that works.

Any suggestions on further things to try would be appreciated! Thanks!

---

_[View the full topic](https://meta.discourse.org/t/502-bad-gateway-after-web-update/136221)._