OK -- this is solved. It must happen in the npm start stuff. Some combination of a pm2 delete and a pm2 start managed to get node running on 8080. But I believe this stuff is flaky, because I tried the same things numerous times. Sometimes it seems you have to do these commands twice. This time was much worse. Very flaky indeed. But for now this is solved.by fbs - Nginx Mailing List - English
So this is very strange. We use nginx for our reactJS website as well as proxy_pass to asp pages on another windows box. I recently installed a new cert from digicert, and now I can't get Node.js to work. The proxy pass works fine, and digicert says our cert is correctly installed. But I get a ton of the same errors in the nginx error.log -- basically at Bad Gateway (502) error: 2023/09/09by fbs - Nginx Mailing List - English
![]() |
![]() |
![]() |
![]() |
![]() |