Failed to load node catalogue

#1

Hello!

I have installed Node-RED in a Raspberry Pi 3 using:

bash <(curl -sL https://raw.githubusercontent.com/node-red/raspbian-deb-package/master/resources/update-nodejs-and-nodered)

I have installed correctly, but when I go to Node-RED I can't install any package using Manage palette because it appears:
Failed to load node catalogue.
Check the browser console for more information


What can I do to solve this problem?

Thanks!

0 Likes

#2

I've just done a fresh install this morning and am having the same issue.
RPi 3 - Raspbian Stretch Lite - node v8.15.1 - node-red v 0.20.4

0 Likes

#3

Someone who already knows the answer may respond, but in the meantime, in a terminal run

node-red-stop
node-red-start

Then copy/paste the resulting log here, starting from the Welcome message. That may provide some clues.
Also do what it says in the error, check the browser console and see if anything useful there.

0 Likes

#4

Can't see anything untoward but always welcome a second opinion...

Starting as a systemd service.
Started Node-RED graphical event wiring tool.
5 Apr 12:34:25 - [info]
Welcome to Node-RED
===================
5 Apr 12:34:25 - [info] Node-RED version: v0.20.4
5 Apr 12:34:25 - [info] Node.js  version: v8.15.1
5 Apr 12:34:25 - [info] Linux 4.14.98-v7+ arm LE
5 Apr 12:34:26 - [info] Loading palette nodes
5 Apr 12:34:30 - [info] Settings file  : /home/pi/.node-red/settings.js
5 Apr 12:34:30 - [info] Context store  : 'default' [module=memory]
5 Apr 12:34:30 - [info] User directory : /home/pi/.node-red
5 Apr 12:34:30 - [warn] Projects disabled : editorTheme.projects.enabled=false
5 Apr 12:34:30 - [info] Flows file     : /home/pi/.node-red/flows_raspberrypi.json
5 Apr 12:34:30 - [info] Creating new flow file
5 Apr 12:34:30 - [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.
---------------------------------------------------------------------
5 Apr 12:34:30 - [info] Starting flows
5 Apr 12:34:30 - [info] Started flows
5 Apr 12:34:30 - [info] Server now running at http://127.0.0.1:1880/
0 Likes

#5

BTW @mikel.garmendia sorry for hijacking your post but I think we're looking for the same answers here. Hope you don't mind. :wink:

0 Likes

#6

Hi!

It doesn't matter to me @mturbutt!

This is my result after node-red-stop + node-red-start

Start Node-RED

Once Node-RED has started, point a browser at http://169.254.0.22: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

Starting as a systemd service.
Started Node-RED graphical event wiring tool.
5 Apr 12:53:31 - [info]
Welcome to Node-RED
===================
5 Apr 12:53:31 - [info] Node-RED version: v0.20.4
5 Apr 12:53:31 - [info] Node.js  version: v10.15.3
5 Apr 12:53:31 - [info] Linux 4.14.98-v7+ arm LE
5 Apr 12:53:32 - [info] Loading palette nodes
5 Apr 12:53:35 - [s7comm-Error] - Installation of Module net-keepalive failed because we might be on the                                                                                      wrong OS. OS=linux
5 Apr 12:53:35 - [s7comm-Info] - Debug configuration for logLevelNodeS7:{"debug":0,"silent":true}
5 Apr 12:53:35 - [s7comm-Info] - Debug configuration for logLevelNodeRED:{"debug":2,"silent":true}
5 Apr 12:53:36 - [info] Settings file  : /home/ii40asset/.node-red/settings.js
5 Apr 12:53:36 - [info] Context store  : 'default' [module=memory]
5 Apr 12:53:36 - [info] User directory : /home/ii40asset/.node-red
5 Apr 12:53:36 - [warn] Projects disabled : editorTheme.projects.enabled=false
5 Apr 12:53:36 - [info] Flows file     : /home/ii40asset/.node-red/flows_ii40asset.json
5 Apr 12:53:36 - [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.
---------------------------------------------------------------------
5 Apr 12:53:36 - [info] Starting flows
1 Like

#7

Browser console lists

https://catalogue.nodered.org/catalogue.json - "SyntaxError: JSON Parse error: Unexpected identifier \"object\""

0 Likes

#8

Hi @ukmoose
I don't understand very well what I have to do.
How can I check the browser console?
Thanks!

0 Likes

#9

Sorry - 0.20.4 broke something. 0.20.5 coming shortly.

1 Like

#10

It was more for @dceejay or @knolleary as it looked as if it is an issue in 20.4.

But to answer your question... :wink: its usually under the Developer/ Develop menu in your browser.

0 Likes

#11

@knolleary Phew! I thought it was me. :joy:
Been running node-red for 2 years and wanted a fresh install before setting my new house.

0 Likes

#12

Where is the best place to check (or better still, get notified) of new releases please?

0 Likes

#13
1 Like

#14

The get announced in the #news category.

1 Like

#15

Got it, thanks. Following that now.

0 Likes

#16

0.20.5 now published with the fix. Sorry for the inconvenience.

3 Likes

#17

That did it! Thanks a million.

@mikel.garmendia if you re-run in terminal:

$ bash <(curl -sL https://raw.githubusercontent.com/node-red/raspbian-deb-package/master/resources/update-nodejs-and-nodered)

You'll get the new release 0.20.5.

I've just tested it and it's working fine now. :slight_smile:

1 Like

#18

I have updated the Node-RED version it works fine!
Thank you very much @mturbutt and @knolleary :wink:

1 Like

#19

Hi,
Complete n00b here, I've ended up here as I'm following the Node-RED: basics to bots online course (https://courses.competencies.ibm.com/courses/course-v1:developerWorks+CB105EN+v1/info)

I'm too seeing the "Failed to load node catalog" message when using the Node-Red in the cloud. The console logs are as follows:

https://catalogue.nodered.org/catalogue.json SyntaxError: Unexpected token o in JSON at position 1
success @ red.min.js:16
j @ vendor.js:2
fireWith @ vendor.js:2
x @ vendor.js:5
b @ vendor.js:5
XMLHttpRequest.send (async)
(anonymous) @ VM21:1
send @ vendor.js:5
ajax @ vendor.js:5
(anonymous) @ red.min.js:16
j @ red.min.js:16
e @ red.min.js:16
(anonymous) @ red.min.js:16
open @ red.min.js:16
o @ red.min.js:16
show @ red.min.js:16
n @ red.min.js:16
(anonymous) @ red.min.js:16
c @ red.min.js:16
(anonymous) @ red.min.js:16
dispatch @ vendor.js:4
r.handle @ vendor.js:4

I'm using Chrome...but seeing the same issue on any browser or machine that I'm using.

Is there something I'm doing wrong? Is it possible to add nodes to the palette if using the cloud version of Node-Red?

Any help gratefully received, thanks in advance...

0 Likes

#20

This was a bug that was briefly introduced in 0.20.4 and fixed in 0.20.5.

Docs for upgrading are here: https://nodered.org/docs/platforms/bluemix

0 Likes