[Solved] Unable to Set Node.js Document Root

[amaljunior002]

Hello,

I'm encountering an issue configuring my Node.js application in Plesk on HelioHost.

Current configuration

• Server: Johnny

• Application Root: /nodeapp

• Document Root: /httpdocs (current)

• Startup File: app.js

Directory structure

/
├── httpdocs/
└── nodeapp/
    ├── app.js
    ├── package.json
    └── public/

The public directory exists inside the application root and has standard permissions (755).

Issue

I'm trying to change the Document Root from:

/httpdocs

to:

/nodeapp/public

Plesk allows me to browse to and select the public directory, but when I click OK or Save, it fails with the following error:

Unable to change document root: Permission denied.

Additional observations

• If I set the Application Root to /, the configuration is accepted and /httpdocs remains the document root.

• If I set the Application Root to /nodeapp, Plesk recognizes the application correctly (it detects app.js and package.json), but changing the document root to /nodeapp/public always results in the "Permission denied" error.

• The public directory is a normal directory (not a symbolic link) and is visible in Plesk's File Manager.

• The application files are owned by my hosting account, and the directory permissions appear to be correct.

This appears to be a server-side Plesk or virtual host configuration issue rather than a filesystem permission issue.

Could someone please check whether there is a restriction or configuration problem preventing my account from setting the document root to a subdirectory of the application root?

Thank you.

[wolstech]

Users don't have the ability to change document roots on our systems by design, because it tends to cause weird issues (especially when users later delete the folder they set the document root to). I went ahead and changed it for you. The changes can take up to 2 hours to take effect.

Keep in mind that if you later remove Node from your domain (or you get suspended, which removes Node automatically), your domain may not work properly until you contact support to have the document root changed back.