Skip to main content

​
Deploying Node.js Applications on Your Hosting

NEW Feature — Node.js application hosting is now available on FREAKHOSTING web hosting accounts. You can deploy, manage, and monitor Node.js applications directly from the Web Hosting Control Panel at web.freakhosting.com, alongside your existing websites and domains.
Node.js allows you to run server-side JavaScript applications on your hosting account. Whether you are building an API, a real-time chat application, a custom web app, or a backend service, you can now deploy and manage it all from your control panel without needing a separate server or VPS.

Difficulty

Intermediate

Time

10 Minutes

​
A Practical Example

Let’s say you have built a simple Node.js application — maybe a contact form handler that receives form submissions from your website and sends email notifications. Your app has an app.js file, a package.json, and a node_modules folder. Right now it only runs on your local machine. Here is what deploying it to FREAKHOSTING looks like in plain terms:
  1. You upload your app files to a folder on your hosting account.
  2. You tell the control panel which file starts your app (app.js).
  3. You choose a URL path where the app will be reachable (like /contact-api).
  4. You click deploy, and the system starts your app, keeps it running, and makes it accessible to the world.
That is it. No command line, no SSH, no server configuration files. The rest of this guide walks you through each step in detail.

​
Accessing the Node.js Manager

The Node.js application manager is located inside the Advanced section of your website’s control panel.
1

Log In to the Control Panel

Go to web.freakhosting.com and log in with your FREAKHOSTING credentials.
2

Select Your Website

From the dashboard or website list, click on the website where you want to deploy a Node.js application.
3

Open the Advanced Dropdown

In the navigation area for your website, click on the Advanced dropdown to expand additional options.
4

Click Node.js

Select Node.js from the dropdown menu. You will notice it has a green NEW badge, highlighting that this is a recently added feature. This opens the Node.js application manager for your website.
If you have not deployed any Node.js applications yet, you will see an empty state with a server icon, the message No applications defined, and a cyan Deploy app button. This is completely normal and simply means you are ready to deploy your first application.

​
Deploying a Node.js Application

Once you have uploaded your Node.js application files to your hosting account (via File Manager or FTP), you can deploy it through the control panel.
1

Open the Node.js Manager

Navigate to Advanced dropdown and select Node.js as described above.
2

Click Deploy App

Click the cyan Deploy app button. This opens the application configuration form where you will set up all the details for your Node.js application.
3

Set the Start File

In the Start file field, enter the filename that starts your application. This is the main entry point of your Node.js app, typically something like app.js, server.js, or index.js. This is the file that Node.js will execute when your application starts.
4

Set the Application Path

In the Path field, enter the directory path where your Node.js application files are located on the server. This tells the control panel where to find your application code.
5

Configure Auto-Start

The Auto-start option determines whether your Node.js application starts automatically when the server restarts. Enable this if you want your application to always be running without manual intervention — which you almost certainly do for anything beyond testing.
6

Configure Monitoring

The Monitoring option enables automatic monitoring of your application. When turned on, the system will watch your application and automatically restart it if it crashes or stops unexpectedly. This is your safety net — if your app hits an unexpected error and goes down at 3am, the system will bring it right back up.
7

Set the Web Server Proxy Path

This is where you decide how visitors will reach your Node.js application. The proxy path is the URL path on your domain that will route traffic to your Node.js app.In plain English: Your Node.js app runs on its own internal port that is not directly accessible from the internet. The web server acts as a middleman — when a visitor goes to yourdomain.com/api, the web server intercepts that request and passes it along to your Node.js app behind the scenes. This is called “proxying.” Your visitors never know the difference; they just see a normal URL.For example, setting the proxy path to /api means your application will be available at yourdomain.com/api. Setting it to / makes your Node.js app the primary application for your entire domain. Choose a path that makes sense for your use case.
8

Deploy the Application

Review all of your settings and click the button to deploy. Your Node.js application will be started and made accessible at the configured path.
Make sure your start file exists. If the start file you specified does not exist at the application path, the deployment will fail and your application will not start. Double-check that your application files are uploaded to the correct directory before deploying.
Enable both Auto-start and Monitoring for production applications. Auto-start ensures your app comes back online after server maintenance or restarts, while Monitoring ensures it is automatically restarted if it crashes during normal operation. Together, they keep your application running reliably around the clock — even if something goes wrong at 3am when you are fast asleep.

​
Managing Your Node.js Applications

Once you have deployed one or more Node.js applications, they will appear in a list on the Node.js manager page. From here you can perform several management actions.

​
Starting, Stopping, and Restarting

Start

Launches your Node.js application if it is currently stopped. Use this after making changes or after manually stopping the app.

Stop

Gracefully shuts down your running Node.js application. Use this when you need to make changes to your code or configuration.

Restart

Stops and immediately restarts your application. This is the quickest way to apply code changes without manually stopping and starting.
1

Open the Node.js Manager

Go to Advanced dropdown and select Node.js.
2

Find Your Application

Locate the application you want to manage in the list of deployed applications.
3

Use the Action Buttons

Click the Start, Stop, or Restart button for the application you want to control. The action takes effect immediately.
After making code changes to your Node.js application, you will need to Restart the application for those changes to take effect. Unlike PHP (which re-reads files on every request), Node.js applications run as persistent processes and do not automatically pick up file changes. Think of it like restarting a desktop app after an update — you need to close and reopen it to get the new version.

​
Viewing Application Logs

Logs are essential for understanding what your Node.js application is doing, diagnosing errors, and troubleshooting issues.
1

Open the Node.js Manager

Navigate to Advanced dropdown and select Node.js.
2

Access Logs for Your Application

Find your application in the list and click on the Logs option. This will display the recent output from your Node.js application, including any messages your app writes to the console and any error messages.
Check your logs first when something goes wrong. If your application is not starting, is crashing, or is behaving unexpectedly, the logs will almost always contain error messages that explain what happened. Common things you will see include missing module errors (meaning you need to run npm install), syntax errors, or port conflict messages. Review the log output before reaching out to support — it will save you time and often points you straight to the fix.

​
The Empty State — No Applications Defined

When you first visit the Node.js manager, before deploying any applications, you will see a screen showing a server icon graphic and the message No applications defined. This is not an error. It simply means your account is ready and waiting for you to deploy your first Node.js application. To get started, click the cyan Deploy app button and follow the deployment steps described above.

​
Frequently Asked Questions

You can upload your application files using the File Manager in the control panel or by connecting via FTP/SFTP. Upload all of your application files (including package.json and your start file) to the directory you plan to specify as the application path during deployment.
The control panel may handle dependency installation automatically depending on your configuration. If your application is not starting because of missing modules, check whether a node_modules folder exists in your application directory. You may need to install dependencies before deploying. Check your application logs for any “Cannot find module” errors — that is a telltale sign.
Yes. You can deploy multiple Node.js applications and proxy each one from a different URL path. For example, one application at /api and another at /dashboard. Each application runs as a separate process with its own start file and configuration.
If you have Monitoring enabled, the system will automatically detect the crash and restart your application — usually within seconds. If Monitoring is not enabled, your application will remain stopped until you manually start it again from the Node.js manager. This is why we strongly recommend enabling Monitoring for any production application.
Upload the updated files to your application directory (replacing the old files), then go to the Node.js manager and click Restart on your application. The restart will load the new code. Remember, Node.js apps are persistent processes, so just uploading new files is not enough — you need to restart for changes to take effect.
The available Node.js version options depend on your hosting account configuration. Check the deployment form for any version selection options when deploying your application.
Check the application Logs in the Node.js manager for error messages. Common causes include a missing start file, missing dependencies (run npm install), syntax errors in your code, or the application listening on the wrong port.
Your Node.js app runs on an internal port that is not directly accessible from the internet. The web server (OpenLiteSpeed) sits in front of it and forwards incoming requests to your app based on the URL path you configured. So when someone visits yourdomain.com/api, the web server grabs that request and passes it to your Node.js app. This is called “reverse proxying” and it means your visitors just use a normal URL — they never need to know about internal ports or how things work behind the scenes.

​
Need Extra Help?

If you encounter any issues, our support team is ready to assist:

​
Save on Your Hosting

Ready to launch your website? Use code KB20 at checkout for 20% off your first month!
Last Updated: March 2026 | Web Hosting Support: Node.js application deployment made simple.