How to track down failure of discourse upstream inside container resulting in 502 Bad Gateway

Given the timing, this is most likely related to a data-explorer change which caused some issues. We’ve now reverted it, so if you try the rebuild again it should work better

3 Likes