{"id":4467,"date":"2026-09-12T17:32:58","date_gmt":"2026-09-12T12:02:58","guid":{"rendered":"https:\/\/cpanelfree.com\/blog\/how-to-deploy-nextjs-ssr-linux-vps-pm2\/"},"modified":"2026-09-17T11:23:52","modified_gmt":"2026-09-17T05:53:52","slug":"how-to-deploy-nextjs-ssr-linux-vps-pm2","status":"publish","type":"post","link":"https:\/\/cpanelfree.com\/blog\/how-to-deploy-nextjs-ssr-linux-vps-pm2\/","title":{"rendered":"How to Deploy Next.js SSR Web Applications on Linux VPS with PM2 & Standalone Output"},"content":{"rendered":"

Next.js is the dominant React framework for building modern, search-engine-optimized web applications. However, hosting Next.js applications on commercial serverless platforms like Vercel often results in exorbitant monthly invoices as soon as traffic scales. High bandwidth egress markups, arbitrary serverless execution function timeouts, and costly concurrency seat limits penalize growing applications.<\/p>\n

By leveraging Next.js\u2019s built-in standalone build output<\/strong>, you can package an entire Next.js SSR application into an ultra-lean Node.js bundle that runs on an affordable Linux VPS<\/a>. Paired with PM2 process manager<\/strong> and an Nginx reverse proxy, self-hosting Next.js delivers continuous sub-20ms SSR response times, eliminates cold-start latency, and reduces infrastructure costs by up to 90%<\/strong>.<\/p>\n

1. Enabling Standalone Build Output in next.config.js<\/h2>\n

By default, a Next.js build requires your entire node_modules<\/code> folder\u2014often weighing several gigabytes. The standalone feature traces your project’s import tree and compiles only the strict dependencies required for production into a lightweight .next\/standalone<\/code> folder.<\/p>\n

Open next.config.js<\/code> (or next.config.mjs<\/code>) and enable standalone mode:<\/p>\n

\/** @type {import('next').NextConfig} *\/\nconst nextConfig = {\n  output: 'standalone',\n  poweredByHeader: false,\n  reactStrictMode: true,\n};\n\nmodule.exports = nextConfig;<\/code><\/pre>\n
Execute the production build on your local machine or CI\/CD runner:<\/p>\n
npm run build<\/code><\/pre>\n
Next.js creates an optimized self-contained web server at .next\/standalone\/server.js<\/code> weighing less than 80MB.<\/p>\n
2. Preparing the Production Linux VPS & Node.js Runtime<\/h2>\n
Log in to your VPS as a non-root administrative user and install Node.js 20 LTS alongside PM2:<\/p>\n
# Install NodeSource repository and Node.js\ncurl -fsSL https:\/\/deb.nodesource.com\/setup_20.x | sudo -E bash -\nsudo apt install -y nodejs nginx\n\n# Install PM2 process manager globally\nsudo npm install -g pm2<\/code><\/pre>\n
Create the target application deployment directory:<\/p>\n
sudo mkdir -p \/var\/www\/my-nextjs-app\nsudo chown -R $USER:$USER \/var\/www\/my-nextjs-app<\/code><\/pre>\n
3. Transferring Artifacts & Managing Static Assets<\/h2>\n
To run a standalone Next.js build, you must deploy three specific folders to \/var\/www\/my-nextjs-app<\/code>:<\/p>\n
    \n
  1. The entire contents of .next\/standalone\/<\/code><\/li>\n
  2. The public\/<\/code> folder (copied into \/var\/www\/my-nextjs-app\/public\/<\/code>)<\/li>\n
  3. The compiled static assets from .next\/static\/<\/code> (copied into \/var\/www\/my-nextjs-app\/.next\/static\/<\/code>)<\/li>\n<\/ol>\n
    Sync these folders efficiently via rsync<\/code>:<\/p>\n
    # Run from your local repository\nrsync -avz --delete .next\/standalone\/ deployer@your-vps-ip:\/var\/www\/my-nextjs-app\/\nrsync -avz --delete public\/ deployer@your-vps-ip:\/var\/www\/my-nextjs-app\/public\/\nrsync -avz --delete .next\/static\/ deployer@your-vps-ip:\/var\/www\/my-nextjs-app\/.next\/static\/<\/code><\/pre>\n
    4. Configuring PM2 Process Manager Ecosystem<\/h2>\n
    Create an ecosystem.config.js<\/code> file in \/var\/www\/my-nextjs-app\/<\/code> to manage multi-core clustering and automatic restarts:<\/p>\n
    module.exports = {\n  apps: [\n    {\n      name: 'nextjs-production',\n      script: 'server.js',\n      cwd: '\/var\/www\/my-nextjs-app',\n      instances: 'max', \/\/ Scales across all available CPU cores in cluster mode\n      exec_mode: 'cluster',\n      env: {\n        NODE_ENV: 'production',\n        PORT: 3000,\n        HOSTNAME: '127.0.0.1',\n      },\n      max_memory_restart: '512M',\n      listen_timeout: 10000,\n      kill_timeout: 5000,\n    },\n  ],\n};<\/code><\/pre>\n
    Start the application cluster and save the systemd boot startup hook:<\/p>\n
    cd \/var\/www\/my-nextjs-app\npm2 start ecosystem.config.js\npm2 save\nsudo env PATH=$PATH:\/usr\/bin pm2 startup systemd -u $USER --hp \/home\/$USER<\/code><\/pre>\n
    5. Nginx Reverse Proxy & Static Asset Caching<\/h2>\n
    Configure Nginx to terminate SSL and serve immutable static files directly from disk without invoking Node.js worker cycles:<\/p>\n
    server {\n    listen 80;\n    listen 443 ssl http2;\n    server_name yourdomain.com;\n\n    ssl_certificate \/etc\/letsencrypt\/live\/yourdomain.com\/fullchain.pem;\n    ssl_certificate_key \/etc\/letsencrypt\/live\/yourdomain.com\/privkey.pem;\n\n    # Serve Next.js static chunks directly from disk with 1-year immutable caching\n    location \/_next\/static\/ {\n        alias \/var\/www\/my-nextjs-app\/.next\/static\/;\n        expires 365d;\n        access_log off;\n        add_header Cache-Control \"public, max-age=31536000, immutable\";\n    }\n\n    # Serve public static assets directly\n    location \/public\/ {\n        alias \/var\/www\/my-nextjs-app\/public\/;\n        expires 30d;\n        access_log off;\n    }\n\n    # Proxy dynamic SSR requests to PM2 Node.js cluster\n    location \/ {\n        proxy_pass http:\/\/127.0.0.1:3000;\n        proxy_http_version 1.1;\n        proxy_set_header Upgrade $http_upgrade;\n        proxy_set_header Connection 'upgrade';\n        proxy_set_header Host $host;\n        proxy_set_header X-Real-IP $remote_addr;\n        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;\n        proxy_set_header X-Forwarded-Proto $scheme;\n        proxy_cache_bypass $http_upgrade;\n    }\n}<\/code><\/pre>\n
    5. Zero-Downtime Rolling Deployments with PM2 Reload & Git Hooks<\/h2>\n
    Deploying application updates to production without interrupting active user sessions is critical for modern Next.js deployments. Instead of executing pm2 restart<\/code>, which terminates the existing process before starting the new one, configure graceful zero-downtime reloads:<\/p>\n