# Node-red editor stuck on launch despite --safe flag

**URL:** <https://discourse.nodered.org/t/node-red-editor-stuck-on-launch-despite-safe-flag/52458>\
**Category:** General\
**Created:** [20 October 2021 11:55 UTC](https://discourse.nodered.org/t/node-red-editor-stuck-on-launch-despite-safe-flag/52458 "2021-10-20T11:55:16Z")\
**Posts on this page:** 12\
**Page:** 1

<div class="post-metadata">

**Author:** ![pytneri](https://avatars.discourse-cdn.com/v4/letter/p/49beb7/32.png) [@pytneri](https://discourse.nodered.org/u/pytneri)\
**Post date:** [20 October 2021 11:55 UTC](https://discourse.nodered.org/t/node-red-editor-stuck-on-launch-despite-safe-flag/52458/1 "2021-10-20T11:55:16Z")

</div>

I've been running node-red successfully for years despite not knowing a thing about linux. After updating a palette yesterday (don't remember which one) the editor won't load anymore. It's eternally stuck at "Loading Nodes 43/97", even after restarting the service, rebooting the device, emptying browser cache etc.

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

I tried using node-red --safe, and it looks good in the command line, but alas, the page still stalls at 43/97. I don't even get anyplace where I could do anything in the UI. I must be doing something wrong on a very basic level. But what? Any ideas?

Edit: when I start it as a service, the log is throwing constant errors regarding a node 2427. It could be unrelated, but maybe that's the culprit somehow. But how can I disable a particular node if the editor doesn't launch? Is there some kind of flag that I could use to disable a particular node or module?

```auto
(node:2427) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 2)
20 Oct 14:22:58 - [warn] [miio-airpurifier-input:Pollen] Miio Airpurifier Error: Could not connect to device, handshake timeout
(node:2427) UnhandledPromiseRejectionWarning: Error: Could not connect to device, handshake timeout
    at Timeout._onTimeout (/home/pi/.node-red/node_modules/miio/lib/network.js:427:17)
    at listOnTimeout (internal/timers.js:554:17)
    at processTimers (internal/timers.js:497:7)

```

---

<div class="post-metadata">

**Author:** ![zenofmud](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/zenofmud/32/316_2.png) [@zenofmud](https://discourse.nodered.org/u/zenofmud)\
**Post date:** [20 October 2021 12:02 UTC](https://discourse.nodered.org/t/node-red-editor-stuck-on-launch-despite-safe-flag/52458/2 "2021-10-20T12:02:07Z")

</div>

What device are you running it on?  
How much free memory does it have?  
How much free storage?

---

<div class="post-metadata">

**Author:** ![pytneri](https://avatars.discourse-cdn.com/v4/letter/p/49beb7/32.png) [@pytneri](https://discourse.nodered.org/u/pytneri)\
**Post date:** [20 October 2021 12:09 UTC](https://discourse.nodered.org/t/node-red-editor-stuck-on-launch-despite-safe-flag/52458/3 "2021-10-20T12:09:06Z")

</div>

It's running on a Raspi 3B, RAM is 1 GB, I think, and the SD-card is 8 GB. But it seems there is plenty of storage and RAM available. Do you think this could be of any connection with the issue I'm experiencing?

---

<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:** [20 October 2021 12:43 UTC](https://discourse.nodered.org/t/node-red-editor-stuck-on-launch-despite-safe-flag/52458/4 "2021-10-20T12:43:54Z")

</div>

What versions of node-red & nodejs are you running?

What browser are you using?

Are there any errors in the browser console (F12)

---

<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:** [20 October 2021 12:45 UTC](https://discourse.nodered.org/t/node-red-editor-stuck-on-launch-despite-safe-flag/52458/5 "2021-10-20T12:45:58Z")

</div>

> [@pytneri](#):
>
> After updating a palette yesterday (don't remember which one) the editor won't load anymore.

For the editor to hang at 'loading nodes', there is an error of some sort in a node. This isn't about the running flows - so the `--safe` option won't have any effect.

I think you're going to have to try to remember what node you updated yesterday as that will be the prime suspect.

---

<div class="post-metadata">

**Author:** ![pytneri](https://avatars.discourse-cdn.com/v4/letter/p/49beb7/32.png) [@pytneri](https://discourse.nodered.org/u/pytneri)\
**Post date:** [20 October 2021 12:57 UTC](https://discourse.nodered.org/t/node-red-editor-stuck-on-launch-despite-safe-flag/52458/6 "2021-10-20T12:57:28Z")

</div>

I'm using node-red v1.1.3 and node.js v12.22.7

Behaviour is the same on any browser, and the errors in the console (Chrome) are what you would expect if the systems stops replying:

![image](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/3X/9/c/9c20ea0493bf5923f8b3c38987c9e005476a79df.png)

---

<div class="post-metadata">

**Author:** ![pytneri](https://avatars.discourse-cdn.com/v4/letter/p/49beb7/32.png) [@pytneri](https://discourse.nodered.org/u/pytneri)\
**Post date:** [20 October 2021 12:59 UTC](https://discourse.nodered.org/t/node-red-editor-stuck-on-launch-despite-safe-flag/52458/7 "2021-10-20T12:59:21Z")

</div>

Thanks for the heads-up regarding the effect of the --safe option! If I did remember the updated modules (I think it was the google docs one), what would be my next step? How would I go about deactivating individual modules?

---

<div class="post-metadata">

**Author:** ![zenofmud](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/zenofmud/32/316_2.png) [@zenofmud](https://discourse.nodered.org/u/zenofmud)\
**Post date:** [20 October 2021 13:26 UTC](https://discourse.nodered.org/t/node-red-editor-stuck-on-launch-despite-safe-flag/52458/8 "2021-10-20T13:26:57Z")

</div>

You can do a `cd $HOME/.node-red` and then `npm remove node-red-contribute-????` which should remove that node.

If you can’t remember the node, do a `cd $HOME/.node-red/node_modules` Then a `ls -al` and look at all the node-red-contrib modules and their dates.

But remember to go back to the `.node-red` Folder before removing the node.

[note: edited to remove sudo from npm command]

---

<div class="post-metadata">

**Author:** ![pytneri](https://avatars.discourse-cdn.com/v4/letter/p/49beb7/32.png) [@pytneri](https://discourse.nodered.org/u/pytneri)\
**Post date:** [20 October 2021 14:09 UTC](https://discourse.nodered.org/t/node-red-editor-stuck-on-launch-despite-safe-flag/52458/9 "2021-10-20T14:09:27Z")

</div>

Thanks! That did it. Easier than I thought. Also kudos to @Steve-Mcl , because the errors in the browser console pointed me toward the malfunctioning module.

---

<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:** [20 October 2021 14:16 UTC](https://discourse.nodered.org/t/node-red-editor-stuck-on-launch-despite-safe-flag/52458/10 "2021-10-20T14:16:00Z")

</div>

> [@zenofmud](#):
>
> sudo npm remove node-red-contribute-????

Generally it is best not to use sudo for locally installed nodes. Only use sudo if you are using -g. Using sudo may mess up file permissions in your home folder.

---

<div class="post-metadata">

**Author:** ![zenofmud](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/zenofmud/32/316_2.png) [@zenofmud](https://discourse.nodered.org/u/zenofmud)\
**Post date:** [20 October 2021 14:19 UTC](https://discourse.nodered.org/t/node-red-editor-stuck-on-launch-despite-safe-flag/52458/11 "2021-10-20T14:19:01Z")

</div>

Arugh I’m out for the morning and couldn’t remember. I originally didn’t have the sudo and then went and changed it. Sigh…. Thanks @Colin for pointing that out

---

<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 November 2021 14:19 UTC](https://discourse.nodered.org/t/node-red-editor-stuck-on-launch-despite-safe-flag/52458/12 "2021-11-03T14:19:40Z")

</div>

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