JSOPanel Get started
Help Center › Website Owners › My website shows a 502 Bad Gateway error

My website shows a 502 Bad Gateway error

A 502 usually means your site used more memory or processes than your plan allows.

A 502 Bad Gateway means the server is running, but the program that builds your pages stopped answering. The most common reason is that your site used more memory, or more simultaneous processes, than your hosting plan allows. When that happens the server stops the program to protect everyone else on it, then starts it again automatically. If it keeps happening in quick succession, the site stays on 502 until it is started again.

Steps

  1. Wait a minute and reload the page. A single, short 502 during a heavy moment often clears itself, because the server restarts your site automatically.
  2. Think about what was running when it started. Large imports, backup or optimisation plugins, bulk image processing, and a plugin or theme update running at the same time as a busy period are the usual causes. Stop that task, or move it to a quiet hour with a cron job.
  3. Open Resource usage and look at Memory now and Processes for your account. It reads idle when nothing is running. Figures that stay high while your site is quiet point to something running that should not be.
  4. Open Processes under Advanced to look for a script that is stuck. See Checking what's running on your account.
  5. If the error keeps coming back, contact your hosting provider. Give them your domain name and the time the error appeared, and say it is a 502. They can see whether the site reached its memory or process limit and raise it, or move you to a larger plan.
Tip: asking for a bigger limit gets the site back, but it works best together with finding what used the memory. A single plugin or a large one-off task is more common than a site that is simply too small.

If the page shows a different error, or it is blank rather than a 502, see My website shows a server error or blank page.