error: 502 Bad Gateway

If you see 502 Bad Gateway errors when accessing your app, it indicates your app is crashing or unavailable.

Typical causes and potential solutions include:

• Your app is listening at the wrong place.
  • Check your app’s upstream properties.
  • If your app listening at a port, make sure it’s using thePORTenvironment variable.
• Your.platform.app.yamlconfiguration has an error and a process isn’t starting or requests can’t be forwarded to it correctly.
  • Check yourweb.commands.startentry or yourpassthruconfiguration.
• The amount of traffic coming to your site exceeds the processing power of your app.
  • Check if bots are overwhelming your site.
  • Increase your plan size.
• Certain code paths in your app are too slow and timing out.
  • Check your code is running smoothly.
  • Add an observability solution to get a better view of your app.
• A PHP process is crashing because of a segmentation fault.
  • See how to deal with crashed processes.
• A PHP process is killed by the kernel out-of-memory killer.
  • See how to deal with killed processes.

First, try to SSH into your app container. If you can't ssh into it, please open a support ticket.

For more information on this feature, please see the following page in the Platform.sh documentation:

https://docs.platform.sh/development/troubleshoot.html

Site outage 

If you can’t access some part of your project, whether it’s the live site, development environment, or Console, check the Platform.sh status page. There you can see planned maintenance and subscribe to updates for any potential outages.

If the status is operational, contact support.