Node.js Fails to Be Started or Stopped on a Windows Host

Symptom 1

On a Windows host, the deployment of the command for starting Node.js fails during the deployment of the action Start/Stop Node.js, and the error message start service failed is displayed.

Cause Analysis

The startup file is not found in the service path.

Solution

Enter the correct service path.

Symptom 2

The error message Node service not installed, service start failed! is displayed.

Cause Analysis

The Node.js service is not installed on the host.

Solution

Install Node.js before action deployment.

Symptom 3

The deployment of the action Start/Stop Node.js does not respond for a long time and then fails, with the error message Install forever failure! displayed.

Cause Analysis

The host cannot connect to the platform.

Solution

Ensure that the host can connect to the external network and the DNS is correctly configured.

Parent topic: Starting or Stopping Node.js

Feedback

Was this page helpful?

Helpful Not helpful

Provide feedback

Thank you very much for your feedback. We will continue working to improve the documentation.See the reply and handling status in My Cloud VOC.

The system is busy. Please try again later.

Which of the following issues have you encountered?

Content is inconsistent with the product UI

Unclear descriptions

Lack of examples or code

Incorrect steps

Can't find what I need

Lack of best practices

Feedback (optional)

0/500

Select at least one type of issue, and enter your comments or suggestions.

Enter a maximum of 500 characters.

Submit Cancel

For any further questions, feel free to contact us through the chatbot.

Chatbot