Influxdb2 always in error

Dear all, I have a strange behavior of Influxdb2, every time I open the webpage to Node-RED the Influxdb2 node shows up with red error sign. But if I only refresh the settings, then it goes away. If I refresh the webpage it comes back, and so on...
I'm running Node-RED as a container under Docker, as well as Influxdb2.

Screenshot 2023-12-28 061948

Screenshot 2023-12-28 062018

Screenshot 2023-12-28 062043

Thank you in advance for your answers.

BR Phoenix

Can you show us the node red startup log please? That is the one that starts with the Welcome to Node Red message. That may tell us something useful.

of course

Welcome to Node-RED

28 Dec 08:20:22 - [info] Node-RED version: v3.0.2
28 Dec 08:20:22 - [info] Node.js version: v16.20.1
28 Dec 08:20:22 - [info] Linux 5.10.0-26-amd64 x64 LE
28 Dec 08:20:23 - [info] Loading palette nodes
using @peculiar/webcrypto
28 Dec 08:20:25 - [info] Dashboard version 3.6.1 started at /ui
28 Dec 08:20:25 - [info] Settings file : /data/settings.js
28 Dec 08:20:25 - [info] Context store : 'default' [module=memory]
28 Dec 08:20:25 - [info] User directory : /data
28 Dec 08:20:25 - [warn] Projects disabled : editorTheme.projects.enabled=false
28 Dec 08:20:25 - [info] Flows file : /data/flows.json
28 Dec 08:20:25 - [info] Server now running at http://127.0.0.1:1880/
28 Dec 08:20:25 - [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.

28 Dec 08:20:25 - [info] Starting flows

I suggest upgrading to the latest version of node-red (3.1.3). It may not make a difference, but is certainly worth doing. Are you using the latest version of the influxdb node?

What does the influx node config look like?

Do the influx nodes function correctly?

Node-RED and Influx upgraded to newest.

DOCKER_INFLUXDB_INIT_CLI_CONFIG_NAME default
GOSU_VER 1.12
INFLUX_CLI_VERSION 2.7.3
INFLUX_CONFIGS_PATH /etc/influxdb2/influx-configs
INFLUXD_INIT_PING_ATTEMPTS 600
INFLUXD_INIT_PORT 9999
INFLUXDB_VERSION 2.7.1
PATH /usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
FLOWS flows.json
NODE_PATH /usr/src/node-red/node_modules:/data/node_modules
NODE_RED_VERSION v3.0.2
NODE_VERSION 16.20.0
PATH /usr/src/node-red/node_modules/.bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
YARN_VERSION 1.22.19

same behavior
Screenshot 2023-12-28 102921
Screenshot 2023-12-28 102940

The influx nodes are receiving data and I see the data in influx, that's no Problem.

No it isn't.

Well I pulled the latest

Screenshot 2023-12-28 105001

Screenshot 2023-12-28 105047

That is not running in docker, look at the path

What does the one running in Docker say?

29 Dec 05:23:48 - [info] 
Welcome to Node-RED
===================
29 Dec 05:23:48 - [info] Node-RED version: v3.1.3
29 Dec 05:23:48 - [info] Node.js  version: v16.20.2
29 Dec 05:23:48 - [info] Linux 5.10.0-26-amd64 x64 LE
29 Dec 05:23:48 - [info] Loading palette nodes
using @peculiar/webcrypto
29 Dec 05:23:51 - [info] Dashboard version 3.6.1 started at /ui
29 Dec 05:23:51 - [info] Settings file  : /data/settings.js
29 Dec 05:23:51 - [info] Context store  : 'default' [module=memory]
29 Dec 05:23:51 - [info] User directory : /data
29 Dec 05:23:51 - [warn] Projects disabled : editorTheme.projects.enabled=false
29 Dec 05:23:51 - [info] Flows file     : /data/flows.json
29 Dec 05:23:51 - [info] Server now running at http://127.0.0.1:1880/
29 Dec 05:23:51 - [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.
---------------------------------------------------------------------
29 Dec 05:23:51 - [info] Starting flows

But in Portainer still says it is the older one

What does it say at the bottom of the dropdown menu in the node-red editor? That will tell you what you are actually using.

You mean this?
Screenshot 2023-12-28 105001
Then 3.13

Yes, so you are running 3.1.3, whatever portainer says.

What version of node-red-contrib-influxdb are you using? You can see that in Manage Palette.

image

0.6.1 is the latest, so it isn't that.

If you open the Developer Tools console in the browser and refresh the page do you see any errors there?

Are you able to try a different browser?

Do not really know where to look

Console is where any errors would surface

So now I don’t see any
Or am I on the wrong page?

no errors ...

That looks ok. Select the failing node and Export it and paste it here. Then we can import and see if we can replicate it.

[
    {
        "id": "aa95626bc84a6eee",
        "type": "influxdb out",
        "z": "fc779838.82f878",
        "influxdb": "c14e58b875fb7716",
        "name": "",
        "measurement": "servercpu",
        "precision": "",
        "retentionPolicy": "",
        "database": "database",
        "precisionV18FluxV20": "ms",
        "retentionPolicyV18Flux": "",
        "org": "HeimCRsr",
        "bucket": "temperature",
        "x": 830,
        "y": 320,
        "wires": []
    },
    {
        "id": "c14e58b875fb7716",
        "type": "influxdb",
        "hostname": "127.0.0.1",
        "port": "8086",
        "protocol": "http",
        "database": "",
        "name": "Server",
        "usetls": false,
        "tls": "",
        "influxdbVersion": "2.0",
        "url": "http://192.168.1.220:8086",
        "rejectUnauthorized": false
    }
]

Your influxdb server node is missing a hidden field database. Did you create that dbconfig in an earlier version and upgrade it, or something like that?
If, in an influxdb Out node, you click the server field and select Add New and then create a new one with the same settings then it should fix the problem. Then change all the other influx nodes to use the new one. Finally you can delete the unused one in Configuration Nodes in the node red dropdown menu.