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

Why use a proxy?

What could be the reason I’m getting the error EADDRNOTAVAIL when executing node hello.js ?

If we are using nginx here, maybe we can use some additional cache settings? So nginx can serve all static files, and node will wake up only for executing some logic.

If I want to run my node.js app across 3 nodes with multi-core processors, PM2 can help me achieve that? I know PM2 helps me run my app across a single server with multi-core support, but if I have more nodes, Can I use PM2 or need a load-balancer like Haproxy or Nginx Proxy?

Digital Oceans always on top of their game. I have been using Monit and Upstart directly, but this seems like a quicker alternative. Thanks.

What are the advantages of suing PM2 vs using something like nodejs forever + nohup?

Great tutorial, but why you are not using NPM to install node instead? @manicas Secondly, if we are using only a single server to be APP and WEB, what would it affect?

hi Please could you tell me … Is it Ok (good ?) to use for creating the app server the image “Node -v 0.12 on 14.04” provided under the *“Create Droplet -Application” * menu ?

Does it also work with node+socket.io (two way communication)?

Hi! i have this:

g++: internal compiler error: Killed (program cc1plus) Please submit a full bug report, with preprocessed source if appropriate. See <file:///usr/share/doc/gcc-4.8/README.Bugs> for instructions. make[1]: *** [/root/node-v0.12.0/out/Release/obj.target/v8_base/deps/v8/src/api.o] Error 4 make[1]: Leaving directory `/root/node-v0.12.0/out’ make: *** [node] Error 2

What happened?

Wonderful stuff! Question is how can I prevent directory browsing of my root folder when running my app in Ubuntu? Can nginx help me save my world in this case? if I run my web server on port 8000 and my rest api on 8001 how can nginx help me start both in one command :(

Just create a separate server block for each app (listening port). Check out this tutorial: How To Set Up Nginx Server Blocks

@manicas I’m kind of confused on what the following do to the HTTP headers:

proxy_set_header Upgrade $http_upgrade;
proxy_set_header Connection 'upgrade';
proxy_cache_bypass $http_upgrade;

What is HTTP Upgrade? How does that have to do with reverse proxy?

Also how does the nginx built-in load balancer compare to pm2’s?

This was a really excellent guide, just the info I needed to get started, thanks!

Thanks for the guide. I assuming that if I configure nginx accordingly I can use this set up for a) multiple domains, and b) multiple app servers. Am I correct in that assumption?

@manicas, great tutorial.

My connection was hanging until I commented out the following line,

proxy_set_header Connection 'upgrade';

Do you have any idea why this would happen?

When using nginx I am able to access my nodejs app at the URL myapp.com/home, but if I navigate to myapp.com I still get the nginx welcome page. Is there a fix for this?

Thanks Mitchell. Wonderful post and has helped us setting our Nodejs production environment. We are facing issue where Nginx is not severing updated HTML files which is part of one nodejs application.

Do Ngnix cache all static contents by default? If yes, then what is the location of caching in Ubantu? Or it doesnt cache, can you pls help with providing required conf setting for this. Googled alot but not able to find the solution.

Great post! Now I’m truly ready for production. Digital Ocean you are really good!

Stupid question, but which droplet should the actual domain name (e.g. example.com) be registered to: the WEB droplet or the APP droplet?

I get this, whats missing or wrong ?

pm2 hello.js [PM2] Spawning PM2 daemon Error: spawn ENOENT at errnoException (child_process.js:988:11) at Process.ChildProcess._handle.onexit (child_process.js:779:34) Error: spawn ENOENT at errnoException (child_process.js:988:11) at Process.ChildProcess._handle.onexit (child_process.js:779:34) Did you forgot to call pm2.connect(function() { }) before interacting with PM2 ?

the part about PM2 will save my life some day…

I have read dozens of other ways to restart an app after reboot but NONE worked. Maybe because my app runs in /home/myUser and this is not yet ready when the server boots and the configured files are started?

Well, PM2 works well.

Actually: today a digital ocean server went down momentarily (first time in two years and about 6 apps) and my application didn’t restart after reboot - that’s why I finally found this article. It won’t happen again!

thanks!

Thank you! This was really informative and well explained! I only had one problem, but the problem did not stop me from setting everything up. Running sudo npm install pm2 -g gave me errors regarding git. I realized I did not have git installed. But even after installation of git I got a new error: “npm WARN optional dep failed, continuing fsevents@0.3.6”

Well, Its working atleast! I am also just using one server.

I couldn’t get my private ip address, what should i input to my command prompt exactly?

Extremely easy to follow and just what I needed to deploy! Thanks!

Very nice tutorial, nginx is returning a 404, after a redirect from my node app to a static login page (the login page didn’t load. should i have another configuration if node is using ui-route? or does it have a conflict with static content being serve by node?

In my application with nodejs + redis + rails, can i use this configuration for node and use this (https://www.digitalocean.com/community/tutorials/how-to-deploy-a-rails-app-with-passenger-and-nginx-on-ubuntu-14-04) for my rails app? With some changes, off course.

Great tutorial! Works perfectly for me.

You can start a droplet with nodejs already installed, is it safe to skip your install step? or is there something different compared to yours.

Adding additional locations other than a root ‘/’ domain it not working for me. The additional locations just redirects to the default nginx page or to the app deployed to / (if any)

In the example below /uds will redirect to the default nginx page if I replace the /uds with / - it’s getting to my node app.

server {
    listen 80;

    server_name mydomain.com;

    location /uds {
        proxy_pass http://127.0.0.1:3000;
        proxy_http_version 1.1;
        proxy_set_header Upgrade $http_upgrade;
        proxy_set_header Connection 'upgrade';
        proxy_set_header Host $host;
        proxy_cache_bypass $http_upgrade;
    }
}

Hi I followed this blog. I am using one Digital Ocean droplet to set up. I end up with a error of 502 Bad Gateway.

Do you know what I can do to fix this?

Thanks for the amazing tutorial! Really helped! One problem: when I access my app by it’s domain+port like http://www.site.com:8000 it works fine, I can see all data and all. But when I access without the port, it doesn’t show any of the data. Weird part: when I add data from the address WITHOUT the port, it adds normally, but shows only on the app WITH the 8000 port, and not on the one without port. What should I do?

Hi everybody, I do not understand why sometines you do use sudo and sometines you don’t.

Hello, I have a problem, with this settings nginx doesnt load the website when accessed with “www.” because it’s a subdomain, how can I do this? I have tried this in nginx config default ( /etc/nginx/sites-available/default ) : server { listen 80; server_name www.domain.com; return 301 $scheme://domain.com$request_uri; }

server { listen 80;

server_name domain.com;
location / {
    proxy_pass http://127.0.0.1:8080;
    proxy_http_version 1.1;
    proxy_set_header Upgrade $http_upgrade;
    proxy_set_header Connection 'upgrade';
    proxy_set_header Host $host;
    proxy_cache_bypass $http_upgrade;
}

}

I found this in stackoverflow but it doesnt work, how can i make www. to redirect to non-www or at least be able to see the website also with www?

Thank you for your help!

Thanks, interesting and informative read!

Hello,

I am newbie in administration of server. Should I use two droplets with ubuntu for this example? Did I understand it right?

Node source mentioned is very old. Current Node version 5.0.0

Would be nice to see the article being updated once in a while…

is it possible to setup 2 reverse proxy to point to Node.js application server ?

Awesome tutorial! Been using this on my droplet for a while and it all worked well. But now when I’m updated my source code and done ubuntu updates, nginx/pm2 crashed and I dont have any idea why really. For starter I had a problem running pm2 without “sudo” but I think I figured that out, and now to the remaining problem: When visiting the site in the browser I get 502 Bad gateway, and when looking at the log I get this:

nginx: [emerg] bind() to 0.0.0.0:80 failed (98: Address already in use)
nginx: [emerg] still could not bind()

and I dont get any errors when running nginx -t. So a little out of my knowledge right now.

Have been looking around in the nginx files and /etc/nginx/sites-available/default and /etc/nginx/sites-enabled/default contains the same information and that is the only thing I can think of?

The configuration for nginx are as in the tutorial.

Adding additional locations other than a root ‘/’ domain it not working for me. The additional locations just redirects to the default nginx page or to the app deployed to / (if any)

In the example below /uds will redirect to the default nginx page if I replace the /uds with / - it’s getting to my node app.

server {
    listen 80;

    server_name mydomain.com;

    location /uds {
        proxy_pass http://127.0.0.1:3000;
        proxy_http_version 1.1;
        proxy_set_header Upgrade $http_upgrade;
        proxy_set_header Connection 'upgrade';
        proxy_set_header Host $host;
        proxy_cache_bypass $http_upgrade;
    }
}

Hi I followed this blog. I am using one Digital Ocean droplet to set up. I end up with a error of 502 Bad Gateway.

Do you know what I can do to fix this?

Thanks for the amazing tutorial! Really helped! One problem: when I access my app by it’s domain+port like http://www.site.com:8000 it works fine, I can see all data and all. But when I access without the port, it doesn’t show any of the data. Weird part: when I add data from the address WITHOUT the port, it adds normally, but shows only on the app WITH the 8000 port, and not on the one without port. What should I do?

Hi everybody, I do not understand why sometines you do use sudo and sometines you don’t.

Hello, I have a problem, with this settings nginx doesnt load the website when accessed with “www.” because it’s a subdomain, how can I do this? I have tried this in nginx config default ( /etc/nginx/sites-available/default ) : server { listen 80; server_name www.domain.com; return 301 $scheme://domain.com$request_uri; }

server { listen 80;

server_name domain.com;
location / {
    proxy_pass http://127.0.0.1:8080;
    proxy_http_version 1.1;
    proxy_set_header Upgrade $http_upgrade;
    proxy_set_header Connection 'upgrade';
    proxy_set_header Host $host;
    proxy_cache_bypass $http_upgrade;
}

}

I found this in stackoverflow but it doesnt work, how can i make www. to redirect to non-www or at least be able to see the website also with www?

Thank you for your help!

Thanks, interesting and informative read!

Hello,

I am newbie in administration of server. Should I use two droplets with ubuntu for this example? Did I understand it right?

Node source mentioned is very old. Current Node version 5.0.0

Would be nice to see the article being updated once in a while…

is it possible to setup 2 reverse proxy to point to Node.js application server ?

Awesome tutorial! Been using this on my droplet for a while and it all worked well. But now when I’m updated my source code and done ubuntu updates, nginx/pm2 crashed and I dont have any idea why really. For starter I had a problem running pm2 without “sudo” but I think I figured that out, and now to the remaining problem: When visiting the site in the browser I get 502 Bad gateway, and when looking at the log I get this:

nginx: [emerg] bind() to 0.0.0.0:80 failed (98: Address already in use)
nginx: [emerg] still could not bind()

and I dont get any errors when running nginx -t. So a little out of my knowledge right now.

Have been looking around in the nginx files and /etc/nginx/sites-available/default and /etc/nginx/sites-enabled/default contains the same information and that is the only thing I can think of?

The configuration for nginx are as in the tutorial.

Hi, i did my setup at the end of tutorial like this server { listen 80;

server_name www.myPortfolio.com;
      
location / {
    proxy_pass http://my_private_ip:8080;
    proxy_http_version 1.1;
    proxy_set_header Upgrade $http_upgrade;
    proxy_set_header Connection 'upgrade';
    proxy_set_header Host $host;
    proxy_cache_bypass $http_upgrade;
}

}
Now, my next step it’s to upload my front-end via filezilla thats what i put host: 159.203.22.215 username: me password: XXXXXXX port: 8080

then somehow i still get Connecting to 159.203.22.215:8080… Status: Connection attempt failed with “ECONNREFUSED - Connection refused by server”. Error: Could not connect to server

i need help !!! :(

Did this all just change in the last two weeks? I swear the commands are different from when I went through this last month and now the commands like “yum” and “systemctl” aren’t being recognized and I don’t remember them from before. I’m on Ubuntu 14.

I have been trying to figure out how to point the server to my static page that i store it up somewhere in my cloud server. Also, i am using NodeJs as my backend.

My new problem: After this new configuration that i did, it points me to a 404 page instead of pointing to my index.html

Also, in the line 20, it gives me an error of duplicate “/” when i run sudo nginx -t for debugging purpose

````nginx: [emerg] duplicate location "/" in /etc/nginx/sites-enabled/default:20 ````

here’s my Nginx configuration file…

    server {
        listen 80 default_server;
        listen [::]:80 default_server ipv6only=on;

        server_name www.andii90s.com;

        root /home/andy/www/myProjectX/app;
        index index.html index.htm;


        location / {
            proxy_pass http://10.137.10.140:8080;
            proxy_http_version 1.1;
            proxy_set_header Upgrade $http_upgrade;
            proxy_set_header Connection 'upgrade';
            proxy_set_header Host $host;
            proxy_cache_bypass $http_upgrade;
        }

        location / {
            #Line 20
            try_files $uri $uri/ =404;
        }

        error_page 404 /404.html;
        error_page 500 502 503 504 /50x.html;
        location = /50x.html {
           root /home/andy/www/myProjectX/app;
        }
    } 

Is there a way to do this on an apache server that points to a subdomain e.g. node.example.com instead of IP_ADDRESS:8080? Forgive me if this is a silly question. Very new to it all.

Do I have to have two droplets—one for app and the other for web—for this to work?

Hey,

I’m a bit confused and lost. Does the APP_PRIVATE_ID_ADDRESS equal with the “Droplet/Settings/ (Networking tab) Private Network/Private IP” ??

Hi Mitchell, great tutorial! How could I serve a second app on a second server block?

I tried to serve a second app on port 8081, and connect it with a second server block file, when I restart nginx it fails an I receive the following error log: 2016/02/02 11:21:23 [emerg] 5447#0: invalid port in upstream "10.135.0.205:8081

I´m able to connect the app with curl http://10.135.0.205:8081

content of my server block file:

server { listen 80;

server_name sidejob.ch;

location / {
    proxy_pass http://10.135.0.205:8081>;
    proxy_http_version 1.1;
    proxy_set_header Upgrade $http_upgrade;
    proxy_set_header Connection 'upgrade';
    proxy_set_header Host $host;
    proxy_cache_bypass $http_upgrade;
}

}

If i’d wanted to make a GET request to the nodejs from my website like this:

< script src =" urltothefile /file. js" > < / script >

how would i do that?!

Hello Sir I have configured Nginx successfully and it works well. For example I could visit my site from http://123.123.123.123. But I can also visit it from inner port like: http://123.123.123.123:7999, is this result normal or I should do something to ban the 7999 connections ? By the way the Nginx and Nodejs are on the same instance and the app was started by : sudo npm start. The conf file is like this: server { listen 80; server_name 123.123.123.123;

location / {
    proxy_pass http://127.0.0.1:7999;
    proxy_http_version 1.1;
    proxy_set_header Upgrade $http_upgrade;
    proxy_set_header Connection 'upgrade';
    proxy_set_header Host $host;
    proxy_cache_bypass $http_upgrade;
}

}

Thanks a lot, Sir, your tutorial is excellent and very easy to learn.

I have my app running on http://PRIVATE_IP:3000 My droplet configured to MY_DOMAIN.com in Networks. My nginx file at /etc/nginx/sites-available/default configured to

server {
    listen 80;
    server_name MY_DOMAIN.com;

    location / {
        proxy_pass http://PRIVATE_IP:3000;
        proxy_http_version 1.1;
        proxy_set_header Upgrade $http_upgrade;
        proxy_set_header Connection 'upgrade';
        proxy_set_header Host $host;
        proxy_cache_bypass $http_upgrade;
    }
} 

And I have restarted nginx. But i can only connect to MY_DOMAIN.com:3000 not MY_DOMAIN.com . Any ideas why?

For me to get pm2 restarting to work I had to run** $ pm2 save** after I had run sudo su -c “env PATH=$PATH:/opt/node/bin pm2 startup ubuntu -u sammy --hp /home/sammy”

I found this on https://serversforhackers.com/node-process-management-with-pm2

Hello, I have created two droplets:

1. Web Server(not installed NGINX yet, as operating system Ubuntu)
2. App Server(have enabled the IP-adress, installed “MEAN Stack one-click-app” and as Operatiog System Ubuntu)

Well, I have create at my App Server the “hello.js” file for testing like the example above:

var http = require(‘http’); http.createServer(function (req, res) { res.writeHead(200, {‘Content-Type’: ‘text/plain’}); res.end(‘Hello World\n’); }).listen(8080, ‘APP_PRIVATE_IP_ADDRESS’); console.log(‘Server running at http://APP_PRIVATE_IP_ADDRESS:8080/’);

The app is running at my App server and at my Web server I want to run the command “curl http://APP_PRIVATE_IP_ADDRESS:8080” for testing but it happened nothing. Just the connection timed out.

In Menu Networking I have set the domains for the app server as follow:

A: @ -> public IP CNAME www - mydomain

What I did wrong?

After run the sudo command to set pm2 up on boot, you have to run “pm2 save”. With this, your app will run too…

Excellent Tutorial. Helped me publish my very first app. Thank you!

for some reason when i use curl to test if the hello.js app is working on the web server it doesnt work

It doesn’t work with my routes in node (it gives me an 404 error). Anyone knows what can I do to solve this issue?

Thanks

Thanks for this tutorial! Simple and useful, that’s the way I like it.

Critical step:

After you do a pm2 start hello.js, I had to do a pm2 save, before I daemonized. Otherwise when I did a sudo service pm2 restart my application did not get spawned automatically (Ubuntu 14.04, node v4.4.5).

I was getting an error when using pm2: /usr/bin/env: node: No such file or directory

And I found the solution, in case anyone was searching for it: I had installed node.js with this method: sudo apt-get install nodejs

this installs node as “nodejs” instead of “node” (there is another Ubuntu package named “node” that is a Ham Radio program), so pm2 couldn’t find it. So, I found this fix:

sudo ln -s /usr/bin/nodejs /usr/bin/node

this creates a symbolic link from “nodejs” to “node”. Now pm2 can continue as expected. You might want to be sure you don’t need to use a ham radio on your server before using this fix though ;)

Missing a slash…should be:

sudo mv node/ /opt

The line sudo npm install pm2 -g shouldn’t include sudo. You should never run npm as sudo! There’s a help page on the npm website to fix the sudo problem - https://docs.npmjs.com/getting-started/fixing-npm-permissions

Great tutorial!

I just add two helpful tutorials as complement:

• How To Set Up And Use DigitalOcean Private Networking
• How To Install Git on Ubuntu 14.04

my pm2 not woking at restart the machine…

pm2 start hello.js pm2 startup ubuntu

[PM2] Generating system init script in /etc/init.d/pm2-init.sh
[PM2] Making script booting at startup...
[PM2] -ubuntu- Using the command:
      su -c "chmod +x /etc/init.d/pm2-init.sh && update-rc.d pm2-init.sh defaults"


[PM2] Done.

su -c “chmod +x /etc/init.d/pm2-init.sh && update-rc.d pm2-init.sh defaults” pm2 save

[PM2] Saving current process list...
[PM2] Successfully saved in /root/.pm2/dump.pm2

App working :)

shutdown -r now

waiting start…

App not working :(

pm2 list

no running

Hey Team,

After configuring nginx along with domain name. I am getting ngix successful configuration message but not the node js message which should be Hello World in this case. Any help would be appreciated.

Hi i got this problem, when I use 127.0.0.1 in the app server everything works fine, but when I use my private network address it crashes and shows me the following message:

events.js:141 throw er; // Unhandled ‘error’ event ^

Error: listen EADDRNOTAVAIL 10.132.83.150:8080 at Object.exports._errnoException (util.js:874:11) at exports._exceptionWithHostPort (util.js:897:20) at Server._listen2 (net.js:1221:19) at listen (net.js:1270:10) at net.js:1379:9 at doNTCallback3 (node.js:452:9) at process._tickCallback (node.js:358:17) at Function.Module.runMain (module.js:469:11) at startup (node.js:136:18) at node.js:963:3

Please need help,

I tried the application (hello.js) following this tutorial and all was ok. But I tried another app that contains static files and it doesn’t work. What’s the problem ? thanks

For this instruction i am getting not found

curl -w “\n” http://169.254.169.254/metadata/v1/interfaces/private/0/ipv4/address not found

Hi,

Am trying to setup multiple domain multiple app nginx node.js apps with https, and so far only one of them works at a time. my setup is as follows for the sites-enabled.

I hope someone can spot the mistake, thanks a lot

default

# HTTP - redirect all requests to HTTPS:
server {
        listen 80;
        listen [::]:80 default_server ipv6only=on;
        return 301 https://$host$request_uri;
}

domain1.com

server {
        listen 443;
        server_name domain1.com, www.domain1.com;

        ssl on;
        # Use certificate and key provided by Let's Encrypt:
        ssl_certificate /etc/letsencrypt/live/domain1.com/fullchain.pem;
        ssl_certificate_key /etc/letsencrypt/live/domain1.com/privkey.pem;
        ssl_session_timeout 5m;
        ssl_protocols TLSv1 TLSv1.1 TLSv1.2;
        ssl_prefer_server_ciphers on;
        ssl_ciphers 'EECDH+AESGCM:EDH+AESGCM:AES256+EECDH:AES256+EDH';

        # Pass requests for / to localhost:8080:
        location / {
                proxy_set_header X-Real-IP $remote_addr;
                proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
                proxy_set_header X-NginX-Proxy true;
                proxy_pass http://localhost:5000/;
                proxy_ssl_session_reuse off;
                proxy_set_header Host $http_host;
                proxy_cache_bypass $http_upgrade;
                proxy_redirect off;
        }
} 

domain2.com

server {
        listen 443;
        server_name domain2.com, www.domain2.com;

        ssl on;
        # Use certificate and key provided by Let's Encrypt:
        ssl_certificate /etc/letsencrypt/live/domain2.com/fullchain.pem;
        ssl_certificate_key /etc/letsencrypt/live/domain2.com/privkey.pem;
        ssl_session_timeout 5m;
        ssl_protocols TLSv1 TLSv1.1 TLSv1.2;
        ssl_prefer_server_ciphers on;
        ssl_ciphers 'EECDH+AESGCM:EDH+AESGCM:AES256+EECDH:AES256+EDH';

        # Pass requests for / to localhost:8080:
        location / {
                proxy_set_header X-Real-IP $remote_addr;
                proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
                proxy_set_header X-NginX-Proxy true;
                #DIFFERENT PORT
                proxy_pass http://localhost:3000/;
                proxy_ssl_session_reuse off;
                proxy_set_header Host $http_host;
                proxy_cache_bypass $http_upgrade;
                proxy_redirect off;
        }
}

Thanks for the guide.

I’ve set up my Nginx proxy and it works just fine. But when I try to access the ip and port directly, I get an unable to connect error.

That is: http://mydomain.com works just fine

But: http://myserverip:port fails

Yes, the server ip alone returns the default Nginx page. But add the port and the error occurs. Should my default Nginx config have a proxy in it too?

This command:

curl -w "\n" http://169.254.169.254/metadata/v1/interfaces/private/0/ipv4/address

Returns not found.

I’m not sure how I’m supposed to determine my private IP address. Can I use the eth1 ip address? It looks like it’s a 10.x.x.x non-routable IP.

To some people it is probably obvious but I struggled for a bit on the part about the server_name in the config file. I was putting the private_ip as the server_name instead of the public ip since the article does not specify. Most people probably won’t have this issue but I slipped up and wasted a good hour or so. Just a heads up. Great article by the way!

JFYI… when creating Node.js applications you might need to store configuration items in a file. Instead of keeping them in cleartext, use the masterkey package as mentioned here: https://www.attosol.com/secure-application-secrets-using-masterkey-in-azure-key-vault/

How to check is my proxy server is working or not. I follow all the above step to set my proxy server but how I know that proxy server is really working.

I’m doing like this

My node app :

const fs = require('fs');
const https = require('https');
const express    = require('express'); 
const app        = express(); 

var router = express.Router();  

router.get('/',function(req,res){
    	// console.log("Route = /");
    	res.json({"success" : 1})
});

app.use('/api/v2', router);

app.listen(8080);

My proxy config :

server {
    listen 80;

    server_name APP_PRIVATE_IP_ADDRESS;

    location / {
        proxy_pass http://APP_PRIVATE_IP_ADDRESS:8080;
        proxy_http_version 1.1;
        proxy_set_header Upgrade $http_upgrade;
        proxy_set_header Connection 'upgrade';
        proxy_set_header Host $host;
        proxy_cache_bypass $http_upgrade;
    }
}

this blog providing good information To learn NodeJS visit http://iwebworld.info contact: iwebworldinfo@gmail.com

I’m getting the error EADDRNOTAVAIL when executing node hello.js, and I am using both Node.JS and nginx at the same droplet. When using private IP, it cause this error and hello.js never works, but using localhost or the public ip, it is working ( but not accessd via browser, I can access it using another terminal and login into the root to test it).

For starters who are not comfortable on the command line, this is simply a no go for many. This is where a tool like opscaptain can help you deploy Node.js applications to your digitalocean droplet the easy way with either a simple upload from the dashboard or run [opscaptain deploy] and that is it. No need to fiddle with bash scripts and maintain them. Simply connect your droplet and you are ready to deploy. https://www.opscaptain.com/nodejs-hosting

hi ,

i am running npm app.js instead the actual directory and it is successful but when i close putty the application stops running and says site cant be reached . This is happening recently in digital ocean server

You’ve GOT to be kidding!!

I have two app server , both need to run npm build before pm2 start , built command generate dist folder , each app different content in dist folder. Am using load balancer with upsteam backend but its getting issue, that is ,first time any user load web site and he may connect to app1 server from the upsteam ,and if he reload once again it will connect second app server, this time he con’t load website correctly because dist folder files will miss mach, can u plz suggest better solution , am looking both app can use one dist folder or any other better solution is there.

I find the best solution always here. Thanks Digital Ocean