• Hi, Pleskians! We are running a UX testing of our upcoming product intended for server management and monitoring.
    We would like to invite you to have a call with us and have some fun checking our prototype. The agenda is pretty simple - we bring new design and some scenarios that you need to walk through and succeed. We will be watching and taking insights for further development of the design.
    If you would like to participate, please use this link to book a meeting. We will sent the link to the clickable prototype at the meeting.
  • (Plesk for Windows):
    MySQL Connector/ODBC 3.51, 5.1, and 5.3 are no longer shipped with Plesk because they have reached end of life. MariaDB Connector/ODBC 64-bit 3.2.4 is now used instead.
  • The Horde webmail has been deprecated. Its complete removal is scheduled for April 2025. For details and recommended actions, see the Feature and Deprecation Plan.

Issue Node.js setting conflict with hosting setting

YannickY

New Pleskian
I face a big obstacle. I am trying to enable node.js with an application but the "Document root" of nodejs overwrites the same "Document root" setting inside the "Host setting", where the domain is set.
This is the situation: Plesk Web Admin (last update) on Linux (Debian 10). Cloud Server. I do not have root access because it is a managed server.

/httpsdocs/app
Folder /httpsdocs is where the site is with index.php
Folder /app is where I have put the application that should work with node.js

Now, I'm following this instructions to enable node.js but there is something wrong.
First of all, as already mentioned, "Document root" overwrites the same setting inside "Hosting setting" and this blows everything up. I don't understand why I have to set something about the documents, there is no documents beside readme.md, changelog.md and license.md and I don't understand why it mess with another unreleated setting as the hosting setting. This is the first problem.
The second one is that this "Document root" HAS to be a subfolder (or the same folder) as the "Application root". So I am forced to install the app inside root directory / (that even me as a non-expert know is not a good idea) or the main site directory /httpsdocs with problems resulting from overwriting of all files. Why I can't set a subfolder for the application?

But now the true problem here: when I enable the node.js my site goes offline with a page I never seen before: "We're sorry, but something went wrong. This website is powered by Phusion Passenger®, the smart application server built by Phusion®." I've never heard about this Phusion Passenger and I don't think is even installed on my VM. No number error, no info, nothing. Sites just go offline. But if I disable node.js the site come back from the death.

What happened here? What am I missing?
Thank you
 
Last edited:
Back
Top