Fix bug in detecting set credential secret #1734
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
frenck
added
the
bugfix
This was referenced Nov 15, 2023
|
Just updated node red to 16.0.1 and all my flows are gone: Edit: Just found this issue: #1736 |
|
after updating to 16.0.1 my flows disappeared, I updated to 16.0.2 but I still get the same message: Credentials could not be decrypted The flow credential file is encrypted, but the project's encryption key is missing or invalid. The flow credential file will be reset on the next deployment. Any existing flow credentials will be cleared. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Proposed Changes
Fixes a typo in a variable name that prevents the credential secret from working.
fixes #1733