The “502 Bad Gateway” response error is not very descriptive in regards to what exactly might be the issues: it might be the Nginx response to an application exception. The following two threads go over some of the possible causes for the 502 response code and how to resolve the issue on an application deployed to App Engine.
[1] https://groups.google.com/d/msg/google-appengine/DEbdfwZN1lc/dxmns1_pBgAJ [2] https://groups.google.com/forum/#!topic/google-appengine/6gvlur9tXW0 On Monday, March 11, 2019 at 4:03:16 PM UTC-4, Amit kumar wrote: > > Locally django app is working fine but on being deployed with docker on > GAE, it is giving 502 Bad Gateway error. > -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To unsubscribe from this group and stop receiving emails from it, send an email to google-appengine+unsubscr...@googlegroups.com. To post to this group, send email to google-appengine@googlegroups.com. Visit this group at https://groups.google.com/group/google-appengine. To view this discussion on the web visit https://groups.google.com/d/msgid/google-appengine/7a4ffa2b-8cba-45bb-a10d-51cd7031a870%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
