Skip to main content

How to Setup NodeJs

This short guide explains how to run Node.js apps on our budget web hosting using our control panel's Node.js tooling. It adapts the control panel's documentation into a customer-friendly checklist and step-by-step instructions.

About​

  • Our control panel installs Node.js per website in the site's home directory so changes don't affect other sites.
  • Multiple Node.js apps and versions can be managed per website.
  • The panel provides tools to update the Node version, startup command, working directory, mode (Automatic / Manual), and to delete the app.
caution

Node.js can be resource‑intensive. Hyper Layer enforces CPU and resource limits on hosting packages to protect overall platform stability. If your application needs more resources, contact our support team to discuss package upgrades or limit adjustments.

Prerequisites​

  • Node.js is enabled on our hosting packages by default. If you are on the B Micro package, Node.js is not included — contact support to upgrade or enable it.
  • If you plan to use Manual mode, you should be comfortable with SSH and Node tooling.

Deploying a Node.js app (panel steps)​

  1. Open Websites in the panel and select the website to deploy to.
  2. In the website dashboard, open the Advanced menu and click Node.js.
  3. Click Deploy app.
  4. Complete the form fields (see details below) and click Deploy.

Form fields (what they mean)​

  • Mode: Automatic or Manual (see Modes section).
  • Proxy settings: enable proxy and specify the path and port your app will listen on (port must be between 1024 and 65535 and unique inside the site).
  • Startup command: the command the panel will run to start your app (e.g., npm start --production). The panel will cd into the Working Directory first, if provided.
  • Working directory: path relative to the home directory where your app runs (do not use absolute paths).
  • Node version: choose the major Node.js version to run. When started automatically, the panel runs the appropriate nvm use command for you.

Modes — Automatic vs Manual​

Automatic mode (recommended for production):

  • The control panel starts your app automatically with the chosen Node version.
  • If the app exits, it will be restarted automatically.
  • Stdout/stderr are logged to persistent_app_<ID>.log in the home directory; logs are rotated at each start.
  • To force a restart, toggle the mode to Manual and back to Automatic.
tip

Automatic mode is recommended for production: the panel manages restarts and log rotation for you.

Manual mode:

  • The panel will not start or restart the app automatically.
  • No automatic log output is produced by the panel.
  • You must initialize the Node environment (run install_nvm_and_node.sh as the website user) and start the app manually via SSH. You may need nvm use before starting.
warning

Manual mode requires SSH access and Linux/Node experience. The panel will not manage restarts or logs for manual apps.

Proxy settings and domains​

  • The panel will proxy requests for the specified path on the primary domain to your Node app.
  • Only the primary domain is proxied. To point additional domains to the same app, add them as aliases and redirect them to the primary domain (for example using .htaccess).
  • The app port must be unique within the website container and in the 1024–65535 range.
note

Only the primary domain is proxied by the panel. To use additional domains with the same app add them as aliases and redirect them to the primary domain (for example via .htaccess).

Logs, updates and restores​

  • Logs for automatically started apps are written to persistent_app_<ID>.log in the home directory.
  • Node apps are restored from backups, but they are not automatically deployed after a website backup restore — you may need to re-deploy.
  • The panel can run a Steam update-like process for other services; for Node, ensure your app's dependencies are installed and up-to-date.
warning

Node.js applications are restored by backups but are not automatically re-deployed after a website restore. You may need to re-deploy the app and reinstall dependencies.

Warnings & best practices​

warning

Hyper Layer cannot provide application-level support — keep apps simple and well-tested. If you enable hard resource limits on a package, make sure the limits are sufficient for your Node app. Node.js cannot be installed on the same path as an existing application. Do not use privileged ports (<1024).

Last updated on