502 typically means something along the lines of the app serving the website wasn’t up when nginx started. Sometimes this is simply a case of programs starting in the wrong order, and restarting nginx will fix the issue. It could also mean the app serving the website is broken.