# This is a new (weird) error

**URL:** <https://discourse.nodered.org/t/this-is-a-new-weird-error/3675>\
**Category:** General\
**Created:** [4 October 2018 06:21 UTC](https://discourse.nodered.org/t/this-is-a-new-weird-error/3675 "2018-10-04T06:21:31Z")\
**Posts on this page:** 9\
**Page:** 1

<div class="post-metadata">

**Author:** ![Trying\_to\_learn](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/trying_to_learn/32/28400_2.png) [@Trying\_to\_learn](https://discourse.nodered.org/u/Trying_to_learn)\
**Post date:** [4 October 2018 06:21 UTC](https://discourse.nodered.org/t/this-is-a-new-weird-error/3675/1 "2018-10-04T06:21:31Z")

</div>

While optimising some flows, etc, I got this error:

```auto
FileError: 'http://192.168.0.99:1880/ui/css/app.min.less' wasn't found (0)

in app.min.less 

```

Google isn't that helpful.

Anyone?

---

<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:** [5 October 2018 08:09 UTC](https://discourse.nodered.org/t/this-is-a-new-weird-error/3675/2 "2018-10-05T08:09:43Z")

</div>

Try restarting node red and force a full refresh of the browser. If it still happens then more information is required I think.

---

<div class="post-metadata">

**Author:** ![Trying\_to\_learn](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/trying_to_learn/32/28400_2.png) [@Trying\_to\_learn](https://discourse.nodered.org/u/Trying_to_learn)\
**Post date:** [5 October 2018 08:11 UTC](https://discourse.nodered.org/t/this-is-a-new-weird-error/3675/3 "2018-10-05T08:11:43Z")

</div>

Thanks.

But in the mean time, it has gone away.

I probably rebooted the machine and all started working again.

---

<div class="post-metadata">

**Author:** ![amusso](https://avatars.discourse-cdn.com/v4/letter/a/edb3f5/32.png) [@amusso](https://discourse.nodered.org/u/amusso)\
**Post date:** [30 May 2019 12:46 UTC](https://discourse.nodered.org/t/this-is-a-new-weird-error/3675/4 "2019-05-30T12:46:49Z")

</div>

The post is old......

I have the same problem on a Tablet with android, just after to run node-red update.

Any comment or help?

---

<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:** [30 May 2019 13:00 UTC](https://discourse.nodered.org/t/this-is-a-new-weird-error/3675/5 "2019-05-30T13:00:40Z")

</div>

Have you tried resetting the browser cache?

---

<div class="post-metadata">

**Author:** ![amusso](https://avatars.discourse-cdn.com/v4/letter/a/edb3f5/32.png) [@amusso](https://discourse.nodered.org/u/amusso)\
**Post date:** [30 May 2019 13:05 UTC](https://discourse.nodered.org/t/this-is-a-new-weird-error/3675/6 "2019-05-30T13:05:51Z")

</div>

Yes but there were no changes

also try other browsers (opera mini, Chrome, etc) and shows the same error ☹

---

<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:** [30 May 2019 14:30 UTC](https://discourse.nodered.org/t/this-is-a-new-weird-error/3675/7 "2019-05-30T14:30:15Z")

</div>

Then please try restarting Node-RED and posting the startup log here

---

<div class="post-metadata">

**Author:** ![amusso](https://avatars.discourse-cdn.com/v4/letter/a/edb3f5/32.png) [@amusso](https://discourse.nodered.org/u/amusso)\
**Post date:** [30 May 2019 17:35 UTC](https://discourse.nodered.org/t/this-is-a-new-weird-error/3675/8 "2019-05-30T17:35:47Z")

</div>

This is the log

My node-red run on raspberrypi B 3

* * *

pi@raspberrypi:~ $ node-red-start

Start Node-RED

Once Node-RED has started, point a browser at xxxxxxxxxxx: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 :flows.nodered.org

# Starting as a systemd service. Started Node-RED graphical event wiring tool. 30 May 14:26:04 - [info] Welcome to Node-RED

## 30 May 14:26:04 - [info] Node-RED version: v0.20.5 30 May 14:26:04 - [info] Node.js version: v8.11.1 30 May 14:26:04 - [info] Linux 4.19.42-v7+ arm LE 30 May 14:26:07 - [info] Palette editor disabled : npm version too old. Requires npm \>= 3.x 30 May 14:26:07 - [info] Loading palette nodes Thu, 30 May 2019 17:26:12 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 [github.com/yagop/node-telegram-bot-api/issues/319](http://github.com/yagop/node-telegram-bot-api/issues/319). at module.js:652:30 30 May 14:26:18 - [info] Dashboard version 2.14.0 started at /ui 30 May 14:26:19 - [info] Settings file : /home/pi/.node-red/settings.js 30 May 14:26:19 - [info] Context store : 'default' [module=memory] 30 May 14:26:19 - [info] User directory : /home/pi/.node-red 30 May 14:26:19 - [warn] Projects disabled : set editorTheme.projects.enabled=true to enable 30 May 14:26:19 - [info] Flows file : /home/pi/.node-red/flows\_raspberrypi.json 30 May 14:26:19 - [info] Server now running at [http://127.0.0.1:1880/](http://127.0.0.1:1880/) 30 May 14:26:19 - [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.

## 30 May 14:26:19 - [info] Starting flows WF2 AC: : WF2 AC: : WF2 AC: : 30 May 14:26:30 - [info] Started flows 30 May 14:26:31 - [error] serial port /dev/rfcomm2 error: Error: Error: No such file or directory, cannot open /dev/rfcomm2 30 May 14:26:31 - [info] serial port /dev/ttyACM0 opened at 9600 baud 8N1 30 May 14:26:31 - [info] serial port /dev/ttyUSB0 opened at 9600 baud 8N1 30 May 14:26:31 - [error] [function:Output Filter: Temperatura] SyntaxError: Unexpected token u in JSON at position 1 30 May 14:26:31 - [error] [function:Output Filter: Humedad] SyntaxError: Unexpected token u in JSON at position 1 30 May 14:26:31 - [info] [mqtt-broker:61e2e87f.71cd08] Connected to broker: mqtt://localhost:1883

 ![error](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/2X/2/222a76dcd293275919a7d39a168f45d8d5807921.jpeg)

---

<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:** [30 May 2019 20:03 UTC](https://discourse.nodered.org/t/this-is-a-new-weird-error/3675/9 "2019-05-30T20:03:40Z")

</div>

So how did you update node-RED?  
As this is on a raspberry pi did you use the upgrade script as suggested in the raspberry pi age in the docs?  
If not try running the script which should fix some of the issues in the logs.