Skip to Content
Browse documentation

Node.js Selector

Choose an installed Node.js runtime for a hosted domain or inherit the server default in Eenos WAP.

Open Runtimes → Node.js → Node.js Selector.

Read the domain table

ColumnMeaning
DomainHosted domain; ordinary domain names link to the website.
OwnerAccount associated with the domain.
RuntimeSaved Node.js selection, or default.
StatusActive or Suspended according to account metadata.
ActionChange-runtime control for an eligible domain.

The table uses hosting-domain metadata, not a scan of running Node.js applications. An Active row does not prove an application is running, and a domain appearing here does not create a Node.js application.

Use search, sorting and pagination. The initial page size is 25; 10, 50, 100 and All are available. Suspended rows do not expose the change action.

Change the runtime

  1. Record the current runtime.
  2. Click Change Node.js runtime on the intended domain.
  3. Review the domain and select an installed runtime, or default to inherit the server default.
  4. Click Change Runtime.
  5. Read the result and verify the domain configuration and application.

The request identifies the domain, owner and runtime. Domain and user values are required, each limited to 200 characters; the runtime is required and limited to 20. Use the choices provided by the panel rather than treating the version-prefix validator as proof that an arbitrary version is installed.

What is applied

The helper writes the domain's Node.js selection and invokes the shared domain virtual-host builder. This can regenerate the domain's configured web stack. It does not explicitly restart a Node.js application process in this selector helper.

Saved choice and running process may differ

Verify the application's launch configuration and effective runtime after changing the selection. A long-running process can keep using its existing executable until the appropriate application lifecycle action is performed.

The helper's final result includes the builder result, but the metadata may already have changed if building fails. Inspect the saved choice and generated configuration before retrying.

Troubleshooting

For invalid selections, choose a listed installed version. For a missing domain or I/O/build failure, inspect ownership metadata, generated configuration and logs. Do not bypass the UI with another account's domain values.

Demo sessions cannot change the runtime. For the effect of changing inherited defaults, see Node.js Settings.