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/ 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 Hopefully that works. Any suggestions on further things to try would be appreciated! Thanks!

A fix is now available. If your server is currently returning 502 errors, you will need to connect via ssh and run cd /var/discourse ./launcher rebuild app For anyone who hasn’t updated yet, it is now safe to hit update in docker manager

502 Bad Gateway for me too. Yikes.

Same issue here, 502 after running docker update

Seems to be the case for me as well. Fighting all morning trying to get a fix. Edit: Whats strange is if you stop the container you can get to the site, its just extremely slow. (cloudflare cache) Another helpful error: /var/www/discourse/vendor/bundle/ruby/2.6.0/gems/unicorn-5.5.1/lib/unicorn/socket_helper.rb:165:in `bind': Cannot assign requested address - bind(2) for [::1]:3000 (Errno::EADDRNOTAVAIL) /var/discourse# docker ps --all CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES ae2dac939415 local_discourse/app "/sbin/boot" 7 minutes ago Exited (5) 2 minutes ago app

Similar problem here: I’ve rebuild the app (./launcher rebuild app) and now the site is returning this error. I was trying to add a new container and setup a multi forum with nginx proxy but something goes wrong, when I’ve reverted the changes to the original ones the forum stopped working (… yes, I’m sure the settings have been correctly restored). :frowning:

Same issue as well, ran the Docker update and then tried to apply the discourse updates only to get the 502 error. The upgrade implied it failed and I was seeing a 500 error, I went ahead and did a rebuild (./launcher rebuild app) and now I’m seeing the 502.

We’ve identified the problem and are building a fix.

Thank you, will you notify the update when it will be ready? :slight_smile:

Of course, we’ll post in this topic when the fix is ready.

Same issue here. So how do we implement the fix without the web update button running?

502: Bad Gateway after web update

Product Support

glynhudson (Glynhudson) December 16, 2019, 4:54pm 18

Fixed! Nice work

Topic		Replies	Views
502 Bad Gateway after Update Product Support	3	969	December 22, 2018
How to track down failure of discourse upstream inside container resulting in 502 Bad Gateway Self-hosting	7	1323	April 23, 2023
Site down: 502 Bad Gateway - after update Self-hosting	2	1246	September 24, 2018
502 Bad Gateway - Newbie help needed Self-hosting	4	641	November 15, 2018
502 Bad Gateway after upgrade to 2.7.0beta2 Self-hosting	0	715	January 23, 2021

502: Bad Gateway after web update

Related topics