Node.js runtime getting 502 - bad gateway

202 views
Skip to first unread message

Gokul Kulkarni

unread,
Nov 29, 2017, 10:49:30 AM11/29/17
to Google App Engine
Hi All,

I have a node.js application, which runs very fine in the local environment without any issues, but I deploy the same in the GCP app engine and when I try to access any API I start getting 502 - Bad gateway error. I do not find anything in the logs.

Yannick (Cloud Platform Support)

unread,
Nov 29, 2017, 4:51:05 PM11/29/17
to Google App Engine
Hello Gokul, this usually means that the App Engine service wasn't able to get a response from your application, which usually means it's not configured properly for use on App Engine.

To get help in figure out what's going wrong you should post on Stack Overflow using one of the tags monitored by our community technical support team with a description of your application and the code that initializes it and allows it to listen to requests.

Be sure to post a link to your Stack Overflow question here so it gets more attention from the group!
Reply all
Reply to author
Forward
0 new messages