Angular SSR does not work OOB with PM2 #31081

Activity

1. JeanMeche

   transferred this issue fromangular/angularon Aug 29, 2025
2. alan-agius4 commented on Sep 1, 2025

   

   alan-agius4

   on Sep 1, 2025

   Collaborator

   More actions

   Feel free to modify the provided server.ts file to suit your specific server configuration, as it's just a basic starting point.
3. alan-agius4

   closed this as not plannedon Sep 1, 2025
4. PowerKiKi

   added 2 commits that reference this issue on Sep 29, 2025

   feat(@schematics/angular): Out of the box support for PM2

   ...

   This issue will close once commit b5d620e is merged into the 'master' branch.

   b5d620e

   fix(@schematics/angular): Out of the box support for PM2

   ...

   This issue will close once commit 6d39c65 is merged into the 'master' branch.

   6d39c65
5. PowerKiKi commented on Sep 29, 2025

   

   PowerKiKi

   on Sep 29, 2025

   Contributor

   More actions

   This tripped me too. I would expected the most popular process manager in node would be supported out of the box. I ended up with this:

     * Start the server if this module is the main entry point.
     * The server listens on the port defined by the `PORT` environment variable, or defaults to 4000.
     */
   -if (isMainModule(import.meta.url)) {
   +if (isMainModule(import.meta.url) || process.env.pm_id) {
        const port = process.env.PORT || 9003;
        app.listen(port, error => {
            if (error) {
6. alan-agius4

   added 2 commits that reference this issue on Sep 29, 2025

   fix(@schematics/angular): Out of the box support for PM2

   ...

   This issue will close once commit 8ac5156 is merged into the 'main' branch.

   8ac5156

   fix(@schematics/angular): Out of the box support for PM2

   ...

   This issue will close once commit c94bf7f is merged into the 'main' branch.

   c94bf7f
7. alan-agius4

   closed this as completedin #31334on Sep 29, 2025
8. hheexx commented on Oct 3, 2025

   

   hheexx

   on Oct 3, 2025

   Last edited by hheexx

   Author

   More actions

   @alan-agius4 thanks!
   Any chance for cluster mode support?
   Currently it's not that easy to scale the app.
9. alan-agius4 commented on Oct 3, 2025

   

   alan-agius4

   on Oct 3, 2025

   Collaborator

   More actions

   That a good idea, please feel free to open a feature request. Using cluster mode directly would certainly make it easier for developers to leverage multi-core CPUs for Angular SSR and would be a valuable feature request. However, it's crucial to understand that scaling isn't just a Node.js issue; it requires proper deployment infrastructure. Even with cluster support, running public traffic directly to the Node.js layer is not recommended.

   For robust scaling, one must use a Reverse Proxy/Load Balancer (like Nginx or a Cloud Load Balancer) in front of multiple Node.js SSR instances. This proxy is vital as it not only distributes the load but also offloads critical work serving static assets and handling SSL and allows you to implement aggressive caching at the edge/CDN layer.
10. hheexx commented on Oct 4, 2025

    

    hheexx

    on Oct 4, 2025

    Author

    More actions

    @alan-agius4 Ok, here it is #31387
    Yea we use nginx anyway but cluster support would make configuration easier on nginx and pm2 sides.
11. angular-automatic-lock-bot commented on Nov 4, 2025

    

    angular-automatic-lock-botBot

    on Nov 4, 2025

    More actions

    This issue has been automatically locked due to inactivity.
    Please file a new issue if you are encountering a similar or related problem.

    Read more about our automatic conversation locking policy.

    _{This action has been performed automatically by a bot.}
12. angular-automatic-lock-bot

    locked and limited conversation to collaborators on Nov 4, 2025