How to Install Node.js on cPanel

Node.js on Shared vs VPS: What Is Possible

Yes, where the plan includes it — and the boundary is worth knowing. Shared cPanel with Setup Node.js App runs one or more Node applications behind Passenger: pick a Node version, point at an application root and startup file, run npm install from the UI, and the app serves on your domain.

What the panel model cannot give. PM2's process dashboard and clustering, long-lived WebSockets beyond Passenger's model, background workers and queues, native modules requiring build chains, or Node versions via nvm that the selector does not offer. Those needs are the graduation signal to a VPS — the cPanel-on-VPS route keeps the panel while adding the freedom.

Step 1: Open Setup Node.js App

Open Setup Node.js App. Do this on one site or a staging copy first, then check the public URL in a private window so cache does not hide the result. Stop if the page errors, and email support@webji.services with the step name and the exact error before you repeat it on every account. WebJi® support mail is staffed 24/7 in Hindi and English; the phone line +91 141 4941811 is business hours only.

Step 2: Create the App (Version, Folder, Startup File)

Create the App (Version, Folder, Startup File). Do this on one site or a staging copy first, then check the public URL in a private window so cache does not hide the result. Stop if the page errors, and email support@webji.services with the step name and the exact error before you repeat it on every account. WebJi® support mail is staffed 24/7 in Hindi and English; the phone line +91 141 4941811 is business hours only.

Step 3: Upload Code and Run npm install

Step two: get code and dependencies in.

1. Upload the project into the Application Root — zip-upload-extract via File Manager, or SFTP with your cPanel credentials — ensuring package.json sits at the root of that folder.
2. Delete the sample app.js cPanel created if your project replaces it.
3. Back in Setup Node.js App, click Run NPM Install on the application row: cPanel executes npm install into a node_modules the environment manages.
4. If install fails, open the app's detail view and check the reported error — missing build tools for a native module (node-gyp needs compilers shared hosting rarely has) is the classic wall; the fix is a pure-JS alternative dependency or a VPS.
5. Set environment variables in the app's detail view, then Restart — the flag in the list reminds you when code changed without one.

Step 4: Run, Stop and Restart via the UI

On package.json, the honest summary is that defaults matter more than brand names — a well-set budget plan outranks a mis-tuned premium one. WebJi® documents its defaults openly and adjusts them per ticket when workloads need it.

Environment Variables and Logs

How this plays out with startup file (app.js): settings that look cosmetic usually decide page speed and uptime under real traffic. The defaults WebJi® ships are tuned for Indian network conditions, and support can review your setup on request.

Node App Not Working: Common Fixes

The ordered checklist:

• 404/empty at the URL — the startup file name in the form does not match your entry script (bin/www versus app.js); fix the field, and confirm files actually sit in the Application Root, not one folder deeper after a zip extraction.

• Passenger error 500 or App spawner errored — the app crashed at boot: check the log output in the app view; typical causes are an unhandled exception in the entry file, a skipped or failed NPM Install, or the app listening on a hard-coded port — replace app.listen(3000) with app.listen(process.env.PORT || 3000) so Passenger's supplied port wins.

• Module not found despite install — node_modules landed in the wrong folder; package.json must be exactly at the Application Root when NPM Install runs.

• Changed code but nothing new served — you did not Restart after upload.