PM2 Start Internal Server Error

Open
#5,531 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
25/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Stale
Tech stack
javascript, node.js
Domain
backend, cli

Research direction

Reproduce the reported setup by cloning, installing, and building the repository, then compare pm2 start file.js from outside the repository with npm run start. Check how each command starts the application and confirm completion when the application is accessible without an internal server error.

Written by the indexing model from the issue text.

Description

What's going wrong?

I did pm2 start file.js but it turned Internal server error when accessed. But when I am trying npm run start on the repo, it worked normally.

How could we reproduce this issue?

Clone a repo from git, and then fetch, pull, install and build with sudo. After everything completed, run pm2 start file.js on the outside folder of the repo. Then access the web.

Supporting information

pm2 version 5.2.2
node.js version 16.19.0
npm version 6.14.4
Dominant language
JavaScript
Stars
43.3k
Forks
2.7k
No merged PRs in 30d

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from Unitech/pm2

All issues in Unitech/pm2

Similar issues

More JavaScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.