Many of the latest web frameworks (such as Node.js) don’t directly integrate into Parallels Plesk or any of the other web control panel systems. However, if you’ve setup the framework and have it running on your VPS, you can still take advantage of Plesk to manage your system. This is also applicable if you have a standalone application which provides a native HTTP interface and need to run it through your standard server.

One way to achieve this is to take advantage of the Apache mod_proxy to present this by proxying it through your existing website. This way, it will run on the standard port 80 and you can run other websites along side it.

Instructions

1. After logging into Plesk, select the domain you want to add the proxy to.
2. If it’s not already expanded, select the Show More link:
   
3. Click on the Web Server Settings button in the expanded view:
   
4. Under the Additional Apache directives, you can then add the following code:

   <Location />
       ProxyPass https://localhost:4321/
       ProxyPassReverse https://localhost:4321/
   </Location>

   This assumes your Node.js (or similar backend system) is listening on port 4321 on the localhost. If you have specified a different port number in your application, you’ll need to ensure it matches here. The result should look like this:
   

   You can also just specify a certain directory to proxy, eg “<Location /test1>” and this will only proxy requests for /test1.

5. Click on the OK button to save the config and force Apache to reload it. You should then be able to view your application from a browser with it being proxied through Apache.

Now that Plesk Onyx and Obsidian natively support Node.js, you can run your applications without any manual changes or hacks to your existing systems. This includes services such as Express, Next.js, Meteor and derivatives which require some server side JavaScript rendering.

Supported versions of node will vary based on the underlying operating system, please contact Conetix to confirm the available versions for your system.

The instructions below will step you through the process of deploying and configuration the application.

Conetix does not support Node.js on shared hosting plans. You will need a Virtual Private Server in order to achieve this.

Prerequisites

1. Own VPS with Plesk installed
2. Plesk root or administrator Login
3. Node.js Plesk Extension installed

Instructions

1. Login to Plesk.
2. Select the domain you wish to run your Node.js, then select Node.js:
   
3. Enter the details about the app:
   
   This needs to include:
   1. Document Root (location of the static assets to be served by the app)
   2. Application Root (the location of your app files, eg what contains the app.js and libraries)
   3. The application startup file (typically app.js, server.js or similar)
   4. Any Custom environment variables required to run the app (if any)
4. After you’ve received confirmation that the Startup File exists, you then need to enable Node.js:
   

Diagnosing issues

If your application fails to start or it’s having an issue, you can enable the debug mode to get further details.

1. Within the Node.js area, set the Application Mode to development:
   
2. If your application fails to start, you should now see a larger error message with further information:
   
3. If the brief message isn’t sufficient to diagnose, click on Detailed diagnostics to get a detailed view of what’s going on.

Startup Files

Some Node.js will need a separate startup file. For example, if you run Frontity, you can create a startup file similar to:

var frontity = require("./server").default;
var http = require(‘http’);
var server = http.createServer(frontity);
server.listen(process.env.PORT);

This will need to be saved to a file, eg startapp.js and set as the Application Startup File in the Plesk Node.js configuration.

The files uploaded should generally be compiled or packaged files. Most frameworks provide you with a build command to produce these files. Uploading the entire app may result in errors for some frameworks.