Error 502 Bad Gateway - Why & How?


Today my team’s site was throwing the 502 Bad Gateway error for around 12 minutes.
Pulsetic monitors the site and showed the downtime here.

I think the deployment logs look fine except for a TypeError that seems unrelated. Could anyone help me by explaining what might have happened and how to prevent it?

Newbie here, so please forgive my inexperience.

Hi there,

Thanks for reaching out.

502s can manifest for a number of different reasons, like your service not being able to provide a connection, or an issue further up the infrastructure chain. If you see them again, please feel free to open a ticket (“Contact Support” link when logged into the dashboard) and share the response headers (e.g. curl -I ``

Kind regards


Hi, thank you for your response.

Just to ensure I understand you, if this should happen again, where should I type curl -I `` Would it be in the shell command area that I can navigate to from my dashboard?

Apologies, I think the formatting got messed up. It would be:

curl -I

And that is a shell command to run from your own machine.


1 Like

Does the 502 error have to be active in order for support to diagnose the issue?

The headers from an occurring 502 can help toward diagnosing the issue, so yes, it would need to be happening to get those headers.


1 Like

Thank you Alan!

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.