502 errors when editing post, uploading featured image to post

• 

  searchremotely · Member · Aug 11, 2026 at 11:06 am

  • Copy link
  • Add topic to favorites

  502 errors when editing post, uploading featured image to post.

  The blog I need help with is: (visible only to logged in users)

• 

  staartmees · Member · Aug 12, 2026 at 6:01 am

  • Copy link

  We can’t help as that site isn’t running on the wordpress;com platform µ https://wordpress.com/site-profiler/http://searchremotely.com

  A 502 Bad Gateway error means an intermediary server (like a proxy or gateway) received an invalid response from the upstream backend server while trying to fulfill your request. It is a server-side issue, meaning the website’s servers are failing to communicate properly. You must wait for the site owners to fix it.

• 

  bilieelish90 · Member · Aug 12, 2026 at 1:13 pm

  • Copy link

  A 502 Bad Gateway error means an intermediary server (like a proxy or gateway) received an invalid response from the upstream backend server while trying to fulfill your request. It is a server-side issue, meaning the website’s servers are failing to communicate properly. You must wait for the site owners to fix it.

• 

  staff-porcupine · Staff · Aug 12, 2026 at 2:31 pm

  • Copy link

  Hi there,

  One thing to clarify up front: searchremotely.com is a self-hosted WordPress site connected to us through Jetpack, rather than a site hosted here on WordPress.com. That distinction matters because a 502 Bad Gateway is generated by your own hosting server, not by WordPress.com, so the fix lives on the hosting side. It usually means the web server didn’t get a valid response back from PHP in time, which is why it tends to surface on heavier actions like saving a post or uploading a featured image.

  Here are the most productive things to check, in order:

  1. Look at your server error logs. This is the fastest way to see the real cause. Your host can point you to the error.log/debug.log, and the entries around the time of a 502 usually reveal what timed out or ran out of memory.
  2. Ask your host to check PHP limits and PHP-FPM. A 502 on save/upload very often comes down to PHP max_execution_time or memory_limit being too low, or the PHP-FPM service needing a restart. You can ask them specifically to “confirm PHP-FPM is running correctly and review the PHP timeout and memory limits.”
  3. Rule out a plugin or theme conflict. Temporarily deactivate your plugins and switch to a default theme, then try the edit/upload again. If it works, reactivate one plugin at a time to find the culprit. Jetpack has a clear walkthrough of this here: https://jetpack.com/support/getting-started-with-jetpack/fixing-jetpack-connection-issues/

  If the site is intermittently unreachable alongside the 502s, this guide has additional steps worth going through: https://jetpack.com/support/what-to-do-if-your-site-is-down/

  Since the underlying error is coming from your hosting environment, your host will be the best resource for the server-level pieces (logs, PHP-FPM, timeouts) and to help you sort this issue out.