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.