502 Bad Gateway Error when accessing Google Firebase Hosting from Google App Engine

[Martin Hellwagner via StackOverflow]

I'm running into a 502 Bad Gateway Error when wanting to access static files hosted on Google Firebase Hosting from a Node.js app hosted on Google App Engine. When accessing the same files from my local machine, everything is working fine. All the CORS headers are defined properly.

Am I missing something else, like an access key for Firebase or so? I believe the problem might lie with my "app.yaml" deployment file.

Thanks for you help!

Screenshot

Please DO NOT REPLY directly to this email but go to StackOverflow:
http://stackoverflow.com/questions/38303991/502-bad-gateway-error-when-accessing-google-firebase-hosting-from-google-app-eng

[Martin Hellwagner via StackOverflow]

I'm running into a 502 Bad Gateway Error when wanting to access static files hosted on Google Firebase Hosting from a Node.js app hosted on Google App Engine. When accessing the same files from my local machine, everything is working fine. All the CORS headers are defined properly.

Am I missing something else, like an access key for Firebase or so? I believe the problem might lie with my app.yaml deployment file.

[Martin Hellwagner via StackOverflow]

Solved the problem myself! Since most middleware is bundled with Express, it was necessary to manually add the package for my EJS views in package.json.

Please DO NOT REPLY directly to this email but go to StackOverflow:

http://stackoverflow.com/questions/38303991/502-bad-gateway-error-when-accessing-google-firebase-hosting-from-google-app-eng/38374292#38374292

[Martin Hellwagner via StackOverflow]

Solved the problem myself! Since most middleware is not bundled with Express any more, it was necessary to manually add the package for my EJS views in package.json.