Share

Question

Hello,
I managed to setup my test app (NODE/Express) on http://178.128.173.30/ but I can access it through http:// only when app.listen(80);

I have opened few other ports in console with sudo ufw allow but none of them working. Am I missing something?

Current sudo ufw status below:

To	Action	From
22	LIMIT	Anywhere
80	ALLOW	Anywhere
443	ALLOW	Anywhere
Nginx HTTP	ALLOW	Anywhere
50/tcp	ALLOW	Anywhere
50	ALLOW	Anywhere
80/tcp	ALLOW	Anywhere
21/tcp	ALLOW	Anywhere
500:600/tcp	ALLOW	Anywhere
500:600/udp	ALLOW	Anywhere
22 (v6)	LIMIT	Anywhere (v6)
80 (v6)	ALLOW	Anywhere (v6)
443 (v6)	ALLOW	Anywhere (v6)
Nginx HTTP (v6)	ALLOW	Anywhere (v6)
50/tcp (v6)	ALLOW	Anywhere (v6)
50 (v6)	ALLOW	Anywhere (v6)
80/tcp (v6)	ALLOW	Anywhere (v6)
21/tcp (v6)	ALLOW	Anywhere (v6)
500:600/tcp (v6)	ALLOW	Anywhere (v6)
500:600/udp (v6)	ALLOW	Anywhere (v6)

Answer 1

X40C August 25, 2018

https://www.digitalocean.com/community/tutorials/how-to-set-up-a-node-js-application-for-production-on-ubuntu-16-04

How To Set Up a Node.js Application for Production on Ubuntu 16.04

by Brennen Bearnes

Node.js is an open source JavaScript runtime environment for easily building server-side and networking applications. Node.js applications can be run at the command line but this guide focuses on running them as a service using PM2, so that they will automatically restart on reboot or failure, and can safely be used in a production environment.

Reply

Answer 2

Numbian August 26, 2018

But I don't need Nginx - I use Express. As I wrote above I have set up server successfully. I can't make app work on other port than 80.

Reply

X40C August 26, 2018

http://ping.eu/port-chk/ for port checking. And first google result related to your issue: https://stackoverflow.com/questions/18008620/node-js-express-js-app-only-works-on-port-3000 .

Answer 3

X40C August 26, 2018

http://ping.eu/port-chk/ for port checking. And first google result related to your issue: https://stackoverflow.com/questions/18008620/node-js-express-js-app-only-works-on-port-3000 .

Answer 4

Numbian August 26, 2018

I have read all those before posting here. Thx I will search somewhere else this is pointless :)

Reply

X40C August 26, 2018

Well you should really first make sure that the app is listening on your desired port with something like lsof -i :port or netstat -tupan |grep port . After try pinging the desired port with the tool i provided above(could be a local block from your ISP).
- Numbian August 26, 2018
  
  All works fine now. I only had to put :8080 after ip in browser <facepalm>.
  
  Port 80 is default so http://178.128.173.30/ was working fine.
  With app.listen(8080) I only had too use http://178.128.173.30:8080.
  
  X40C August 26, 2018
  
  xD

Answer 5

X40C August 26, 2018

Well you should really first make sure that the app is listening on your desired port with something like lsof -i :port or netstat -tupan |grep port . After try pinging the desired port with the tool i provided above(could be a local block from your ISP).
- Numbian August 26, 2018
  
  All works fine now. I only had to put :8080 after ip in browser <facepalm>.
  
  Port 80 is default so http://178.128.173.30/ was working fine.
  With app.listen(8080) I only had too use http://178.128.173.30:8080.
  
  X40C August 26, 2018
  
  xD

Node.js with express is accessible only via port 80.

Leave a Comment

Share

Share your Question

Node.js with express is accessible only via port 80.

Leave a Comment

Related Questions

Almost there!