- Server operating system version
- AlmaLinux 8.8 (Sapphire Caracal)
- Plesk version and microupdate number
- Plesk Obsidian Version 18.0.53 Update #1, last updated on June 15, 2023 02:16 AM
Hi
I have set up a Node.js add on a domain following these instructions: Plesk Node.Js Setup
It pretty much works except I get a message: "Another Node.js application in the subscription already uses this application root. Specify another application root that contains the document root." But anyway.
My question is: how is this interacting with Nginx and/or Apache. In a default set up Nginx acts as a reverse proxy for Apache and serves static content (after it is passed the disk location by Apache which has processed the request). In the case of a Node app installed as per the above how does this work? Is Apache out of the picture? Is Nginx still serving static content? The docs explain how to set it up but they don't say what you have done.
If someone can give me a brief outline of how this is working I will be very grateful.
Thanks
I have set up a Node.js add on a domain following these instructions: Plesk Node.Js Setup
It pretty much works except I get a message: "Another Node.js application in the subscription already uses this application root. Specify another application root that contains the document root." But anyway.
My question is: how is this interacting with Nginx and/or Apache. In a default set up Nginx acts as a reverse proxy for Apache and serves static content (after it is passed the disk location by Apache which has processed the request). In the case of a Node app installed as per the above how does this work? Is Apache out of the picture? Is Nginx still serving static content? The docs explain how to set it up but they don't say what you have done.
If someone can give me a brief outline of how this is working I will be very grateful.
Thanks