• Debian 11 is approaching its end-of-life (vendor EOL date - August 31, 2026). Plesk Obsidian 18.0.80 will be the last release to support it.
    If you are running Plesk Obsidian on Debian 11, we recommend you upgrade those servers to Debian 12 using our dist-upgrade tool.
  • We plan to deprecate and remove the support for XML RPC protocol versions earlier than 1.6.9.1 in Plesk Obsidian 18.0.82. We strongly recommend that you update all existing integrations using earlier versions of the XML RPC protocol to comply with the version 1.6.9.1 specification.

Question Run a nodejs server internally without exposing online

plainstuff

New Pleskian
Server operating system version
Ubuntu 24.04
Plesk version and microupdate number
Plesk Obsidian 18.0.66 Update #1 Web Host Edition
Hi. I'm moving from Pterodactyl to Plesk and I was wondering if it's possible to run a nodejs server internally (without exposing it to a domain) - so the nodejs server running on the domain can communicate with it, but it won't be publicly accessible.

I suppose if not I'll have to expose it and add some sort of token authentication.
 
You can. You need the nodeJS app to listen on tcp port that is not opened in the firewall. Then from Additional nginx directives pass the requests to the nodeJS app port.

You can monitor the nodeJS app with supervisord or pm2, installed as the webspace system user.
 
Back
Top