Great. I actually just googled it after you mentioned it and found a bunch of stuff as well. I am still having an issue where I can re-attach to a screen, the only one running with screen -ls but my sever does not appear. Any idea how I can see the server?
The server is running somewhere, I just can’t find it :)

It definitely has a learning curve to it. But once you do it a few times it’s a a piece of cake. Try this:

screen -d -r
ps -elf|grep nodejs

What do you see?

Yeah for sure!

I get this
0 S arssoni+ 8407 8327 0- 3714 pipe_w 19:28 pts/3 00:00:00 grep --color=auto nodejs

If running “screen -d -r” completed without error or warning that means you’re inside a SCREEN session. And because there’s no nodejs process running, go ahead and start nodejs now. Anytime you want to close your terminal but keep nodejs running you can do that and nodejs will keep running in the background. If you want to reconnect to the screen session after you close your terminal run this:

screen -d -r

If you want to get out of the screen session but keep it running, type this:

ctrl-a-d

I was able to attach/detach and quit useless sessions using the commands you’ve given me, but I could not see the running server. When I try to restart node, I go node app.js in this case, it says that port 3000, the place I started it originally, is already in use.

I guess I thought I would be able to log in to that particular running server?
If I do screen -d -r 4445 , I think this is the name of the screen I want, it brings me there, but there is no running server.

Let’s figure out what’s running on that port. Do this:

netstat -atnlp|grep “3000”

fuser 3000/tcp

This is out of comfort zone now. Haha.
netstat -atnlp|grep "3000"
Gives:
tcp6 0 0 :::3000 :::* LISTEN 4502/node

And
fuser 3000/tcp
Gives:
3000/tcp: 4502

I killed the process and now my app is dead.
So, when I started the app I used a npm script npm run prod. That is the script to start it. I’m a currently trying to get pm2 to run the app but it will not. Man this is confusing.