Tabs get stuck on cursor

Hi everyone,
Last year, I made an app with Node-RED, but by mistake I changed some configuration of the Node-RED deep files and now I have the problem that I click on any tab, flow and nodes, mainly, and they get stuck on my cursor, they don't drop as long as I click on the right button. So, if I click on the right button and I click on any flow, it gets stuck again... It is like that I drag whatever I click on...

Could anyone help me?

Thank you so much!

can you explain what you mean by this?

If you changed some of the node-red core programs, go back and examine what you did. If you don't remember, get a fresh copy and do a comprehensive of what you have with the original code.

The fact is that I copied all the files and what I remember is that there was a .json where I enabled and disabled some things by mistake. I can get the .json again, but it is so extense, so it is so confused to know what parameter is exactly

Are you referring to the settings.js file? If so t is in the .node-red folder.

What platform are you running node-red on ?

I am just controlling some PLC from industrialshields, but I put Node-RED on a web server.

I checked the settings.js file, and it is not that file... It was some like app.min.js, and I don't even know if it is the app.min.js, maybe it could be, but I don't really understand web language, so I don't really know the parameters

That's not much help.

  1. how did you install Node-RED? i.e. what commands did you use?
  2. What device (raspberry pi?, pc?, mac?) did you install it on?
  3. Stop and start NR and copy the startup log and paste it to a reply.

I'm pretty sure the parameter should be somewhere in @node-red/editor-client/...


1- sudo npm install -g --unsafe-perm node-red
2- Ubuntu 20.04 LTS
3- 19 Mar 10:27:30 - [info]

Welcome to Node-RED

19 Mar 10:27:30 - [info] Node-RED version: v1.2.2
19 Mar 10:27:30 - [info] Node.js  version: v10.19.0
19 Mar 10:27:30 - [info] Linux 5.8.0-45-generic x64 LE
19 Mar 10:27:31 - [info] Loading palette nodes
19 Mar 10:27:31 - [info] Dashboard version 2.24.0 started at /ui
19 Mar 10:27:31 - [info] Settings file  : /home/qmf/.node-red/settings.js
19 Mar 10:27:31 - [info] Context store  : 'default' [module=memory]
19 Mar 10:27:31 - [info] User directory : /home/X/.node-red
19 Mar 10:27:31 - [warn] Projects disabled : editorTheme.projects.enabled=false
19 Mar 10:27:31 - [info] Flows file     : /home/X/.node-red/flows_X.json
19 Mar 10:27:31 - [info] Server now running at
19 Mar 10:27:31 - [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.


19 Mar 10:27:31 - [info] Starting flows
19 Mar 10:27:31 - [info] Started flows
````Preformatted text`

Have you just re-run that npm install command? If so then it doesn't make sense that it has installed v1.2.2 as it should have installed 1.2.9.

Also I see that you have an obsolete version of node.js, which suggests that you have not followed the recommended method for installing on Ubuntu (and the Pi and other Debian based distributions). If you run the script there it should update you to recommended versions of nodejs and node-red. By re-installing node-red it will remove any hacks you accidentally made to it.

Thank you! I will try it and I will let you know!

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