Skip to content

Node.js Management

Create and operate managed Node.js and Next.js applications.

1Overview

Node.js Management lists Node-based applications that the account is allowed to run. A managed application owns one registered domain and runs through a controlled service.

Node.js Management in the user panel. Account names, domains, and addresses are examples. Available controls depend on your package and server configuration.
Node.js and Next.js Management page with application inventory, Git connections, refresh, and application creation controls.

Node.js Management in the user panel. Account names, domains, and addresses are examples. Available controls depend on your package and server configuration.

2Before you begin

User-panel actions affect only resources owned by the signed-in hosting account. This is an advanced task; schedule it carefully and keep a rollback path.

3Step-by-step workflow

Open Node.js Management, create an application if your package allows it, select the domain, upload or connect the project, set the package start and build configuration, install dependencies, build, then deploy. Use logs and status to verify it is running.

  1. Open Node.js Management and check the available runtime and application allowance.
  2. Prepare your project source and package.json, including the scripts needed to build and start it.
  3. Choose Create application and select a domain already owned by your hosting account.
  4. Set the application root, runtime, and required entry or start settings offered by the form.
  5. Upload the source or connect the approved Git source, and add required environment variables without putting secrets in public files.
  6. Install dependencies and run the build when the project requires compiled output.
  7. Deploy or Start the application and read its logs immediately.
  8. Open its public URL, test a representative request, and use Restart only after a configuration or source change requires it.

4Practical example

Example: a Next.js application usually needs both a successful production build and a production start script. The managed application must listen on the address and port expected by the panel.

5Static websites and application processes

A simple HTML, CSS, and JavaScript website can be uploaded to its website document root without creating a Node.js process. Projects that generate static output should publish the generated output folder through the appropriate deployment method.

For a running Node.js application, use the managed process controls. Follow the supplied PORT or startup configuration instead of choosing a public port arbitrarily, and keep environment secrets outside files served directly to visitors.

6Verify the result

Validate the outcome from the affected website, mailbox, application, or client connection after the panel reports success.

  1. Confirm the application reports Running or Healthy.
  2. Request its public URL and check logs for startup or proxy errors.

7Common problems and what to check

Creation is denied: check package permissions, domain ownership, and whether the runtime is installed.

Dependencies or build fail: read the first relevant error and confirm package.json and the supported Node.js version.

A process runs but the site returns a gateway error: check the managed port, listening address, start command, and application log.

8Security, impact, and rollback

Static websites do not need a Node.js application. For a process-backed app, never expose environment secrets in source files or browser bundles.

Related guides

Python SelectorCreate and manage supported Python web applications.Select PHP VersionChoose PHP versions, extensions, and options per website.See all guides in User hosting panel

Still need a hand?

Get help with your plan, website, or hosting through your client area.

Open client area