Node-Red is Installed with all defaults.
Normal operation until "projects" is enabled.
Then when starting I get:
Graph showing "Loading Nodes 1/59 that stops at 59/59"
Error: Failed to load ‘node-red/comment’
Normal operation resumes after disabling "projects" and restarting node-red.
Node-RED version: v1.2.7
Node.js version: v14.15.3
Dashboard version 2.26.1 started at /ui
Windows_NT 10.0.18363 x64 LE
Win10 pro v1909 6700K w/ 32 GB Ram
Firefox, Chrome and Edge give identical results.
Have uninstalled and reinstalled node-red using Power Shell w/ Admin - forced all new default directories
With a new node-red install and projects enabled:
PS C:\Windows\system32> node-red
8 Jan 21:29:03 - [info]
Welcome to Node-RED
8 Jan 21:29:03 - [info] Node-RED version: v1.2.7
8 Jan 21:29:03 - [info] Node.js version: v14.15.3
8 Jan 21:29:03 - [info] Windows_NT 10.0.18363 x64 LE
8 Jan 21:29:04 - [info] Loading palette nodes
8 Jan 21:29:05 - [info] Dashboard version 2.26.1 started at /ui
8 Jan 21:29:05 - [info] Settings file : C:\Users\FLA.node-red\settings.js
8 Jan 21:29:05 - [info] Context store : 'default' [module=memory]
8 Jan 21:29:05 - [info] User directory : \Users\FLA.node-red
8 Jan 21:29:05 - [warn] No active project : using default flows file
8 Jan 21:29:05 - [info] Flows file : \Users\FLA.node-red\flows_FLA.json
8 Jan 21:29:05 - [info] Server now running at http://127.0.0.1:1880/
8 Jan 21:29:05 - [info] Starting flows
8 Jan 21:29:05 - [info] Started flows
8 Jan 21:29:05 - [info] [udp in:f2742f39.0019b8] udp listener at 0.0.0.0:4992
8 Jan 21:31:29 - [info] Stopping flows
8 Jan 21:31:29 - [info] [udp in:f2742f39.0019b8] udp listener stopped
8 Jan 21:31:29 - [info] Stopped flows
8 Jan 21:31:29 - [info] Starting flows
8 Jan 21:31:29 - [info] Started flows
8 Jan 21:31:29 - [info] [udp in:f2742f39.0019b8] udp listener at 0.0.0.0:4992
8 Jan 22:33:32 - [info] Stopping flows
8 Jan 22:33:32 - [info] [udp in:f2742f39.0019b8] udp listener stopped
8 Jan 22:33:32 - [info] Stopped flows
PS C:\Windows\system32> node-red
8 Jan 22:33:38 - [info]
With projects disabled:
Welcome to Node-RED
8 Jan 22:33:38 - [info] Node-RED version: v1.2.7
8 Jan 22:33:38 - [info] Node.js version: v14.15.3
8 Jan 22:33:38 - [info] Windows_NT 10.0.18363 x64 LE
8 Jan 22:33:39 - [info] Loading palette nodes
8 Jan 22:33:39 - [info] Dashboard version 2.26.1 started at /ui
8 Jan 22:33:39 - [info] Settings file : C:\Users\FLA.node-red\settings.js
8 Jan 22:33:39 - [info] Context store : 'default' [module=memory]
8 Jan 22:33:39 - [info] User directory : \Users\FLA.node-red
8 Jan 22:33:39 - [warn] Projects disabled : editorTheme.projects.enabled=false
8 Jan 22:33:39 - [info] Flows file : \Users\FLA.node-red\flows_FLA.json
8 Jan 22:33:39 - [info] Server now running at http://127.0.0.1:1880/
8 Jan 22:33:39 - [info] Starting flows
8 Jan 22:33:39 - [info] Started flows
8 Jan 22:33:39 - [info] [udp in:f2742f39.0019b8] udp listener at 0.0.0.0:4992
Thanks for any trouble-shooting suggestions as I am very new to this!
If you have not already done so then clear the browser cache, do a full page refresh in the browser and see if that fixes it.
If not then what browser are you using? Are you able to try another browser (not IE)?
If still not then have a look in the browser developer console to see if there are any errors there.
Hi Colin:
Thanks for the help.
I restarted windows and then cleared FireFox as you suggested but got the same failure.
After clearing the previous errors from the Browser Console and re-starting Node-Red it shows:
Content Security Policy: Ignoring “'unsafe-inline'” within script-src: ‘strict-dynamic’ specified
Content Security Policy: Ignoring “https:” within script-src: ‘strict-dynamic’ specified
Content Security Policy: Ignoring “http:” within script-src: ‘strict-dynamic’ specified
You say it is loaded with all the defaults, but I see you have got a flow running. Did it work previously? If so then start node-red using node-red --safe
which will start without running the flows. If that is ok then undo whatever was the last thing you did and deploy.
Alternatively restore the flows file from your most recent backup.
Using node-red --safe had the same results. I even restarted windows.
The problem is with projects enabled - OK when disabled.
Projects had worked before but not initially. I could start the flow with projects disabled, then enable it in settings.js and restart node-red. The flow would then reconnect with projects enabled. The project feature would work for days until I would, say import a new module such as random.
Yesterday, an import again disabled projects. I removed node-red and reinstalled it. While the Flows are now much faster and the snap to grid feature now functions, I can no longer get projects to work even as before.
Rename the .node-red folder so you start with a clean sheet. Then try again and make sure it starts up ok. Then enable projects in settings.js and restart node red.
I suspect that it is one of the installed nodes (which are in .node-red/node_modules) that is causing the problem.
... err how can that happen ? projects is enabled in your settings file... any normal import can't touch that. Not sure what you are importing but that doesn't sound right to me.
When I was able to have projects working and imported a new node, sometimes the flow UI would no longer load. As soon as I would disable projects in the settings.js file, The flow UI would again load. Then enabling projects in the settings.js file again causes the flow UI to hang.
I have projects enabled now. Disabled node-red-contrib-multiproject and the dashboard nodes in the process. However after enabling the dashboard nodes, I get the error:
The workspace contains some nodes that are not properly configured:
Well, that would be my very first port of call if I were having problems like this. It hasn't been updated in over 4 years and the chances of it behaving well are pretty low.
Get rid of that first before trying anything else.