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
Come individuare il guasto di discourse upstream all'interno del container che causa 502 Bad Gateway
3 Mi Piace