how can make the pm2 config file works in the deno for the nextjs project?

[BertramYe]

hello, when I trying to customised an pm2 config file (ecosystem.config.js) to help host the nextjs project with the details here below:

I found that the url can't be works even the pm2 shows no error, just like here below:

1. fisr of all, when I tried with the commend of the deno run start, it works file when I visit the url: http://localhost:3000/

but when I customsed an ecosystem.config.js for pm2 here below:
and start with the commend, just like here below:

// ecosystem.config.js
// ecosystem.config.js
module.exports = {
  apps: [{
    // application names
    name: 'blog',

    script:"deno",
    interpreter: 'deno', // deno interpreters
    interpreterArgs: 'run start --compat --unstable --allow-read --allow-env --allow-net', // enviroments
    cwd: './',
    
    instances: 1,
    exec_mode: 'cluster', 
    autorestart: true,
    restart_delay: 3000,
    max_restarts: 10,
    
    // moniter
    watch: true, 
    ignore_watch: [
      'node_modules',
      '.next',
      'logs',
      '*.log',
      '*.tmp'
    ],
    
    // memory
    max_memory_restart: '800M',
    
    // logs
    log_date_format: 'YYYY-MM-DD HH:mm:ss',
    error_file: './logs/error.log',
    out_file: './logs/output.log',
    pid_file: './logs/nextjs.pid',
    
    // enviroment
    env: {
      NODE_ENV: 'production',
      PORT: 3000,
      HOST: '0.0.0.0',
      NEXT_TELEMETRY_DISABLED: '1',
    }
  }]
};

but when I try to visit the page: http://localhost:3000/ and found, it dosen't works anymore,

and also as you can see, it works fine without any errors shows

how can I make it works?

os: windows 10
deno 2.6.3+ce1d451 (canary, release, x86_64-pc-windows-msvc)
v8 14.2.231.17-rusty
typescript 5.9.2
pm2: 6.0.14
nextjs: 16.1.1

[ismaildasci]

Hey! The issue is with how you're configuring the script and interpreter fields - they're conflicting with each other.

When you set both script: "deno" and interpreter: "deno", PM2 gets confused because it's essentially trying to run deno deno run start ... which doesn't work.

Here's what should work:

module.exports = {
  apps: [{
    name: 'blog',
    script: 'npm',
    args: 'run start',
    cwd: './'  ,
    instances: 1,
    exec_mode: 'fork',  // use fork mode, cluster doesn't work well with Deno
    autorestart: true,
    restart_delay: 3000,
    max_restarts: 10,
    watch: false,  // recommend disabling in production
    max_memory_restart: '800M',
    log_date_format: 'YYYY-MM-DD HH:mm:ss',
    error_file: './logs/error.log',
    out_file: './logs/output.log',
    env: {
      NODE_ENV: 'production',
      PORT: 3000,
      HOST: '0.0.0.0',
      NEXT_TELEMETRY_DISABLED: '1'
    }
  }]
};

A few things I changed:

1. Removed the interpreter stuff - just let PM2 call npm run start directly (or deno task start if you have that set up)
2. Changed to fork mode - cluster mode doesn't play nice with Deno since it uses Node's cluster module internally
3. Disabled watch - generally better for production; you can enable it for dev if needed

Alternatively, if you want to call deno directly:

script: 'deno',
args: 'task start',
interpreter: 'none',

The interpreter: 'none' is key here - it tells PM2 not to wrap the command with another interpreter.

Also heads up: the --compat flag was removed in Deno 2.x, so you don't need that anymore.

Let me know if this works!

[BertramYe]

ok, got it, @ismaildasci , thanks for your explain， I will check and have a try later, much appreciate.

[aniruddhaadak80]

@BertramYe You are very close - the key detail is that PM2 must run the correct interpreter/entry command.

For a Next.js app, the most stable production path is usually Node (
ext start) instead of trying to run Next itself with Deno runtime.

If this is a Deno app under PM2, set interpreter and args explicitly (for example deno +
un -A server.ts).

References:

• https://docs.deno.com/runtime/manual
• https://nextjs.org/docs/app/building-your-application/deploying

[BertramYe]

@aniruddhaadak80 ok, but just from the docs, I didn't get any description on the PM2 deployments for the Deno of the Nextjs, have you ever tried with them?