502 Errors on every request to GAE Flex PHP Runtime

[Paul Kim]

Hello,

Issue: 502 errors on every web request to newly deployed apps (as of this morning) on Google App Engine Flexible Environment with PHP runtime with a custom service specified in app.yaml.

I started encountering this error today.  Every request to the application results in a 502 error.  It was working fine this morning.  It appears to be occurring on any new deployments where a service is specified in the yaml config.  Previously deployed apps were not affected.

I have tried deploying the sample Hello World app here to make sure it's not an issue with my app or config:

https://cloud.google.com/appengine/docs/flexible/php/quickstart

1. Ran the Hello World app locally and worked fine.
2. Deployed to the GAE with a custom service specified and all requests result in a 502 error.
3. Works fine on GAE with the default service.
   

I also tried creating a new service but 502 errors appeared that as well.  When looking at the App Engine logs, it doesn't appear that the requests ever made it to the GCE instances (there are no logs of the requests).

@type:  "type.googleapis.com/google.cloud.loadbalancing.type.LoadBalancerLogEntry"   

statusDetails:  "failed_to_connect_to_backend" 

[Kenworth (Google Cloud Platform)]

This was a known issue affecting some users. It could also manifest itself in an elevated error rate with the Cloud Load Balancers. This issue has since been resolved for all users as of 2018-05-25 20:20 US/Pacific. If this is still a problem, please open a new issue via the channels detailed here: https://cloud.google.com/support/docs/issue-trackers

[Paul Kim]

Thank you for the update.  Is there a reason why this issue was not posted to the Google Cloud Platform Status dashboard?  We wasted a few hours yesterday trying to determine the cause of the issue.  Luckily, our production service was unaffected.

[Kenworth (Google Cloud Platform)]

Hi Paul, the issue was not posted on the dashboard because it was only affecting a handful of users. Next time an issue happens and you highly suspect it is a defect on the platform rather than your end, feel free to report it here as per this article.