• 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.

Issue Node+Phusion port conflicts

mytchb

New Pleskian
Server operating system version
Ubuntu 22.04.5 LTS
Plesk version and microupdate number
Plesk Obsidian 18.0.68
When starting a Next.js Node app with the Plesk UI, it uses port 3000 by default.
This is an issue if I want to start a new Next.js app on a different domain, as it conflicts with the same port, giving an error "This address is already in use".

If I stop the first node app process, it frees up the port and I can start the second app.
When I hit the first app's domain, Phusion Passenger gets the request, sees the app is stopped and restarts it - noting that port 3000 is unavailable so it dynamically assigns a new port and both apps are running.

Can there be a way where Phusion does this when starting node apps via the UI?

Note: I could specify a fixed unique port to run for each app, but Plesk+Phusion has the ability to dynamically assign internal ports and route them so why not use it.
 
Back
Top