Bug when updating NodeRED v1.4.3

George_Santiago · February 27, 2023, 11:19am

I updated my NodeRED (before 1.4.1) to version 1.4.3, but it is generating an error. See log below:
I’m trying to identify and fix it.

27 Feb 11:11:58 - [info] Loading palette nodes
27 Feb 11:11:59 - [info] Settings file  : /data/settings.js
27 Feb 11:11:59 - [info] Context store  : 'default' [module=memory]
27 Feb 11:11:59 - [info] User directory : /data
27 Feb 11:11:59 - [warn] Projects disabled : editorTheme.projects.enabled=false
27 Feb 11:11:59 - [info] Flows file     : /data/flows.json
27 Feb 11:11:59 - [info] Server now running at http://127.0.0.1:1880/
27 Feb 11:11:59 - [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.
---------------------------------------------------------------------

27 Feb 11:11:59 - [info] Starting flows
27 Feb 11:11:59 - [error] [thinger-server:TOKEN_NODERED] Invalid JWT Token
27 Feb 11:11:59 - [error] [server-events:89f0142276739be7] server-events: check thinger server configuration
27 Feb 11:11:59 - [error] [server-events:ed3dabc182294cc4] server-events: check thinger server configuration
27 Feb 11:11:59 - [error] [server-events:deveci_property_update] server-events: check thinger server configuration
27 Feb 11:11:59 - [info] Started flows

George_Santiago · February 27, 2023, 11:32am

I tried:

Create a new Token (did not work);
Go back to version 1.4.1 (didn’t work).
HELP!!!

jaimebs · February 27, 2023, 11:40am

Hi @George_Santiago

We are looking into it, will let you know asap.

George_Santiago · February 27, 2023, 11:42am

The newly created token “TOKEN_NODERED_v143” is also returned as invalid.

27 Feb 11:33:50 - [info] 

Welcome to Node-RED
===================

27 Feb 11:33:50 - [info] Node-RED version: v3.0.2
27 Feb 11:33:50 - [info] Node.js  version: v16.16.0
27 Feb 11:33:50 - [info] Linux 5.4.0-1083-aws x64 LE
27 Feb 11:33:51 - [info] Loading palette nodes
27 Feb 11:33:52 - [info] Settings file  : /data/settings.js
27 Feb 11:33:52 - [info] Context store  : 'default' [module=memory]
27 Feb 11:33:52 - [info] User directory : /data
27 Feb 11:33:52 - [warn] Projects disabled : editorTheme.projects.enabled=false
27 Feb 11:33:52 - [info] Flows file     : /data/flows.json
27 Feb 11:33:52 - [info] Server now running at http://127.0.0.1:1880/
27 Feb 11:33:52 - [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.
---------------------------------------------------------------------

27 Feb 11:33:52 - [info] Starting flows
27 Feb 11:33:52 - [error] [thinger-server:TOKEN_NODERED] Invalid JWT Token
27 Feb 11:33:52 - [error] [thinger-server:TOKEN_NODERED_v143] Invalid JWT Token
27 Feb 11:33:52 - [error] [server-events:89f0142276739be7] server-events: check thinger server configuration
27 Feb 11:33:52 - [error] [server-events:ed3dabc182294cc4] server-events: check thinger server configuration
27 Feb 11:33:52 - [error] [server-events:deveci_property_update] server-events: check thinger server configuration
27 Feb 11:33:52 - [info] Started flows

George_Santiago · February 27, 2023, 11:45am

The only measure I haven’t tried (and I’m afraid to do) is to remove the plugin and install again.
As I have many flows, I am afraid of something breaking when importing the JSON with the settings in the new instance.

jaimebs · February 27, 2023, 11:50am

I wouldn’t remove the plugin, we are currently publishing the fix and will be available in a few minutes, hold on tight.

George_Santiago · February 27, 2023, 12:00pm

Just to let you know:

I deleted the NodeRed token on the “Access Token” screen to force the creation of a new token, but without success. NodeRED 1.4.3 did not create a new token on the “Access Token” screen after creating a new credential: “TOKEN_NODERED_v143_NEW” , configured with $(THINGER_HOST) and $(THINGER_TOKEN_NODE_RED_PLUGIN)

27 Feb 11:55:18 - [info] Starting flows
27 Feb 11:55:18 - [error] [thinger-server:TOKEN_NODERED_v143_NEW] Invalid JWT Token
27 Feb 11:55:18 - [error] [server-events:89f0142276739be7] server-events: check thinger server configuration
27 Feb 11:55:18 - [error] [server-events:ed3dabc182294cc4] server-events: check thinger server configuration
27 Feb 11:55:18 - [error] [server-events:deveci_property_update] server-events: check thinger server configuration
27 Feb 11:55:18 - [info] Started flows

jaimebs · February 27, 2023, 12:16pm

In the meantime, if you’ve removed the autoprovisioned token for Node-RED, try clicking on upgrade on the plugin (do not remove the plugin), even if it is for the same version you have installed, and it should recreate the token and pass it to the environment of Node-RED.

The version of Node-RED will not make a difference, so I recommend you to stay with the latest one (1.4.3).

Sorry for the inconvenience

George_Santiago · February 27, 2023, 12:21pm

It worked!!!
After deleting the self-provisioned Token on the “Access Token” screen and clicking on UPDATE on the Plugin screen (forcing the creation of a new token on “Access Token”), NodeRed returned to work correctly.

Thank you very much, @jaimebs