# Cannot access node-red

**URL:** <https://discourse.nodered.org/t/cannot-access-node-red/5225>\
**Category:** Dashboard\
**Created:** [27 November 2018 01:29 UTC](https://discourse.nodered.org/t/cannot-access-node-red/5225 "2018-11-27T01:29:21Z")\
**Posts on this page:** 20\
**Page:** 1

<div class="post-metadata">

**Author:** ![MPELectronique](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/mpelectronique/32/99492_2.png) [@MPELectronique](https://discourse.nodered.org/u/MPELectronique)\
**Post date:** [27 November 2018 01:29 UTC](https://discourse.nodered.org/t/cannot-access-node-red/5225/1 "2018-11-27T01:29:21Z")

</div>

Hi. It's been 2 days i have started with node-red, i think i have installed a wrong package.  
Before it was working fine then i see that when i tried to run node-red:

Start Node-RED

Once Node-RED has started, point a browser at [http://192.168.0.169:1880](http://192.168.0.169:1880)  
On Pi Node-RED works better with the Firefox or Chrome browser

Use node-red-stop to stop Node-RED  
Use node-red-start to start Node-RED again  
Use node-red-log to view the recent log output  
Use sudo systemctl enable nodered.service to autostart Node-RED at every boot  
Use sudo systemctl disable nodered.service to disable autostart on boot

To find more nodes and example flows - go to [http://flows.nodered.org](http://flows.nodered.org)

## Starting as a systemd service. 26 Nov 20:28:09 - [info] Dashboard version 2.10.1 started at /ui 26 Nov 20:28:10 - [warn] ------------------------------------------------------ 26 Nov 20:28:10 - [warn] [node-red-contrib-pushover/pushover] Type already registered 26 Nov 20:28:10 - [warn] [node-red-contrib-ovia-os/os] Type already registered 26 Nov 20:28:10 - [warn] ------------------------------------------------------ 26 Nov 20:28:10 - [info] Settings file : /home/pi/.node-red/settings.js 26 Nov 20:28:10 - [info] Context store : 'default' [module=memory] 26 Nov 20:28:10 - [info] User directory : /home/pi/.node-red 26 Nov 20:28:10 - [warn] Projects disabled : editorTheme.projects.enabled=false 26 Nov 20:28:10 - [info] Flows file : /home/pi/.node-red/flows\_raspberrypi.json 26 Nov 20:28:10 - [warn]

## Your flow credentials file is encrypted using a system-generated key. If the system-generated key is lost for any reason, your credentials file will not be recoverable, you will have to delete it and re-enter your credentials. You should set your own key using the 'credentialSecret' option in your settings file. Node-RED will then re-encrypt your credentials file using your chosen key the next time you deploy a change.

26 Nov 20:28:10 - [info] Starting flows  
26 Nov 20:28:11 - [info] Started flows  
26 Nov 20:28:11 - [info] Server now running at ....  
26 Nov 20:28:11 - [red] Uncaught Exception:  
26 Nov 20:28:11 - Error: ENOENT: no such file or directory, stat '/var/spool/sms/incoming'  
nodered.service: Main process exited, code=exited, status=1/FAILURE  
nodered.service: Unit entered failed state.  
nodered.service: Failed with result 'exit-code'.  
nodered.service: Service hold-off time over, scheduling restart.  
Stopped Node-RED graphical event wiring tool.  
Started Node-RED graphical event wiring tool.  
26 Nov 20:28:14 - [info]

I really dont know what i did wrong.  
I would like some help please.

Thank you.  
Marc.

---

<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:** [27 November 2018 08:42 UTC](https://discourse.nodered.org/t/cannot-access-node-red/5225/2 "2018-11-27T08:42:09Z")

</div>

Well a couple of things

1. you have managed to a couple of packages that overlap with existing package names. For now you will have to uninstall them manually. (We are trying to handle this situation better in the next release).

You need to find where they are installed (usually your ~/.node-red/ directory but may vary depending on how you installed.) - and then run `npm uninstall node-red-contrib-pushover node-red-contrib-ovia-os`

1. whatever node you have for handling sms is failing to access a directory. Which node is that ? Either there are some more pre-requisites required to et it up correctly or there is a bug in that node.

---

<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:** [27 November 2018 08:47 UTC](https://discourse.nodered.org/t/cannot-access-node-red/5225/3 "2018-11-27T08:47:32Z")

</div>

First can you post the start of the log, from the Welcome message. To see this you can run

```bash
node-red-stop
node-red-start

```

Then sort the Type already registered messages. These probably mean that you have installed two nodes that provide the same node types. Have you installed two pushover nodes? In the case of ovia I suspect possibly you have installed node-red-contrib-os as well as the ovia one. Fix those by uninstalling one of the duplicates and see where that takes you.

---

<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:** [27 November 2018 08:55 UTC](https://discourse.nodered.org/t/cannot-access-node-red/5225/4 "2018-11-27T08:55:18Z")

</div>

Colin the error that is causing the crash is

> [@MPELectronique](#):
>
> Error: ENOENT: no such file or directory, stat '/var/spool/sms/incoming'  
> nodered.service: Main process exited, code=exited, status=1/FAILURE

The duplicate nodes don't help - but...

---

<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:** [27 November 2018 08:58 UTC](https://discourse.nodered.org/t/cannot-access-node-red/5225/5 "2018-11-27T08:58:34Z")

</div>

I suspected there was another problem, but my strategy is always to fix the problems that have obvious solutions first, sometimes you find unexpectedly that it also fixes other problems.

---

<div class="post-metadata">

**Author:** ![MPELectronique](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/mpelectronique/32/99492_2.png) [@MPELectronique](https://discourse.nodered.org/u/MPELectronique)\
**Post date:** [28 November 2018 02:12 UTC](https://discourse.nodered.org/t/cannot-access-node-red/5225/6 "2018-11-28T02:12:27Z")

</div>

Hi.  
Thanks for the reply, i accidently remove the node-red directory because i thought of fixing the problem that way..

how can i remove all the dependencies and start node-red from the start?

Thanks.  
Marc.

---

<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:** [28 November 2018 08:16 UTC](https://discourse.nodered.org/t/cannot-access-node-red/5225/7 "2018-11-28T08:16:38Z")

</div>

> [@MPELectronique](#):
>
> i accidently remove the node-red directory

Which node red directory did you remove?

---

<div class="post-metadata">

**Author:** ![MPELectronique](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/mpelectronique/32/99492_2.png) [@MPELectronique](https://discourse.nodered.org/u/MPELectronique)\
**Post date:** [28 November 2018 13:53 UTC](https://discourse.nodered.org/t/cannot-access-node-red/5225/8 "2018-11-28T13:53:07Z")

</div>

The node-red directory entirely.  
thanks.  
marc.

---

<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:** [28 November 2018 14:27 UTC](https://discourse.nodered.org/t/cannot-access-node-red/5225/9 "2018-11-28T14:27:11Z")

</div>

Which node-red directory? Do you mean the .node-red directory in your home folder? If so then all you have to do is to restart node-red and it will recreate the directory with an empty flow.

---

<div class="post-metadata">

**Author:** ![MPELectronique](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/mpelectronique/32/99492_2.png) [@MPELectronique](https://discourse.nodered.org/u/MPELectronique)\
**Post date:** [28 November 2018 23:39 UTC](https://discourse.nodered.org/t/cannot-access-node-red/5225/10 "2018-11-28T23:39:04Z")

</div>

> [@Colin](#):
>
> you mean the .nod

the node-red directory yes.  
i typed node-red-start  
and i didnt see any node-red directory ☹

thanks.  
marc.

---

<div class="post-metadata">

**Author:** ![MPELectronique](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/mpelectronique/32/99492_2.png) [@MPELectronique](https://discourse.nodered.org/u/MPELectronique)\
**Post date:** [28 November 2018 23:42 UTC](https://discourse.nodered.org/t/cannot-access-node-red/5225/11 "2018-11-28T23:42:36Z")

</div>

here's the log:

# Welcome to Node-RED

## 28 Nov 18:41:29 - [info] Node-RED version: v0.19.5 28 Nov 18:41:29 - [info] Node.js version: v10.13.0 28 Nov 18:41:29 - [info] Linux 4.14.79-v7+ arm LE 28 Nov 18:41:30 - [info] Loading palette nodes 28 Nov 18:41:35 - [info] Polymer started at /polymer Missing ENV var CONFIG\_PATH 28 Nov 18:41:40 - [info] Dashboard version 2.10.1 started at /ui 28 Nov 18:41:40 - [warn] ------------------------------------------------------ 28 Nov 18:41:40 - [warn] [node-red-contrib-pushover-inline-image/pushover] Type already registered 28 Nov 18:41:40 - [warn] [node-red-contrib-ovia-os/os] Type already registered 28 Nov 18:41:40 - [warn] ------------------------------------------------------ 28 Nov 18:41:40 - [info] Settings file : /home/pi/.node-red/settings.js 28 Nov 18:41:40 - [info] Context store : 'default' [module=memory] 28 Nov 18:41:40 - [info] User directory : /home/pi/.node-red 28 Nov 18:41:40 - [warn] Projects disabled : editorTheme.projects.enabled=false 28 Nov 18:41:40 - [info] Flows file : /home/pi/.node-red/flows\_raspberrypi.json 28 Nov 18:41:40 - [warn]

## Your flow credentials file is encrypted using a system-generated key. If the system-generated key is lost for any reason, your credentials file will not be recoverable, you will have to delete it and re-enter your credentials. You should set your own key using the 'credentialSecret' option in your settings file. Node-RED will then re-encrypt your credentials file using your chosen key the next time you deploy a change.

28 Nov 18:41:40 - [info] Starting flows  
28 Nov 18:41:41 - [info] Started flows  
28 Nov 18:41:41 - [info] Server now running at [http://127.0.0.1:1880/](http://127.0.0.1:1880/)  
28 Nov 18:41:41 - [red] Uncaught Exception:  
28 Nov 18:41:41 - Error: ENOENT: no such file or directory, stat '/var/spool/sms/incoming'  
nodered.service: Main process exited, code=exited, status=1/FAILURE  
nodered.service: Unit entered failed state.  
nodered.service: Failed with result 'exit-code'.  
nodered.service: Service hold-off time over, scheduling restart.  
Stopped Node-RED graphical event wiring tool.  
Started Node-RED graphical event wiring tool.  
28 Nov 18:41:43 - [info]

thanks for helping me.  
Marc.

---

<div class="post-metadata">

**Author:** ![shrickus](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/shrickus/32/517_2.png) [@shrickus](https://discourse.nodered.org/u/shrickus)\
**Post date:** [28 November 2018 23:50 UTC](https://discourse.nodered.org/t/cannot-access-node-red/5225/12 "2018-11-28T23:50:58Z")

</div>

> [@MPELectronique](#):
>
> 28 Nov 18:41:41 - Error: ENOENT: no such file or directory, stat '/var/spool/sms/incoming'  
> nodered.service: Main process exited, code=exited, status=1/FAILURE

As Dave pointed out previously, this missing directory _appears_ to be causing the crash.  
Does it exist? If so, what are its permissions? If not, try creating it and restarting node-red.

> [@MPELectronique](#):
>
> 28 Nov 18:41:40 - [warn] ------------------------------------------------------  
> 28 Nov 18:41:40 - [warn] [node-red-contrib-pushover-inline-image/pushover] Type already registered  
> 28 Nov 18:41:40 - [warn] [node-red-contrib-ovia-os/os] Type already registered  
> 28 Nov 18:41:40 - [warn] ------------------------------------------------------

And you still need to get rid of these duplicate nodes. Have you tried to uninstall them, or do you need help with that also?

---

<div class="post-metadata">

**Author:** ![MPELectronique](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/mpelectronique/32/99492_2.png) [@MPELectronique](https://discourse.nodered.org/u/MPELectronique)\
**Post date:** [29 November 2018 00:03 UTC](https://discourse.nodered.org/t/cannot-access-node-red/5225/13 "2018-11-29T00:03:42Z")

</div>

type that:  
npm uninstall node-red-contrib-pushover node-red-contrib-ovia-os

got that:  
npm WARN saveError ENOENT: no such file or directory, open '/home/pi/package.json'  
npm WARN enoent ENOENT: no such file or directory, open '/home/pi/package.json'  
npm WARN pi No description  
npm WARN pi No repository field.  
npm WARN pi No README data  
npm WARN pi No license field.

audited 938 packages in 11.606s  
found 30 vulnerabilities (1 low, 29 moderate)  
run `npm audit fix` to fix them, or `npm audit` for details

i dont understant .  
thanks.  
marc.

---

<div class="post-metadata">

**Author:** ![shrickus](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/shrickus/32/517_2.png) [@shrickus](https://discourse.nodered.org/u/shrickus)\
**Post date:** [29 November 2018 00:04 UTC](https://discourse.nodered.org/t/cannot-access-node-red/5225/14 "2018-11-29T00:04:42Z")

</div>

Looks like you did not run that from your `.node-red` directory.

---

<div class="post-metadata">

**Author:** ![MPELectronique](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/mpelectronique/32/99492_2.png) [@MPELectronique](https://discourse.nodered.org/u/MPELectronique)\
**Post date:** [29 November 2018 00:06 UTC](https://discourse.nodered.org/t/cannot-access-node-red/5225/15 "2018-11-29T00:06:32Z")

</div>

> [@shrickus](#):
>
> node-red

here are my directories:  
Desktop ngrok passwordfile  
Documents ngrok-stable-linux-arm.zip Pictures  
Downloads node\_latest\_armhf.deb Public  
install\_johnny5.txt node\_modules python\_games  
MagicMirror node-v8.9.0-linux-armv6l Scratch  
MagPi node-v8.9.0-linux-armv6l.tar.gz Templates  
mosquitto nohup.out Videos  
mosquitto.conf oldconffiles wunderground-sensehat  
Music package-lock.json  
pi@raspberrypi:~ $ ls  
Desktop ngrok passwordfile  
Documents ngrok-stable-linux-arm.zip Pictures  
Downloads node\_latest\_armhf.deb Public  
install\_johnny5.txt node\_modules python\_games  
MagicMirror node-v8.9.0-linux-armv6l Scratch  
MagPi node-v8.9.0-linux-armv6l.tar.gz Templates  
mosquitto nohup.out Videos  
mosquitto.conf oldconffiles wunderground-sensehat  
Music package-lock.json

i cant find it, i accidently erase it ☹  
thanks.  
marc.

---

<div class="post-metadata">

**Author:** ![shrickus](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/shrickus/32/517_2.png) [@shrickus](https://discourse.nodered.org/u/shrickus)\
**Post date:** [29 November 2018 00:16 UTC](https://discourse.nodered.org/t/cannot-access-node-red/5225/16 "2018-11-29T00:16:32Z")

</div>

It is a hidden directory, since it starts with a dot. Try `ls -la` from your home directory. Or use  
`cd ~/.node-red` and see if it puts you into that hidden dir. If so, then you should be able to run  
`npm uninstall node-red-contrib-pushover node-red-contrib-ovia-os`

---

<div class="post-metadata">

**Author:** ![MPELectronique](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/mpelectronique/32/99492_2.png) [@MPELectronique](https://discourse.nodered.org/u/MPELectronique)\
**Post date:** [30 November 2018 00:42 UTC](https://discourse.nodered.org/t/cannot-access-node-red/5225/17 "2018-11-30T00:42:47Z")

</div>

Thank You shrickus , problem solved 🙂  
🙂

Thanks.

good night 🙂  
Marc.

---

<div class="post-metadata">

**Author:** ![MPELectronique](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/mpelectronique/32/99492_2.png) [@MPELectronique](https://discourse.nodered.org/u/MPELectronique)\
**Post date:** [3 December 2018 17:01 UTC](https://discourse.nodered.org/t/cannot-access-node-red/5225/18 "2018-12-03T17:01:09Z")

</div>

# Hi there. Another problems... and node-red- not quite start ☹ here's the log 🙂 Welcome to Node-RED

## 3 Dec 11:59:56 - [info] Node-RED version: v0.19.5 3 Dec 11:59:56 - [info] Node.js version: v10.13.0 3 Dec 11:59:56 - [info] Linux 4.14.79-v7+ arm LE 3 Dec 11:59:57 - [info] Loading palette nodes 3 Dec 12:00:09 - [info] Polymer started at /polymer Mon, 03 Dec 2018 17:00:11 GMT node-telegram-bot-api deprecated Automatic enabling of cancellation of promises is deprecated. In the future, you will have to enable it yourself. See [https://github.com/yagop/node-telegram-bot-api/issues/319](https://github.com/yagop/node-telegram-bot-api/issues/319). at internal/modules/cjs/loader.js:688:30 Missing ENV var CONFIG\_PATH 3 Dec 12:00:18 - [info] Dashboard version 2.10.1 started at /ui 3 Dec 12:00:21 - [warn] ------------------------------------------------------ 3 Dec 12:00:21 - [warn] [node-red-contrib-moment-bug\_locale/moment] Type already registered 3 Dec 12:00:21 - [warn] [node-red-contrib-google-home-notify-volume-adjustable/google-notify] Type already registered 3 Dec 12:00:21 - [warn] ------------------------------------------------------ 3 Dec 12:00:21 - [info] Settings file : /home/pi/.node-red/settings.js 3 Dec 12:00:21 - [info] Context store : 'default' [module=memory] 3 Dec 12:00:21 - [info] User directory : /home/pi/.node-red 3 Dec 12:00:21 - [warn] Projects disabled : editorTheme.projects.enabled=false 3 Dec 12:00:22 - [info] Flows file : /home/pi/.node-red/flows\_raspberrypi.json 3 Dec 12:00:22 - [info] Server now running at [http://127.0.0.1:1880/](http://127.0.0.1:1880/) 3 Dec 12:00:22 - [warn]

## Your flow credentials file is encrypted using a system-generated key. If the system-generated key is lost for any reason, your credentials file will not be recoverable, you will have to delete it and re-enter your credentials. You should set your own key using the 'credentialSecret' option in your settings file. Node-RED will then re-encrypt your credentials file using your chosen key the next time you deploy a change.

3 Dec 12:00:22 - [info] Starting flows  
3 Dec 12:00:23 - [info] [google-config:643fae08.b4fb1] Reauthenticating YouTube API with AIzaSyBruo4RqbJ3XSkv1eBrF3FTH0SajC2MSHk  
3 Dec 12:00:24 - [info] Started flows  
3 Dec 12:00:24 - [red] Uncaught Exception:  
3 Dec 12:00:24 - Error: ENOENT: no such file or directory, stat '/var/spool/sms/incoming'  
nodered.service: Main process exited, code=exited, status=1/FAILURE  
nodered.service: Unit entered failed state.  
nodered.service: Failed with result 'exit-code'.  
nodered.service: Service hold-off time over, scheduling restart.  
Stopped Node-RED graphical event wiring tool.  
Started Node-RED graphical event wiring tool.  
3 Dec 12:00:27 - [info]

can you help me ?  
thanks.  
Marc.

---

<div class="post-metadata">

**Author:** ![ukmoose](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/ukmoose/32/13_2.png) [@ukmoose](https://discourse.nodered.org/u/ukmoose)\
**Post date:** [3 December 2018 20:55 UTC](https://discourse.nodered.org/t/cannot-access-node-red/5225/19 "2018-12-03T20:55:16Z")

</div>

Given you started again only 5 days ago. How did you install the two nodes it is now complaining about?  
Moment and google-home?

---

<div class="post-metadata">

**Author:** ![MPELectronique](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/mpelectronique/32/99492_2.png) [@MPELectronique](https://discourse.nodered.org/u/MPELectronique)\
**Post date:** [4 December 2018 00:29 UTC](https://discourse.nodered.org/t/cannot-access-node-red/5225/20 "2018-12-04T00:29:07Z")

</div>

with the palette manager in node-red.

how can i uninstall these ?  
thanks.  
marc.

[Next page](https://discourse.nodered.org/t/cannot-access-node-red/5225.md?page=2)