Currently running node-RED on a local Raspberry Pi, and in the process of moving all flows etc to a Oracle VM. In the Pi, I've been using 'Projects', but in the VM I will not be using 'Projects'. So, I've created an archive comprising of the following files from the Pi; flows_raspberrypi_cred.jso…

[image] zenofmud: Just to let you know. i reproduced this pi with projects -> macOS no projects What steps did you take exactly? What files did you copy? Did you copy and properties from one file to another? Let me try to explain all the different bits. Without Projects if credentialSecr…

Maybe the auto-generated credentialSecret is stored in there. That would explain it.

I just checked... it is indeed in the .config.json as key _credentialSecret So once you set credentialSecret in your settings.js with your own secret, it will be removed from there at the next launch and the existing credentials will be re-encrypted with your own key. For reference, these are the …

[image] zenofmud: in this case the original flow was NOT in a project. I then realized I had not moved the .config.json . Once I did, it worked fine. Thanks for testing Paul. I think that the issue maybe in the last few lines of the .config.json file; "projects": { "projects": { "Maste…

You can try to use the credentialSecret from the "Master_flow" section. That is the actual secret that was used to encrypt the credentials. Just set it as credentialSecret in the settings.js on the new machine. And, on the new machine, look out for the _credentialSecret in .config.json. I think it…

I think by now it would be best to start the migration again with a fresh Node-RED workspace on the target machine. I have some steps in mind that you could follow. I can write them down, if you want.

Thanks, but first I'd be interested to know what I asked in my last post, as that could be the issue.

None of that is in the json since there were no projects involved. Try taking it out.

That's what I thought. The .config.json keeps different settings per project. And the key "activeProject": "Master_flow" determines the project that is launched at start-up. So to migrate from a projects to non-projects workspace, we need to piece all this data together into the right place.

[image] zenofmud: Try taking it out. Still the same with that section taken out unfortunately. It seems strange that the "mysecret" in .config.json, isn't a hash, it's a single word password "credentialSecret": "mysecret"

Strange, but it should not matter. As soon as it is set to any string, it will be used as encryption key.

Node-RED

Node-RED Forum

Moving node-RED - Failed to decrypt credentials

General

Paul-Reed 13 November 2019 12:10 27

That's good, perhaps @knolleary has thoughts on this.

Moving credentials to another machine (v3.0.2)

Topic		Replies	Views
Moving credentials to another machine (v3.0.2) General	3	716	30 August 2022
Flow credentials cannot be decrypted General	8	2600	31 May 2022
Your flow credentials file is encrypted using a system-generated key General	57	33793	28 July 2021
Copying everything between two NR instances General	49	4097	15 September 2020
Credentials could not be decrypted General	6	3729	21 March 2020

Copyright OpenJS Foundation and Node-RED contributors. All rights reserved. The OpenJS Foundation has registered trademarks and uses trademarks. For a list of trademarks of the OpenJS Foundation, please see our Trademark Policy and Trademark List. Trademarks and logos not indicated on the list of OpenJS Foundation trademarks are trademarks™ or registered® trademarks of their respective holders. Use of them does not imply any affiliation with or endorsement by them.

Moving node-RED - Failed to decrypt credentials

Related topics