• Our team is looking to connect with folks who use email services provided by Plesk, or a premium service. If you'd like to be part of the discovery process and share your experiences, we invite you to complete this short screening survey. If your responses match the persona we are looking for, you'll receive a link to schedule a call at your convenience. We look forward to hearing from you!
  • We are looking for U.S.-based freelancer or agency working with SEO or WordPress for a quick 30-min interviews to gather feedback on XOVI, a successful German SEO tool we’re looking to launch in the U.S.
    If you qualify and participate, you’ll receive a $30 Amazon gift card as a thank-you. Please apply here. Thanks for helping shape a better SEO product for agencies!
  • The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.

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