# Remote deploy feature issue from the node-red-contrib-flow-manager library

**URL:** <https://discourse.nodered.org/t/remote-deploy-feature-issue-from-the-node-red-contrib-flow-manager-library/97110>\
**Category:** General\
**Tags:** flows\
**Created:** [17 May 2025 19:27 UTC](https://discourse.nodered.org/t/remote-deploy-feature-issue-from-the-node-red-contrib-flow-manager-library/97110 "2025-05-17T19:27:56Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![bereket-09](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/bereket-09/32/94819_2.png) [@bereket-09](https://discourse.nodered.org/u/bereket-09)\
**Post date:** [17 May 2025 19:27 UTC](https://discourse.nodered.org/t/remote-deploy-feature-issue-from-the-node-red-contrib-flow-manager-library/97110/1 "2025-05-17T19:27:56Z")

</div>

Hello,

I'm currently testing the **remote deploy** feature from the **Flow Manager** library. I've configured the remote URLs as shown below, and Flow Manager is already installed and functioning on the remote destination servers (I can access filters and other functionalities on them without any issues).

However, when attempting a remote deploy to any of the remote servers (e.g., UAT or PPD , Custome\_2), I receive a **flow error**. Interestingly, when I add a custom remote entry that points to the **same instance (localhost:1880)** as the destination, the deploy works as expected. This suggests the issue may lie with the remote target configuration or a missing setup.

using node red v 4.0.9  
Here’s my current `flow-manager-cfg.json`:

```auto
{
  "filter": [],
  "fileFormat": "json",
  "remoteDeploy": {
    "remotes": [
      {
        "name": "UAT",
        "nrAddress": "https://uat-flowbuilder.vas.blueprint.lab/"
      },
      {
        "name": "PPD",
        "nrAddress": "https://ppd-flowbuilder.vas.blueprint.lab"
      },
      {
        "name": "Custom",
        "nrAddress": "http://localhost:1880"
      },
      {
        "name": "Custom_2",
        "nrAddress": "http://localhost:9006" // another locally installed Node-RED instance
      }
    ]
  }
}

```

 ![image](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/3X/6/0/607ce62a1eb332e6d628891278301c4e71efa9c7.png)

 ![image](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/3X/e/a/ea3c6ec763b8d3f073a770fc77aa53fe629481fb.png)

 ![image](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/3X/0/3/03b9bd5fb76c1ed18bb6e2df283e32c80a0e2dfa.png)

---

<div class="post-metadata">

**Author:** ![bereket-09](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/bereket-09/32/94819_2.png) [@bereket-09](https://discourse.nodered.org/u/bereket-09)\
**Post date:** [28 May 2025 09:21 UTC](https://discourse.nodered.org/t/remote-deploy-feature-issue-from-the-node-red-contrib-flow-manager-library/97110/2 "2025-05-28T09:21:54Z")

</div>

Hey,

😕🥲🥲🥲😕🥲🥲🥲😕🥲🥲🥲

---

<div class="post-metadata">

**Author:** ![knolleary](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/knolleary/32/3_2.png) [@knolleary](https://discourse.nodered.org/u/knolleary)\
**Post date:** [28 May 2025 10:36 UTC](https://discourse.nodered.org/t/remote-deploy-feature-issue-from-the-node-red-contrib-flow-manager-library/97110/3 "2025-05-28T10:36:15Z")

</div>

Hi @bereket-09

I'm not sure how widely used the flow manager is or if it's maintainers are active in this forum.

You could consider raising an issue in their repo here: [Issues · monogoto.io / node-red-contrib-flow-manager · GitLab](https://gitlab.com/monogoto.io/node-red-contrib-flow-manager/-/issues) - but there doesn't appear to be much activity there either.

---

<div class="post-metadata">

**Author:** ![bereket-09](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/bereket-09/32/94819_2.png) [@bereket-09](https://discourse.nodered.org/u/bereket-09)\
**Post date:** [28 May 2025 10:48 UTC](https://discourse.nodered.org/t/remote-deploy-feature-issue-from-the-node-red-contrib-flow-manager-library/97110/4 "2025-05-28T10:48:48Z")

</div>

Hey @knolleary ,

Thanks for your feedback! I’d really appreciate any suggestions you might have on how best to handle this requirement.

To summarize:  
I'm trying to set up a development environment where the entire team can freely build and test their flows. However, when it's time to push changes, I want to enforce a **remote deployment** approach — where developers can select specific tabs/flows to deploy.

Before deployment, I’d like to enable a **diff and review** process, allowing the team to compare changes and only then accept and push them to the next environment. This way, we can prevent direct access to the UAT and PROD Node-RED instances.

The use case is for a USSD application where each flow represents a different service, and we’re working collaboratively as a team on these flows.

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/1X/d073cd938eafa2e558d7c2cd59003b3ef4963033.png) [@system](https://discourse.nodered.org/u/system)\
**Post date:** [26 August 2025 10:49 UTC](https://discourse.nodered.org/t/remote-deploy-feature-issue-from-the-node-red-contrib-flow-manager-library/97110/5 "2025-08-26T10:49:44Z")

</div>

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.