# Update of NodeRed-container in Portainer 1.17.1 - Node RBE - Type\_already\_registered

**URL:** <https://discourse.nodered.org/t/update-of-nodered-container-in-portainer-1-17-1-node-rbe-type-already-registered/56073>\
**Category:** General\
**Created:** [4 January 2022 08:58 UTC](https://discourse.nodered.org/t/update-of-nodered-container-in-portainer-1-17-1-node-rbe-type-already-registered/56073 "2022-01-04T08:58:09Z")\
**Posts on this page:** 12\
**Page:** 1

<div class="post-metadata">

**Author:** ![Eraser](https://avatars.discourse-cdn.com/v4/letter/e/c4cdca/32.png) [@Eraser](https://discourse.nodered.org/u/Eraser)\
**Post date:** [4 January 2022 08:58 UTC](https://discourse.nodered.org/t/update-of-nodered-container-in-portainer-1-17-1-node-rbe-type-already-registered/56073/1 "2022-01-04T08:58:09Z")

</div>

Hello,

after the update of NodeRed to V2.x.x I get the type\_already\_registeres message with the RBE-node.

I have read in other topics that the rbe-node has been replaced with the filter-node.  
All my nodes are still shown as "rbe". A double-click on it states them then as "filter".

I have tried "npm remove node-red-node-rbe" or "npm uninstall node-red-node-rbe" in the command window of Portainer and after that restarted the container.

```auto
bash-5.0$ npm remove node-red-node-rbe
audited 317 packages in 55.121s

29 packages are looking for funding
  run `npm fund` for details

found 0 vulnerabilities

```

Unfortunately there is no difference, the rbe-node is still shown in the palette manager and also on the flows.  
How do I remove the rbe-node and this warning?

Looking forward for help, thanks  
Wolfgang

---

<div class="post-metadata">

**Author:** ![Colin](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/colin/32/17040_2.png) [@Colin](https://discourse.nodered.org/u/Colin)\
**Post date:** [4 January 2022 10:03 UTC](https://discourse.nodered.org/t/update-of-nodered-container-in-portainer-1-17-1-node-rbe-type-already-registered/56073/2 "2022-01-04T10:03:59Z")

</div>

Welcome to the forum @Eraser

When you ran the `npm remove` command, were you in the folder where the `package.json` and `node_modules` folders are located? When you run it you should see a message telling you that it removed one or more packages.

---

<div class="post-metadata">

**Author:** ![Eraser](https://avatars.discourse-cdn.com/v4/letter/e/c4cdca/32.png) [@Eraser](https://discourse.nodered.org/u/Eraser)\
**Post date:** [4 January 2022 10:43 UTC](https://discourse.nodered.org/t/update-of-nodered-container-in-portainer-1-17-1-node-rbe-type-already-registered/56073/3 "2022-01-04T10:43:24Z")

</div>

Hello Colin,

thanks for your answer.

Yes both are in this folder:

```auto
bash-5.0$ ls -la
total 140
drwxrwxr-x 1 node-red root 4096 Jan 4 08:25 .
drwxr-xr-x 1 root root 4096 Dec 5 09:51 ..
-rw------- 1 node-red node-red 63 Jan 4 08:25 .bash_history
drwx------ 3 node-red node-red 4096 Jan 4 07:48 .config
drwxr-xr-x 5 node-red node-red 4096 Jan 4 09:56 .npm
drwxr-xr-x 1 node-red root 4096 Jan 4 08:19 node_modules
-rw-r--r-- 1 node-red node-red 111535 Jan 4 08:19 package-lock.json
-rw-r--r-- 1 node-red node-red 1063 Jan 4 08:19 package.json
bash-5.0$

```

---

<div class="post-metadata">

**Author:** ![Colin](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/colin/32/17040_2.png) [@Colin](https://discourse.nodered.org/u/Colin)\
**Post date:** [4 January 2022 11:14 UTC](https://discourse.nodered.org/t/update-of-nodered-container-in-portainer-1-17-1-node-rbe-type-already-registered/56073/4 "2022-01-04T11:14:32Z")

</div>

Your node\_modules folder is owned by root. I guess you installed using sudo at some point. Change the ownership of that folder and all contained files/folders. Then run  
`npm install node-red-node-rbe`  
`npm remove node-red-node-rbe`  
Then restart node-red. If still no joy then what do these commands show  
`npm list node-red-node-rbe`  
`sudo npm list -g node-red-node-rbe`

---

<div class="post-metadata">

**Author:** ![Eraser](https://avatars.discourse-cdn.com/v4/letter/e/c4cdca/32.png) [@Eraser](https://discourse.nodered.org/u/Eraser)\
**Post date:** [4 January 2022 11:55 UTC](https://discourse.nodered.org/t/update-of-nodered-container-in-portainer-1-17-1-node-rbe-type-already-registered/56073/5 "2022-01-04T11:55:57Z")

</div>

I didn't install it with sudo rights.  
This is just the latest NodeRed-image for docker (nodered/node-red:latest)

There is one additional volume which maps to /data to ensure that I can easily upgrade NodeRed without having every data wiped.

Here is what I get with your command:

```auto
bash-5.0$ npm list node-red-node-rbe
node-red-docker@2.1.4 /usr/src/node-red
`-- (empty)

bash-5.0$

```

Thanks for your ongoing help  
Wolfgang

---

<div class="post-metadata">

**Author:** ![Colin](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/colin/32/17040_2.png) [@Colin](https://discourse.nodered.org/u/Colin)\
**Post date:** [4 January 2022 12:11 UTC](https://discourse.nodered.org/t/update-of-nodered-container-in-portainer-1-17-1-node-rbe-type-already-registered/56073/6 "2022-01-04T12:11:32Z")

</div>

What is in the /data folder?

---

<div class="post-metadata">

**Author:** ![Eraser](https://avatars.discourse-cdn.com/v4/letter/e/c4cdca/32.png) [@Eraser](https://discourse.nodered.org/u/Eraser)\
**Post date:** [4 January 2022 13:37 UTC](https://discourse.nodered.org/t/update-of-nodered-container-in-portainer-1-17-1-node-rbe-type-already-registered/56073/7 "2022-01-04T13:37:47Z")

</div>

This is in the data-volume, which is mapped to /data:

```auto
bash-4.3# ls -la
total 52
drwxr-xr-x 1 root root 4096 Jan 4 13:34 .
drwxr-xr-x 1 root root 4096 Jan 4 13:34 ..
drwxr-xr-x 1 root root 4096 Jan 30 2019 cache
dr-xr-xr-x 2 root root 4096 Jan 30 2019 empty
drwxr-xr-x 5 root root 4096 Jan 30 2019 lib
drwxr-xr-x 2 root root 4096 Jan 30 2019 local
drwxr-xr-x 3 root root 4096 Jan 30 2019 lock
drwxr-xr-x 2 root root 4096 Jan 30 2019 log
drwxrwxr-x 6 1000 root 4096 Jan 4 10:48 nodered_data
drwxr-xr-x 2 root root 4096 Jan 30 2019 opt
drwxr-xr-x 2 root root 4096 Jan 30 2019 run
drwxr-xr-x 3 root root 4096 Jan 30 2019 spool
drwxrwxrwt 2 root root 4096 Jan 30 2019 tmp
bash-4.3# cd nodered_data
bash-4.3# ls -la
total 432
drwxrwxr-x 6 1000 root 4096 Jan 4 10:48 .
drwxr-xr-x 1 root root 4096 Jan 4 13:34 ..
-rw-r--r-- 1 1000 1000 16025 Oct 31 2020 .config.json
-rw-r--r-- 1 1000 1000 16121 Oct 31 2020 .config.json.backup
-rw-r--r-- 1 1000 1000 29589 Jan 4 07:03 .config.nodes.json
-rw-r--r-- 1 1000 1000 29662 Jan 4 07:03 .config.nodes.json.backup
-rw-r--r-- 1 1000 1000 2 Nov 1 2020 .config.projects.json
-rw-r--r-- 1 1000 1000 95 Nov 1 2020 .config.runtime.json
-rw-r--r-- 1 1000 1000 626 Jan 4 08:19 .config.users.json
-rw-r--r-- 1 1000 1000 626 Jan 4 08:19 .config.users.json.backup
-rw-r--r-- 1 1000 1000 116077 Jan 4 10:48 .flows.json.backup
-rw-r--r-- 1 1000 1000 152 Jan 4 06:29 .flows_cred.json.backup
drwxr-xr-x 4 1000 1000 4096 Jan 4 06:58 .npm
-rw-r--r-- 1 1000 1000 116077 Jan 4 10:48 flows.json
-rw-r--r-- 1 1000 1000 124 Jan 4 06:29 flows_cred.json
drwxr-xr-x 3 1000 1000 4096 Sep 3 09:18 knxultimatestorage
drwxr-xr-x 3 1000 1000 4096 Jun 9 2020 lib
drwxr-xr-x 104 1000 1000 4096 Jan 4 06:58 node_modules
-rw-r--r-- 1 1000 1000 35864 Jan 4 06:58 package-lock.json
-rw-r--r-- 1 1000 1000 827 Jan 4 06:58 package.json
-rw-r--r-- 1 1000 1000 12450 Jun 9 2020 settings.js
bash-4.3# ^C
bash-4.3#

```

---

<div class="post-metadata">

**Author:** ![Colin](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/colin/32/17040_2.png) [@Colin](https://discourse.nodered.org/u/Colin)\
**Post date:** [4 January 2022 13:46 UTC](https://discourse.nodered.org/t/update-of-nodered-container-in-portainer-1-17-1-node-rbe-type-already-registered/56073/8 "2022-01-04T13:46:06Z")

</div>

Isn't that where you should be running npm remove? Try removing it there.  
If it isn't that then I think you need someone who knows more about docker to help.

---

<div class="post-metadata">

**Author:** ![dceejay](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/dceejay/32/38_2.png) [@dceejay](https://discourse.nodered.org/u/dceejay)\
**Post date:** [4 January 2022 16:19 UTC](https://discourse.nodered.org/t/update-of-nodered-container-in-portainer-1-17-1-node-rbe-type-already-registered/56073/9 "2022-01-04T16:19:21Z")

</div>

It's just a warning - as they are in fact the same node (we renamed rbe to filter for 2.x) -the fact that they are overlapping won't cause an issue and can be ignored.

---

<div class="post-metadata">

**Author:** ![Eraser](https://avatars.discourse-cdn.com/v4/letter/e/c4cdca/32.png) [@Eraser](https://discourse.nodered.org/u/Eraser)\
**Post date:** [5 January 2022 05:26 UTC](https://discourse.nodered.org/t/update-of-nodered-container-in-portainer-1-17-1-node-rbe-type-already-registered/56073/10 "2022-01-05T05:26:31Z")

</div>

I have now executed the npm remove in the desired data-folder:

```auto
bash-5.0$ ls -la
total 432
drwxrwxr-x 6 node-red root 4096 Jan 4 11:48 .
drwxr-xr-x 1 root root 4096 Jan 4 07:47 ..
-rw-r--r-- 1 node-red node-red 16025 Oct 31 2020 .config.json
-rw-r--r-- 1 node-red node-red 16121 Oct 31 2020 .config.json.backup
-rw-r--r-- 1 node-red node-red 29589 Jan 4 08:03 .config.nodes.json
-rw-r--r-- 1 node-red node-red 29662 Jan 4 08:03 .config.nodes.json.backup
-rw-r--r-- 1 node-red node-red 2 Nov 1 2020 .config.projects.json
-rw-r--r-- 1 node-red node-red 95 Nov 1 2020 .config.runtime.json
-rw-r--r-- 1 node-red node-red 626 Jan 4 09:19 .config.users.json
-rw-r--r-- 1 node-red node-red 626 Jan 4 09:19 .config.users.json.backup
-rw-r--r-- 1 node-red node-red 116077 Jan 4 11:48 .flows.json.backup
-rw-r--r-- 1 node-red node-red 152 Jan 4 07:29 .flows_cred.json.backup
drwxr-xr-x 4 node-red node-red 4096 Jan 4 07:58 .npm
-rw-r--r-- 1 node-red node-red 116077 Jan 4 11:48 flows.json
-rw-r--r-- 1 node-red node-red 124 Jan 4 07:29 flows_cred.json
drwxr-xr-x 3 node-red node-red 4096 Sep 3 11:18 knxultimatestorage
drwxr-xr-x 3 node-red node-red 4096 Jun 9 2020 lib
drwxr-xr-x 104 node-red node-red 4096 Jan 4 07:58 node_modules
-rw-r--r-- 1 node-red node-red 35864 Jan 4 07:58 package-lock.json
-rw-r--r-- 1 node-red node-red 827 Jan 4 07:58 package.json
-rw-r--r-- 1 node-red node-red 12450 Jun 9 2020 settings.js
bash-5.0$ npm remove node-red-node-rbe
removed 1 package and audited 103 packages in 22.841s

1 package is looking for funding
  run `npm fund` for details

found 2 high severity vulnerabilities
  run `npm audit fix` to fix them, or `npm audit` for details
bash-5.0$

```

After restarting NodeRED I have checked the webinterface again and now all nodes are changed to "filter" instead of "rbe". Thank you very much for your help.

The 2 vulnerabilites are from a S7-controller node, which I fixed with npm audit fix.

---

<div class="post-metadata">

**Author:** ![Eraser](https://avatars.discourse-cdn.com/v4/letter/e/c4cdca/32.png) [@Eraser](https://discourse.nodered.org/u/Eraser)\
**Post date:** [6 January 2022 09:51 UTC](https://discourse.nodered.org/t/update-of-nodered-container-in-portainer-1-17-1-node-rbe-type-already-registered/56073/11 "2022-01-06T09:51:07Z")

</div>

Thanks for your help Colin, now everything is fine.

---

<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:** [20 January 2022 09:51 UTC](https://discourse.nodered.org/t/update-of-nodered-container-in-portainer-1-17-1-node-rbe-type-already-registered/56073/12 "2022-01-20T09:51:26Z")

</div>

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