Deploying a Node.js app shouldn’t feel like solving a Rubik’s cube blindfolded. But if you’re new to unmanaged server hosting, DigitalOcean’s droplet setup can seem intimidating at first. This step-by-step guide will walk you through every stage of a DigitalOcean Node.js deploy, from spinning up a droplet to securing your app with SSL — no prior server management experience required.
Prerequisites
Before you start your DigitalOcean Node.js deploy, make sure you have these basics ready:
- A DigitalOcean account (sign up for a free credit if you’re new)
- A simple Node.js app to deploy (a “Hello World” app on port 3000 works fine)
- Basic familiarity with terminal commands
- An SSH key (optional but highly recommended for secure access)
Step 1: Create a DigitalOcean Droplet
A droplet is DigitalOcean’s term for a virtual private server. Follow these steps to set one up:
- Log into your DigitalOcean dashboard and click Create > Droplets.
- Choose Ubuntu 22.04 LTS as your operating system (it’s stable and widely supported).
- Select the Basic plan, then pick the $6/month shared CPU option (sufficient for small Node.js apps).
- Choose a datacenter region closest to your target users for lower latency.
- Add your SSH key under the Authentication section (or choose password authentication if you prefer).
- Set a hostname for your droplet, then click Create Droplet.
Wait for your droplet to spin up — you’ll get a public IP address once it’s ready.
Step 2: Connect to Your Droplet via SSH
Open your local terminal and connect to your droplet using its public IP:
ssh root@your_droplet_ip_here
If you added an SSH key, you’ll connect immediately. If you chose password authentication, enter the root password DigitalOcean sent to your email.
First, update your droplet’s system packages to avoid security gaps:
sudo apt update && sudo apt upgrade -y
Step 3: Install Node.js on Your Droplet
We’ll use the NodeSource repository to install the latest Node.js LTS version:
curl -fsSL https://deb.nodesource.com/setup_lts.x | sudo -E bash -
sudo apt install -y nodejs
Verify the installation with:
node -v
npm -v
You should see version numbers for both tools.
Step 4: Upload Your Node.js App to the Droplet
The easiest way to get your app on the droplet is via Git. First, install Git:
sudo apt install git -y
Clone your app’s repository (replace the URL with your own):
git clone https://github.com/your-username/your-node-app.git
Navigate to your app directory and install dependencies:
cd your-node-app
npm install
Test that your app runs correctly:
node app.js
Visit http://your_droplet_ip:3000 in your browser — you should see your app. Note that this process will stop when you close your terminal, which is why we’ll use PM2 next.
Step 5: Set Up PM2 to Manage Your Node.js App
PM2 is a process manager that keeps your Node.js app running in the background, restarts it if it crashes, and sets it to launch on server reboot.
Install PM2 globally:
sudo npm install -g pm2
Start your app with PM2 (replace app.js with your app’s entry point):
pm2 start app.js --name "my-node-app"
Save your PM2 process list so it persists after reboot:
pm2 save
Set up PM2 to start automatically on boot:
pm2 startup
Follow the command output PM2 provides (it will usually be a sudo command to set up systemd) then run pm2 save again.
Step 6: Configure Nginx as a Reverse Proxy
Node.js apps typically run on port 3000, but we want users to access your app via standard port 80 (HTTP) or 443 (HTTPS). Nginx will forward incoming requests to your Node.js app.
Install Nginx:
sudo apt install nginx -y
Adjust your firewall to allow Nginx and SSH traffic:
sudo ufw allow 'Nginx Full'
sudo ufw allow OpenSSH
sudo ufw enable
Create a new Nginx configuration file for your app:
sudo nano /etc/nginx/sites-available/my-node-app
Paste the following configuration (replace your_domain_or_ip with your droplet’s IP or domain name):
server { listen 80; server_name your_domain_or_ip; location / { proxy_pass http://localhost: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; } }
Save and close the file (Ctrl+O, Ctrl+X if using nano). Enable the site by creating a symbolic link:
sudo ln -s /etc/nginx/sites-available/my-node-app /etc/nginx/sites-enabled/
Test your Nginx configuration for errors:
sudo nginx -t
Restart Nginx to apply changes:
sudo systemctl restart nginx
Visit http://your_droplet_ip in your browser — your Node.js app should now load without specifying a port. For advanced Nginx configuration options, consult the official Nginx documentation.
Step 7: Set Up SSL with Let’s Encrypt
Let’s Encrypt provides free, auto-renewing SSL certificates to secure your app. You’ll need a domain name pointed to your droplet’s IP for this step (it’s not required to run your app, but is mandatory for SSL).
Install Certbot, the Let’s Encrypt client for Nginx:
sudo apt install certbot python3-certbot-nginx -y
Run Certbot and follow the prompts:
sudo certbot --nginx -d your_domain -d www.your_domain
Certbot will automatically update your Nginx configuration to redirect HTTP traffic to HTTPS, and set up auto-renewal. Test the renewal process with:
sudo certbot renew --dry-run
Common Troubleshooting Tips
- App not loading? Check PM2 logs with
pm2 logs my-node-appto see errors. - 502 Bad Gateway error? Check Nginx error logs:
sudo tail -f /var/log/nginx/error.log. - Can’t connect to the droplet? Verify your firewall settings with
sudo ufw status. - SSL not working? Ensure your domain’s DNS is fully propagated, and check Certbot logs for errors.
FAQ: DigitalOcean Node.js Deploys
Can I deploy multiple Node.js apps on one DigitalOcean droplet?
Yes! Assign each app a unique port, create separate Nginx server blocks for each, and manage them all with PM2.
Do I need a domain to complete a DigitalOcean Node.js deploy?
No — you can access your app via your droplet’s public IP address. A domain is only required if you want to set up SSL certificates.
How do I update my Node.js app after deployment?
Pull the latest changes from your Git repository, run npm install to update dependencies, then restart your app with pm2 restart my-node-app.
Is DigitalOcean a good choice for production Node.js apps?
DigitalOcean is a cost-effective, flexible option for small to medium Node.js apps. You’ll need to handle server maintenance yourself, but you get full control over your environment.
Conclusion
A DigitalOcean Node.js deploy is far less intimidating than it seems once you break it into clear steps. You now have a live, SSL-secured Node.js app running on a managed VPS, with automatic restarts and reverse proxy configuration.
Have you deployed a Node.js app on DigitalOcean before? Share your tips or troubleshooting tricks in the comments below! For more server management guides, consider checking out our upcoming post on securing DigitalOcean droplets for production use.
Comments are closed, but trackbacks and pingbacks are open.