Log in
creativeleaf
Updated on February 9, 2026

How to fix “503 Service Unavailable” in Node.js hosting?

Introduction

Seeing a “503 Service Unavailable” error after deploying your Node.js app can be alarming, but don’t worry, it’s a common issue in shared hosting environments. On BigCloudy Node.js Hosting, this typically occurs when the application fails to start or respond correctly under CloudLinux and Passenger (Phusion Passenger), which manage Node.js processes in a shared hosting setup.

In this guide, you’ll learn why the 503 error happens, how to fix it step by step, and best practices to prevent it in future deployments. We’ll cover everything from checking resource usage and verifying Node.js versions, to reinstalling dependencies and properly configuring your startup file. By following these steps, you can ensure your Node.js applications run reliably on BigCloudy Node.js hosting, with minimal downtime and better stability.

What Does “503 Service Unavailable” Mean in Node.js?

A 503 Service Unavailable error in Node.js means that your application is not running or responding when the web server tries to connect.
In shared hosting with CloudLinux + cPanel + Passenger, your Node.js app doesn’t run continuously — instead, Passenger spawns the app when it’s first accessed. If something fails during startup (like missing dependencies or version mismatch), cPanel shows a 503 response.

Common Causes of 503 Service Unavailable in Node.js on cPanel

Here are the most common reasons behind this issue:

  1. Node.js Application Crash :

    The app stopped due to code errors, syntax bugs, or missing modules.
    Example: missing express or broken import path.

  2. Node.js Version Mismatch

    You’re using a different Node.js version locally (e.g., v20) and cPanel is configured for another (e.g., v18).

  3. Resource Limits Reached (CloudLinux)

    CPU, memory, or entry process limits are maxed out.

  4. Incorrect Startup File in cPanel

    The wrong entry file (like server.js instead of app.js) is selected.

  5. Port Conflict or Wrong Port Binding

    Passenger handles ports internally — you don’t need to manually use 3000, 8080, etc.

  6. Incomplete Deployment or Missing Dependencies

    You uploaded files manually but forgot to run npm install inside cPanel.

  7. Corrupted or Incomplete ZIP Uploads

    Missing package.json, node_modules, or environment files after extraction.

Step-by-Step Fix for 503 Error in Node.js on cPanel

Step 1: Check Resource Usage (CloudLinux Limits)

  1. Log in to your cPanel dashboard.
  2. Go to Metrics → Resource Usage.
  3. Look for CPU, Memory, or Entry Processes hitting 100%.
    • If they are maxed out, either optimize your app or upgrade your plan.
cPanel login page
Resources high nodejs Bigcloudy
Note: CloudLinux suspends applications that exceed their resource limits to maintain server stability.

Step 2: Open Node.js App Setup and Verify Configuration

  1. Search for “Setup Node.js App” in cPanel.
    1. Verify:
      • Application root directory is correct.
      • The startup file (e.g., app.js or server.js) is correct.
      • The Node.js version matches what you used in local development.

        Keep Node.js versions consistent between local and server (e.g., both using Node.js 22.x).

Virtual Env URL Bigcloudy

Step 3: Open Terminal in cPanel

  1. Search for Terminal in cPanel,
  2. Click Terminal.
  3. Copy NodeJS app virtual environment URL and paste it in the terminal:
				
					# source /home/cpanelusername/nodevenv/yourdomain.com/24/bin/activate
&& cd /home/cpanelusername/yourdomain.com

Navigate to your app directory:

4. Verify your package.json exists in this folder.

Virtual Env URL Bigcloudy

Step 4: Reinstall Missing Dependencies

  1. Sometimes, uploaded ZIPs don’t include node_modules. Run:

    If logs mention a missing module (like express), run:

				
					# npm install

# npm install express
cPanel terminal image Bigcloudy

Step 5: Check for Port Conflicts

  1. You generally shouldn’t specify a port manually on shared hosting. Passenger manages this automatically.
    If you’ve hardcoded a port in your script (like app.listen(3000)), replace it with:
				
					const PORT = process.env.PORT || 3000; 

app.listen(PORT);

This ensures compatibility with cPanel’s internal Passenger port binding.

To check if a port is stuck: 

				
					# lsof -i:3000 

# kill -9 <PID>

Step 6: Review Logs for Errors

Setup Node.js App → Edit → Logs.

    Check for:
    • Syntax errors
    • Missing dependencies
    • Invalid file paths
    • Permission issues

If you see Error: Cannot find module ‘express’  reinstall the missing dependency.

Step 7: Restart the Node.js Application

    1. After fixes, restart the app:

      1. Go to Setup Node.js App → Edit.
      2. Click Stop, wait a few seconds, then Start again.

        Alternatively, from the terminal:

				
					npm start

If the app runs fine, reload the browser, the 503 error should be gone.

How to Prevent 503 Errors in Future Deployments?

  1. Use a version manager locally (like nvm) to match the exact Node.js version in cPanel.
  2. Keep your startup file path simple — avoid nested directories.
  3. Monitor resource usage regularly from cPanel.
  4. Use environment variables instead of hard-coded ports.
  5. Deploy with Git or FTP instead of ZIPs when possible.

Why CloudLinux & Passenger Matter?

  1. Shared hosting servers often run CloudLinux + Passenger.

    • CloudLinux isolates each account in a “Lightweight Virtual Environment (LVE)” to prevent one user from consuming all server resources.
    • Passenger (also known as Phusion Passenger) serves Node.js, Python, and Ruby apps under Apache or Nginx.

    While this setup is efficient, it means your app isn’t persistent if it crashes, and it won’t auto-restart until accessed again. That’s why monitoring and correct configuration are crucial.

Hosting Built for Node.js Developers

  1. If you frequently deploy Node.js apps, shared hosting may not always be ideal. Consider upgrading to a CloudLinux VPS with full Node.js support, which includes:

    • Node.js version selector
    • SSH & full terminal access
    • Real-time resource monitoring
    • Persistent background processes
    • Root access for advanced debugging

    You can explore Node.js hosting plans optimized for Passenger environments, which provide better uptime and fewer 503 interruptions.

Conclusion

 

A 503 Service Unavailable error on Node.js shared hosting usually indicates a startup or configuration failure rather than a server outage. In cPanel environments using CloudLinux and Passenger, common causes include missing dependencies, incorrect startup files, Node.js version mismatches, resource limits, or improper port handling.

By checking resource usage, confirming app settings, reinstalling dependencies, reviewing logs, and restarting the application, most 503 errors can be resolved quickly. Consistent Node.js versions, proper use of environment variables, and careful deployment practices reduce the chance of recurrence. For applications that require persistent processes or higher resource limits, moving beyond shared hosting may be necessary.

Need Help?

If you require assistance at any point while using this guide, our Support Team is here to help:

FAQ

Why do I see “503 Service Unavailable” after uploading my Node.js app?

Because the app isn’t running or Passenger failed to start it. Usually caused by a version mismatch or missing module.

Does Node.js run 24/7 on shared hosting?

No. In cPanel shared hosting, Node.js apps start when accessed and stop after inactivity or errors.

How do I change the Node.js version in cPanel?

Go to Setup Node.js App → Edit → Node.js version, select your desired version, and click Save.

Can I run multiple Node.js apps under one cPanel account?

Yes, but each app must be configured separately with its own directory and startup file.

How do I monitor my Node.js app logs in cPanel?

Go to Setup Node.js App → Edit → Logs or use the terminal to view real-time logs.

What if the 503 error still appears after all fixes?

Try restarting the app, reinstalling dependencies, or contacting your hosting support to check for CloudLinux throttling.

Powered By BigCloudy

Copyright Ⓒ 2026 BigCloudy Internt Services Pvt. Ltd. All Rights Reserved