Articles in this section

See more

Node.js menu in Plesk shows error: The file does not exist

Avatar
Marc Vidal
Updated
Follow
Plesk for Windows Plesk for Linux kb: technical ABT: Group B ext: nodejs

Applicable to:

  • Plesk for Linux
  • Plesk for Windows

Symptoms

  • The following error appears next to the Application Startup File in Domains > example.com > Node.js:

    PLESK_ERROR: The file does not exist

  • The NodeJS application doesn't work

Cause

Application Startup File is missing in the Application Root directory.

Resolution

  1. Log in to Plesk GUI

  2. Go to Domains > example.com > Node.js

  3. Verify that the Application Root directory is set to the existing directory

  4. Make sure that the Application Startup File exists in the  Application Root directory and set the correct name

Additional information:

For the working capacity of Node.js, the following conditions should be met:

  • For Linux:

    The Application Root directory must be equal to the subdirectory of the Document Root directory

  • For Windows:

    The Application Root directory must be equal to the Document Root directory.

Comments

4 comments

Sort by Date Votes
  • Avatar
    Tre Stange

    Thank you for this info, but for the life of me I *still* can't find the app.js file. Plesk says it's installed, but I don't see any evidence of node in my domain. The 'file does not exist' notification is still next to the app.js in the Application Startup File row. Thoughts?

     

    0
    Comment actions Permalink
  • Avatar
    Nelson Leiva

    Hi Tre Stange,

    This message means that there is no such file in the application root.

    For example, there is no app.js file in /httpdocs/. However, if you create a file app.js in that same directory /httpdocs/, no error will be shown.

    In case applications is using another startup file, for example server.js, you can just click on app.js and specify another startup file name.

    0
    Comment actions Permalink
  • Avatar
    Oscar

    npm WARN lifecycle npm is using /opt/plesk/node/12/bin/node but there is no node binary in the current PATH. Use the --scripts-prepend-node-path option to include the path for the node binary npm was executed with.
    sh: node: command not found

    0
    Comment actions Permalink
  • Avatar
    Marc Vidal

    Hi Oscar!

    The error that was mentioned in your screenshot was related to a different issue. Please, apply the solution described in the following KB article: https://support.plesk.com/hc/en-us/articles/360000644114

    0
    Comment actions Permalink

Please sign in to leave a comment.

Have more questions? Submit a request

Related articles