• Plesk Uservoice will be deprecated by October. Moving forward, all product feature requests and improvement suggestions will be managed through our new platform Plesk Productboard.
    To continue sharing your ideas and feedback, please visit features.plesk.com

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