Knowledge Base

Managing Node.js in Thamara

Managing Node.js in Thamara

Using the Node.js extension, you can:

     ◦ Enable Node.js for a domain or subdomain.

     ◦ Upload and run your app (e.g., Express.js, Next.js, etc.).

     ◦ Manage environment variables.

     ◦ Restart or stop your app from Plesk.

  • Accessing the Node.js Tool

◦ Log in to your Plesk Dashboard.

  • From the left menu, navigate to Websites & Domains.

 

  • Click it to open the Node.js management interface

 

  • Deploying a Node.js Application
  1. Upload your app files to the desired domain’s root directory (usually /httpdocs or a custom path).

  2. In the Node.js tool, set the following:

    • Document Root: Path to your app folder.

    • Application Startup File: e.g. app.js, index.js, or server.js.

    • Application Mode: Choose between Development or Production.

  3. Click Enable Node.js to activate your app.

Once enabled, Plesk automatically sets up the runtime and environment for you.



  • Environment Variables & Logs

Inside the Node.js panel, you can:

◦ Add or edit environment variables (e.g. PORT, NODE_ENV, DATABASE_URL).

◦ View logs directly from the panel to monitor runtime messages or errors.

◦ Restart or stop your app at any time.

  • Important Notes for Shared Hosting

    ◦ 
    Node.js apps run under your account’s user environment — no root privileges.

    ◦ Some modules that require system-level compilation may not be supported.

    ◦ The default port (usually 80 or 443) is managed automatically by Plesk’s reverse proxy — you don’t need to configure it manually.

    ◦ Always deploy apps using relative paths and avoid hardcoded ports.

  • Support Tip

If your app fails to start:

       ◦ Check your startup file path.

       ◦ Review logs for syntax or runtime errors.

       ◦ Ensure all dependencies are installed (npm install inside the app directory).

       ◦ Restart Node.js from the Plesk panel after any change.

 

 

Please rate this article to help us improve our Knowledge Base.

0 0