Resolved Unable to Disable Node.js Application in Plesk – App Remains Accessible

[HawkSky]

Server operating system version

Ubuntu 24.04

Plesk version and microupdate number

Version 18.0.64 Update #1

Dear Forum Users,

I am experiencing an issue with the Node.js application management within Plesk Obsidian on an Ubuntu server, and despite several attempts to resolve the problem, it persists. Below are the details of the issue and the troubleshooting steps I've already taken.

Issue Description:

I have a Node.js application set up on a sub-subdomain interpreter.app.domain.com. When configuring the app within Plesk, it becomes accessible immediately without enabling Node.js, which should - I guess - not happen. Additionally, once the application is running, clicking "Enable Node.js" in the Plesk interface does not change the app's state - it remains accessible.

However, when I click "Disable Node.js," although the backend shows that the app is disabled, the application remains fully reachable and functional in the browser. I have no control over properly disabling the app through the Plesk interface.

The screenshot I’ve attached provides specific details of my setup:

• Node.js Version: 20.18.0
• Package Manager: npm
• Document Root: /interpreter/public
• Application Mode: Production
• Application URL: http://interpreter.app.domain.com
• Application Root: /interpreter
• Application Startup File: app.js

No other apps are running on the server, and the primary subdomain (installed as domain) app. domain.com does not have Node.js enabled.

Troubleshooting Steps Taken:

1. Server and Reverse Proxy Restart: I restarted the server and relevant services (Nginx/Apache) with disabled node.js to ensure there was no caching or reverse proxy interference. However, the app remained accessible even after these steps.
2. Node.js Process Check: Since Plesk controls the Node.js processes internally, I could not directly access or manually manage them outside of Plesk.
3. Deactivated Proxy mode: I deactivated Proxy mode in the nginx settings on both the domain and the subdomain, but it didn't change anything.
4. Complete Reinstallation of Plesk: I have reinstalled Plesk and set up everything from scratch, but the problem persists.
5. Logs and Domain Setup: The logs do not provide clear indications of why the app cannot be properly disabled.

Current Situation:

At this point, I am unable to properly manage the Node.js application’s availability via the Plesk interface, which impacts the functionality and security of my setup. The app is always accessible, even when it should be disabled.

I would appreciate any assistance in resolving this problem.
Thank you for your help.

 

[HawkSky]

SOLVED:

Don't set Document Root to /public/ when there is the application index file in it:

So:

Document Root
/interpreter

Application Root
/interpreter

Solved this in my case.