Node.js Manager

Node.js Manager discovers and manages account-owned Node.js applications, ports, PM2 state, logs, package installation, and repair actions.

Where to find it: Open the account and choose Node.js Manager.

Available to: The account user for their own account, plus root or the owning reseller when working inside that account. The item may be hidden when its feature profile or required service is disabled.

What this page does

Use Node.js Manager for the selected hosting account. SHM checks role, ownership, feature availability, limits, and target identifiers before it accepts a change.

Before you start

Confirm the selected account, domain, id, and path before saving. Availability depends on the assigned feature profile, package limits, ownership, and installed server services.

Why use it — and when not to

Use Node.js Manager when the target belongs to the selected hosting account and its feature profile allows the module. Use a server page only when the prerequisite service or policy is genuinely global.

How to use it

1. Open Node.js Manager in the correct role and confirm the selected target.
2. Review the current values before editing them.
3. Change only the fields required for the task and read any confirmation carefully.
4. Wait for a final result, then test the affected service or resource.

Result and next check

A successful action updates only the selected account resource. Confirm the on-page result, then test the affected domain, mailbox, database, application, file, certificate, or job from the customer's point of view.