• Introducing WebPros Cloud - a fully managed infrastructure platform purpose-built to simplify the deployment of WebPros products !  WebPros Cloud enables you to easily deliver WebPros solutions — without the complexity of managing the infrastructure.
    Join the pilot program today!
  • Support for BIND DNS has been removed from Plesk for Windows due to security and maintenance risks.
    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.

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