Hi Alison,
Sometimes 502 errors (which are typically about a problem between the source site - i.e. your AtoM installation - and the webserver [Nginx] responding to requests) are falsely returned by a web browser due to cache issues. Therefore, the first thing to determine is whether it's just your browser or not. Things you can try:
- Perform a hard refresh: most browsers support CTRL+SHIFT+R as a way of refreshing a page without using a cached version (or CMD instead of CTRL on a Mac)
- Clear your web browser's cache, or test in an incognito / private browser window, where caching is typically disabled by default
- Test in an entirely different browser (to make sure that browser plugins or extensions are not contributing to the issue)
- Entering your AtoM site URL into an online status checker, such as https://www.isitdownrightnow.com/ or https://downforeveryoneorjustme.com/
If it IS a local issue, then try things like clearing your web browser cache, restarting your browser or computer, etc. If it's not a local issue and there is in fact a problem with your site, then the first thing you should do is check the webserver logs to see if more information about the nature of the error is available. See:
Beyond that, it will depend on what you find! Feel free to share any relevant error message you come across, and we will try to offer further suggestions.
Cheers,