If you encountered a 502 error getting to the forums over the past 12-ish hours, that was me.
I had the hosting company doing a BIOS upgrade on the web server last night, which required a reboot, and it appears that someone hit the CoG forum URL at exactly the right instance at the tail end of the reboot, just before the Discourse docker container was fully back online. The 502 bad gateway response was cached, and Varnish has been serving that since last night. It would have eventually fixed itself as the cache expired, but I’ve killed & restarted Varnish and that appears to have fixed the problem.
It’s no problem! Didn’t mean to make it sound like someone was to blame or anything like that—it’s just a consequence of upgrading in the middle of production rather than doing things the “right” way.
The “right” way would be to pick an off-hours outage window, alert everybody about the outage at intervals starting 48 hrs prior to the picked time, switch the site over to a maintenance/outage “we’ll be right back” page, do the upgrade, and then cut back live.
Heyyyyyyyyyyyyy I did it again. Apologies for anyone who saw a weird-ass error for a bit this evening.
The good news, though, is that now everything in the entire web stack now uses unix sockets instead of loopback ports! Which…okay, yeah, that sounds a lot less impressive because it’s just kind of an under-the-hood change but it was neat figuring out how to make it work!
Yes, I left something out of the config and it was causing a lot of really weird unintended redirects. Should be OK as of yesterday evening. @Nabiki, if you’re still seeing oddness, please do let me know.