Prepare a trusted application with its package manifest, lockfile, documented build process and compatible supported Node.js version. Identify the application root, public document root and startup file. Keep environment secrets outside the repository and preserve application data before deployment.

1. Open the domain Node.js tool or select the Node.js website setup option offered by the installed version.
2. Choose the available runtime compatible with the project. Set the application root and document root deliberately; public assets should not expose private server configuration.
3. Select the actual application startup file and production application mode. Enter the required environment settings through the supported configuration mechanism without publishing secrets.
4. Install dependencies using the offered package-manager action and review the result. Run the documented build script if the project requires one. Package scripts execute code, so use only trusted application sources.
5. Enable or restart the application through the panel. Check its logs and test a simple request before testing database-backed features.

Confirm the application answers through its intended HTTPS domain and survives a panel-managed restart. Test static assets, authentication and a representative API route. Verify that development error pages and debugging endpoints are not publicly exposed.

For startup failure, check the startup filename, runtime compatibility, required environment values and dependency-install result. For framework-specific deployment requirements, follow the application supported Plesk version and adapter guidance. Do not start a second unmanaged process on a public port to hide a broken panel deployment. Restore the previous tested release if needed.

• Deploying a website from Git with Plesk
• Changing a Plesk website document root safely
• Diagnosing website errors with the Plesk log browser
• Adding supported Apache and nginx directives in Plesk

• Plesk: Nodejs Support
• Plesk: Using Nodejs