@kevin said:

@termnml

root@15:/etc/nginx/sites-enabled# ls -la /etc/nginx/sites-enabled
total 8
drwxr-xr-x 2 root root 4096 Nov 22 04:21 .
drwxr-xr-x 6 root root 4096 Nov 22 04:14 ..
lrwxrwxrwx 1 root root 41 Nov 22 04:21 bikenode.com -> /etc/nginx/sites-available/yourAppUrl.com

Ah okay. The link is wrong

root@15:# cd /etc/nginx/sites-enabled
root@15:# rm ./bikenode.com
root@15:# ln -sf /etc/nginx/sites-available/bikenode.com -T /etc/nginx/sites-enabled/bikenode.com 
root@15:# service nginx restart

server {
	listen 80;
	server_name bikenode.com;
	location / {

	    proxy_set_header X-Real-IP $remote_addr;
	    proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
	    proxy_set_header Host $http_host;
	    proxy_set_header X-NginX-Proxy true;

		proxy_pass http:127.0.0.1:4567/;
	    proxy_redirect off;

	  	proxy_http_version 1.1;
	   	proxy_set_header Upgrade $http_upgrade;
	   	proxy_set_header Connection "upgrade";
	}
}

add a ; after proxy_set_header Connection "upgrade"
So it should look like the above now.

@psychobunny could

@fr3em1nd said:

@a_5mith yep

fuser -k 3000/tcp

seem to fix it so it will kill all to processes using that port

It may do work. But it is not very clean and can lead to serious problems to solve problems of this kind that way.
Just a little advice. No offence.

PORT     STATE SERVICE
22/tcp   open  ssh
4567/tcp open  tram

1st reason could be your nginx is not running at all.
But you mentioned you restarted so I guess the 2nd possibility.

/etc/init.d/nginx start

your firewall is blocking port 80

The two nginx names are okay.
What says ls -la /etc/nginx/sites-enabled ?
Maybe a broken link. Nginx would(should XD) complain. But better check.

Glad to see. We won.
Don't forget to prepend your OP with [solved].