Node.js 502 Bad Gateway Issues and How To Resolve Them ... | err_aborted 502
RecentNode.js502badgatewayissuesInDecemberof2018,manyNode.jsusersnoticedthattheirapplicationsrandomlyreturnedanHTTPstatuscode502“BadGateway”error.Onthe IBMCloud[1],theaffectedapplicationsaredeployedasCloudFoundryapplicationsorasDockercontainers[2]inKubernetesclusters[3].TheNode.jscommunityimmediatelynoticedtheissueandrecognizeditasaregressionbugthatwillaffectdifferentLTSruntimeversions(6.14.xand6.15.x,8.14.x,and10.14.x).Furtherinformationaboutthisbugcanbefoundin thisGithubissueonNode.jssourc...
Recent Node.js 502 bad gateway issuesIn December of 2018, many Node.js users noticed that their applications randomly returned an HTTP status code 502 “Bad Gateway” error. On the IBM Cloud[1], the affected applications are deployed as Cloud Foundry applications or as Docker containers[2] in Kubernetes clusters[3].
The Node.js community immediately noticed the issue and recognized it as a regression bug that will affect different LTS runtime versions (6.14.x and 6.15.x, 8.14.x, and 10.14.x). Further information about this bug can be found in this Github issue on Node.js source code[4].
Immediately the community started to fix this bug. Before the end of 2018, the community released new minor versions which contain the fix. In particular, the minor versions released are 6.16.x, 8.15.x, and 10.15.x.
Steps to take to resolve the iss...