Node.js is a powerful runtime environment for executing JavaScript code on the server side, while Passenger is a web server that specializes in hosting web applications written in various programming languages, including Node.js. When using Node.js with Passenger, the two work together to provide a scalable and efficient solution for deploying Node.js applications.
Passenger manages the incoming network connections and load balances them across multiple instances of Node.js, allowing for high availability and optimal resource utilization. By leveraging Passenger's features, such as process monitoring and automatic application restarts, Node.js applications can be seamlessly deployed and managed, ensuring reliable and performant web services.
This guide provides an overview of which ports are available to use with Node.js on our servers.
Related Article
Available Ports on Shared, Shared Reseller, and WordPress Hosting
IMPORTANT: Please be aware that Technical Support cannot provide support on this issue as it is out of scope (OOS). It is strongly advised that a third-party developer assists with any NGINX configuration updates.
- Node.js will use the HTTP and HTTPS ports by default, 80 and 443
- Other ports can be used, but they will not respond outside of the server as the ports are closed
Available Ports on VPS or Dedicated Hosting
IMPORTANT: Please be aware that Technical Support cannot provide support on this issue as it is out of scope (OOS). It is strongly advised that a third-party developer assists with any NGINX configuration updates.
- Node.js managed by Passenger will use port 3000 by default, which is a closed port in the default firewall configuration
- Node.js can be set to use any port
- The port may need to be opened in the firewall
NOTE: If the port Node.js is using is closed, the application will respond from within the server, but will not be accessible to visitors outside the server.
Comments
0 comments
Article is closed for comments.