# 'rbe' already registered by module node-red

**URL:** <https://discourse.nodered.org/t/rbe-already-registered-by-module-node-red/84847>\
**Category:** General\
**Created:** [23 January 2024 21:02 UTC](https://discourse.nodered.org/t/rbe-already-registered-by-module-node-red/84847 "2024-01-23T21:02:34Z")\
**Posts on this page:** 8\
**Page:** 1

<div class="post-metadata">

**Author:** ![GiovanniG](https://avatars.discourse-cdn.com/v4/letter/g/ecd19e/32.png) [@GiovanniG](https://discourse.nodered.org/u/GiovanniG)\
**Post date:** [23 January 2024 21:02 UTC](https://discourse.nodered.org/t/rbe-already-registered-by-module-node-red/84847/1 "2024-01-23T21:02:34Z")

</div>

Hi, on startup I have this warn, how can I remove it? Thanks  
[warn] [node-red-node-rbe/rbe] 'rbe' already registered by module node-red

---

<div class="post-metadata">

**Author:** ![GogoVega](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/gogovega/32/71313_2.png) [@GogoVega](https://discourse.nodered.org/u/GogoVega)\
**Post date:** [23 January 2024 21:10 UTC](https://discourse.nodered.org/t/rbe-already-registered-by-module-node-red/84847/2 "2024-01-23T21:10:59Z")

</div>

Hi,

This means that you are using a contrib node that has the same `rbe` type.

There is nothing you can do to avoid this conflict other than not using this node anymore.

Note: this node is registered from the node-red core which means that the contrib node has not been loaded (and not usable)

PS: I don't know if disabling one of the two nodes works

---

<div class="post-metadata">

**Author:** ![marcus-j-davies](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/marcus-j-davies/32/103435_2.png) [@marcus-j-davies](https://discourse.nodered.org/u/marcus-j-davies)\
**Post date:** [23 January 2024 21:24 UTC](https://discourse.nodered.org/t/rbe-already-registered-by-module-node-red/84847/3 "2024-01-23T21:24:51Z")

</div>

If memory serves me right..

The `rbe` node was moved into the core sometime ago

Previously this was optional (like all other user contributed nodes)

It would appear you have an old copy (one that was installed after you installed Node RED) but is now included.

Since the RBE node is now included, you will get the message.

Go into your node red directory (.node-red) and issue the command.

**npm uninstall node-red-node-rbe**

And restart node red.

I could have these instructions wrong, but I’m sure it’s easily fixable

---

<div class="post-metadata">

**Author:** ![Steve-Mcl](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/steve-mcl/32/4826_2.png) [@Steve-Mcl](https://discourse.nodered.org/u/Steve-Mcl)\
**Post date:** [23 January 2024 21:28 UTC](https://discourse.nodered.org/t/rbe-already-registered-by-module-node-red/84847/4 "2024-01-23T21:28:17Z")

</div>

> [@marcus-j-davies](#):
>
> npm uninstall node-red-node-rbe

I _think_ it was installed globally in times gone by. My memory might be off, but it won't hurt to do global uninstall also...

```auto
npm remove -g node-red-node-rbe

```

---

<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:** [23 January 2024 21:32 UTC](https://discourse.nodered.org/t/rbe-already-registered-by-module-node-red/84847/5 "2024-01-23T21:32:38Z")

</div>

> [@Steve-Mcl](#):
>
> `npm remove -g node-red-node-rbe`

Or `sudo npm remove node-red-node-rbe` if you are on a linux system.

It was moved into the core and renamed the Filter node. Existing rbe nodes will keep working.

---

<div class="post-metadata">

**Author:** ![GiovanniG](https://avatars.discourse-cdn.com/v4/letter/g/ecd19e/32.png) [@GiovanniG](https://discourse.nodered.org/u/GiovanniG)\
**Post date:** [18 February 2024 10:12 UTC](https://discourse.nodered.org/t/rbe-already-registered-by-module-node-red/84847/6 "2024-02-18T10:12:58Z")

</div>

Hi mates, thank you for your kind answers! Please excuse me for the delay on answer  
Can I remove RBE safely? Anything on my flow won't stop after it? and how can I repair if this happens?  
Can I use so:  
`npm uninstall node-red-node-rbe`  
`npm remove -g node-red-node-rbe`  
To be honest, under palette I see rbe not working and I can disabe or remove this node by buttons, can I do then from Palette?  
I'm running NR 3.0.2, I plan to update it, better update after removing rbe?  
Thank you

---

<div class="post-metadata">

**Author:** ![Steve-Mcl](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/steve-mcl/32/4826_2.png) [@Steve-Mcl](https://discourse.nodered.org/u/Steve-Mcl)\
**Post date:** [18 February 2024 10:15 UTC](https://discourse.nodered.org/t/rbe-already-registered-by-module-node-red/84847/7 "2024-02-18T10:15:04Z")

</div>

> [@GiovanniG](#):
>
> npm remove -g node-red-node-rbe

just run this ^ first (or later!)

As Colin says, you probably need to use `sudo`

---

<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:** [3 March 2024 10:15 UTC](https://discourse.nodered.org/t/rbe-already-registered-by-module-node-red/84847/8 "2024-03-03T10:15:50Z")

</div>

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