"Error: Invalid "keyPath" option supplied."

[sama...@gmail.com]

Hello,

I have problem to set the keypath in Node-RED.

The installation directory of Node-RED is

/root/.node-red

The start of Node-RED application is from

/root/app

The security certificates, keys and root-CA files are stored in

/root/app/certs

The problem is whatever I set the path to the security files I get the error message "Error: Invalid "keyPath" option supplied.".
I get the same error message even when I copied the folder /certs to be in the installation directory of Node-RED.

/root/.node-red/certs

My question is: How to specify the path so that Node-RED can accept it to find the security files?

[Julian Knight]

This may help: https://github.com/TotallyInformation/SelfSigned-Cert-Creator

[Graph Sam]

Thanks Julian,

Whatever I set the path to the private key I get the same keypath error. If I run javascript file with the same keys it works without any error.

The problem does exist when I run node-red.

Could you give an example how to set the path?

--
http://nodered.org
 
Join us on Slack to continue the conversation: http://nodered.org/slack
---
You received this message because you are subscribed to a topic in the Google Groups "Node-RED" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/node-red/RJDesFhFzec/unsubscribe.
To unsubscribe from this group and all its topics, send an email to node-red+unsubscribe@googlegroups.com.
To post to this group, send email to node...@googlegroups.com.
Visit this group at https://groups.google.com/group/node-red.
To view this discussion on the web, visit https://groups.google.com/d/msgid/node-red/903f3a24-b502-4e3f-a209-c5720e499977%40googlegroups.com.

For more options, visit https://groups.google.com/d/optout.

[Nick O'Leary]

What are you setting the path to? There shouldn't be anything special about it ... Just a path to the cert file.

Nick

To unsubscribe from this group and all its topics, send an email to node-red+u...@googlegroups.com.

To post to this group, send email to node...@googlegroups.com.
Visit this group at https://groups.google.com/group/node-red.

To view this discussion on the web, visit https://groups.google.com/d/msgid/node-red/903f3a24-b502-4e3f-a209-c5720e499977%40googlegroups.com.

For more options, visit https://groups.google.com/d/optout.

--

http://nodered.org
 
Join us on Slack to continue the conversation: http://nodered.org/slack
---

You received this message because you are subscribed to the Google Groups "Node-RED" group.
To unsubscribe from this group and stop receiving emails from it, send an email to node-red+u...@googlegroups.com.

To post to this group, send email to node...@googlegroups.com.
Visit this group at https://groups.google.com/group/node-red.

To view this discussion on the web, visit https://groups.google.com/d/msgid/node-red/CAD5DeLC6GriAjOD74Hbu-WMj07Gx-0ASxuu1CFE-awBapD6rtA%40mail.gmail.com.

[Graph Sam]

Hello Nick.... happy to respond on this.

In the settings.js I set the following lines.

    https: {
      key: fs.readFileSync(path.join('/root', '/.node-red', '/certs', 'private.pem.key')),
      cert: fs.readFileSync(path.join('/root', '/.node-red', '/certs', 'certificate.pem.crt')),
      ca: fs.readFileSync(path.join('/root', '/.node-red', '/certs', 'root-CA.crt'))
    },

In the node I set the field for the certs to /root/.node-red/certs

but the results give me always the same error about the keypath.

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

20 Mar 00:46:29 - [info] Node-RED version: v0.16.2
20 Mar 00:46:29 - [info] Node.js  version: v6.2.1
20 Mar 00:46:29 - [info] Linux 4.4.41-36.55.amzn1.x86_64 x64 LE
20 Mar 00:46:29 - [info] Loading palette nodes
20 Mar 00:46:30 - [info] Dashboard version 2.3.5 started at /ui
20 Mar 00:46:30 - [warn] ------------------------------------------------------
20 Mar 00:46:30 - [warn] [rpi-gpio] Info : Ignoring Raspberry Pi specific node
20 Mar 00:46:30 - [warn] [mqtt] Error: Cannot find module 'buffer-shims'
20 Mar 00:46:30 - [warn] [feedparse] Error: Cannot find module 'util-deprecate'
20 Mar 00:46:30 - [warn] ------------------------------------------------------
20 Mar 00:46:30 - [info] Settings file  : /root/.node-red/settings.js
20 Mar 00:46:30 - [info] User directory : /root/.node-red
20 Mar 00:46:30 - [info] Flows file     : /root/.node-red/flows_ip-172-31-22-220.json
20 Mar 00:46:30 - [info] Server now running at http://127.0.0.1:1880/
20 Mar 00:46:30 - [info] Starting flows
20 Mar 00:46:30 - [info] [aws-iot-device:MQTT-AWS] Attempt to connect to broker with 00-04-A3-0B-00-1A-06-58 from: /root/.node-red/certs
20 Mar 00:46:30 - [error] [aws-mqtt in:23215990.b98496] Error: Invalid "keyPath" option supplied.
20 Mar 00:46:30 - [info] Started flows

The error in the startup of Node-RED prevents me from accessing the flow editor from the browser. Hence, I am forced to comment out the lines in the settings.js file for the key path to start node-red normally but the error I can get it when the path /root/.node-red/certs is triggered from the flow to give me again the same error.

3/20/2017, 12:47:43 AMnode: 8b125318.5079emsg : error

To unsubscribe from this group and all its topics, send an email to node-red+unsubscribe@googlegroups.com.

To post to this group, send email to node...@googlegroups.com.
Visit this group at https://groups.google.com/group/node-red.

To view this discussion on the web, visit https://groups.google.com/d/msgid/node-red/903f3a24-b502-4e3f-a209-c5720e499977%40googlegroups.com.

For more options, visit https://groups.google.com/d/optout.

--
http://nodered.org
 
Join us on Slack to continue the conversation: http://nodered.org/slack
---

You received this message because you are subscribed to the Google Groups "Node-RED" group.

To unsubscribe from this group and stop receiving emails from it, send an email to node-red+unsubscribe@googlegroups.com.

To post to this group, send email to node...@googlegroups.com.
Visit this group at https://groups.google.com/group/node-red.
To view this discussion on the web, visit https://groups.google.com/d/msgid/node-red/CAD5DeLC6GriAjOD74Hbu-WMj07Gx-0ASxuu1CFE-awBapD6rtA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

--

http://nodered.org
 
Join us on Slack to continue the conversation: http://nodered.org/slack
---
You received this message because you are subscribed to a topic in the Google Groups "Node-RED" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/node-red/RJDesFhFzec/unsubscribe.

To unsubscribe from this group and all its topics, send an email to node-red+unsubscribe@googlegroups.com.

To post to this group, send email to node...@googlegroups.com.
Visit this group at https://groups.google.com/group/node-red.

To view this discussion on the web, visit https://groups.google.com/d/msgid/node-red/CAF%3DvhqdFvsnNc_s-8KUJiNR4iGrafd3d2nxn5SGup-pbJSDfaw%40mail.gmail.com.

[Julian Knight]

2 things. Firstly you don't need the "/" on any of the path elements.

Secondly, you shouldn't be running as root. That throws loads of other things out of whack & opens your machine's security quite badly.

To unsubscribe from this group and all its topics, send an email to node-red+u...@googlegroups.com.

To post to this group, send email to node...@googlegroups.com.
Visit this group at https://groups.google.com/group/node-red.

To view this discussion on the web, visit https://groups.google.com/d/msgid/node-red/903f3a24-b502-4e3f-a209-c5720e499977%40googlegroups.com.

For more options, visit https://groups.google.com/d/optout.

--
http://nodered.org
 
Join us on Slack to continue the conversation: http://nodered.org/slack
---

You received this message because you are subscribed to the Google Groups "Node-RED" group.

To unsubscribe from this group and stop receiving emails from it, send an email to node-red+u...@googlegroups.com.

To post to this group, send email to node...@googlegroups.com.
Visit this group at https://groups.google.com/group/node-red.
To view this discussion on the web, visit https://groups.google.com/d/msgid/node-red/CAD5DeLC6GriAjOD74Hbu-WMj07Gx-0ASxuu1CFE-awBapD6rtA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

--
http://nodered.org
 
Join us on Slack to continue the conversation: http://nodered.org/slack
---
You received this message because you are subscribed to a topic in the Google Groups "Node-RED" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/node-red/RJDesFhFzec/unsubscribe.

To unsubscribe from this group and all its topics, send an email to node-red+u...@googlegroups.com.

To post to this group, send email to node...@googlegroups.com.
Visit this group at https://groups.google.com/group/node-red.

[Nick O'Leary]

Ah, so this error is coming from the aws-mqtt node - you hadn't mentioned that anywhere.

I haven't used it myself so cannot help directly and I don't know why that node is complaining about your configuration.

It's readme does explain a bit about what is expected to exist in that certs directory: http://flows.nodered.org/node/node-red-contrib-aws-iot-hub

I would start by double checking that.

If you continue to have an issue, I suggest you raise an issue on that node's github repo to get the author's help.

Nick

To unsubscribe from this group and stop receiving emails from it, send an email to node-red+unsubscribe@googlegroups.com.

To post to this group, send email to node...@googlegroups.com.
Visit this group at https://groups.google.com/group/node-red.

To view this discussion on the web, visit https://groups.google.com/d/msgid/node-red/0fec5e58-0b95-4ecd-9365-1653e9594b40%40googlegroups.com.

[Graph Sam]

Thanks a lot Nick for your answer.

I have this working on the end-device to access keys from the path suggested by the node library creator but this doesn't work for me on the application server because of the keyPath error message.

I tried to create a javascript file to access the keys and it works without errors so the only problem here is from within Node-RED.

Please if you can get this working in your environment so just let me know.

/Samy

To unsubscribe from this group and all its topics, send an email to node-red+unsubscribe@googlegroups.com.

To post to this group, send email to node...@googlegroups.com.
Visit this group at https://groups.google.com/group/node-red.

To view this discussion on the web, visit https://groups.google.com/d/msgid/node-red/CAF%3Dvhqd%2BwBqvJ6vXtZ%3DFxsBDimvX%2BY%2BfsGD88yE0iuq93-wUrQ%40mail.gmail.com.

[Julian Knight]

I replied to your PM - I'm not sure you have the right settings.

To unsubscribe from this group and stop receiving emails from it, send an email to node-red+u...@googlegroups.com.

To post to this group, send email to node...@googlegroups.com.
Visit this group at https://groups.google.com/group/node-red.

To view this discussion on the web, visit https://groups.google.com/d/msgid/node-red/0fec5e58-0b95-4ecd-9365-1653e9594b40%40googlegroups.com.

For more options, visit https://groups.google.com/d/optout.

--
http://nodered.org
 
Join us on Slack to continue the conversation: http://nodered.org/slack
---
You received this message because you are subscribed to a topic in the Google Groups "Node-RED" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/node-red/RJDesFhFzec/unsubscribe.

To unsubscribe from this group and all its topics, send an email to node-red+u...@googlegroups.com.
To post to this group, send email to node...@googlegroups.com.
Visit this group at https://groups.google.com/group/node-red.

[Graph Sam]

Thanks Julian for your hints!

The keys are signed and I can access them from javascript file without any error message. The problem is that I can't access them from within Node-RED. Do you have any suggestion about any of my configurations?

To unsubscribe from this group and all its topics, send an email to node-red+unsubscribe@googlegroups.com.

To post to this group, send email to node...@googlegroups.com.
Visit this group at https://groups.google.com/group/node-red.

To view this discussion on the web, visit https://groups.google.com/d/msgid/node-red/d87fcdf4-ea1f-4d1f-a3de-624d8faa68f1%40googlegroups.com.

[Nick O'Leary]

Hi,

the problem is something specific to the AWS node. Have you contacted its author?

NIck

To unsubscribe from this group and stop receiving emails from it, send an email to node-red+unsubscribe@googlegroups.com.

To post to this group, send email to node...@googlegroups.com.
Visit this group at https://groups.google.com/group/node-red.

To view this discussion on the web, visit https://groups.google.com/d/msgid/node-red/CAD5DeLCf%3DJ%3DmfsvBSHk6eybqobzO2w5dk9M6u_gNQEMO4LRsjg%40mail.gmail.com.

[Graph Sam]

Yes I have sent him a message to look at it. I will inform you if there's any information.

Thanks

To view this discussion on the web, visit https://groups.google.com/d/msgid/node-red/CAF%3DvhqcV4y23%2BtL%3DbysN0XdwFr3Z4uOt1X6O11FEdrBFb8wwRA%40mail.gmail.com.

[Graph Sam]

Hi Nick,

Which mqtt node version I have to install so that I can get the fields shown in the attached files?

I am asking because I can't find the security/keys fields in the mqtt node, I have downloaded three different mqtt nodes but none of them has the fields to specify the security keys.

node-red-contrib-mqttssl

node-red-contrib-mqtt-env

node-red-contrib-mqtt-dynamic

In addition, Node-RED version 0.16.2 has no mqtt node at all while the mqtt node is included in Node-RED

in previous versions like 0.10.x  

/Samy

[Nick O'Leary]

The MQTT nodes are part of the core install of node-red. If they are missing from your palette that suggests you are using node-red 0.16 with node.js 0.10.

Node.js 0.10 is no longer supported - one of the symptoms of using it is the MQTT nodes no longer work as they depend on a newer version of node.js.

Once you have updated your node.js version, you'll find the MQTT nodes are there, and in their broker configuration you can enable a TLS connection where you provide the cert paths.

Nick

To view this discussion on the web, visit https://groups.google.com/d/msgid/node-red/CAD5DeLABsEpHmodFSknTh159J6XEx-bo5JHUUj2n%2BkiDxu8K8A%40mail.gmail.com.

[Graph Sam]

Do you know on Linux how to specify which node.js version from command line? ... does it work if npm downloads the latest version of node.js?

To view this discussion on the web, visit https://groups.google.com/d/msgid/node-red/CAF%3DvhqdivEQ1eQJ-k_7bchjv4bHJYTDTR1gq-hez%2Bn-3EWB3GA%40mail.gmail.com.

[Graph Sam]

Hi Nick,

It's already installed node.js v6.2.1 and this should work, am I right?

/Samy

[Nick O'Leary]

When Node-RED starts up it logs what version of node.js it is using, along with any errors associated with the nodes it tried to load.

Can you share that start-up log (up to the point where it says 'starting flows')?

Nick

To view this discussion on the web, visit https://groups.google.com/d/msgid/node-red/CAD5DeLA7Y6Ox89_vyf-CE8Dw%3D1SG3NjC5QFK0QZTJjbGMAEa3A%40mail.gmail.com.

[Graph Sam]

Here it's the print at start of Node-RED.

Welcome to Node-RED

===================

21 Mar 09:33:07 - [info] Node-RED version: v0.16.2

21 Mar 09:33:07 - [info] Node.js  version: v6.2.1

21 Mar 09:33:07 - [info] Linux 4.4.41-36.55.amzn1.x86_64 x64 LE

21 Mar 09:33:07 - [info] Loading palette nodes

21 Mar 09:33:07 - [info] Dashboard version 2.3.5 started at /ui

21 Mar 09:33:08 - [warn] ------------------------------------------------------

21 Mar 09:33:08 - [warn] [rpi-gpio] Info : Ignoring Raspberry Pi specific node

21 Mar 09:33:08 - [warn] [mqtt] Error: Cannot find module 'buffer-shims'

21 Mar 09:33:08 - [warn] [feedparse] Error: Cannot find module 'util-deprecate'

21 Mar 09:33:08 - [warn] ------------------------------------------------------

21 Mar 09:33:08 - [info] Settings file  : /root/.node-red/settings.js

21 Mar 09:33:08 - [info] User directory : /root/.node-red

21 Mar 09:33:08 - [info] Flows file     : /root/.node-red/flows_ip-112-11-09-200.json

21 Mar 09:33:08 - [info] Server now running at http://127.0.0.1:1880/

21 Mar 09:33:08 - [info] Starting flows

21 Mar 09:33:08 - [info] [aws-iot-device:MQTT-AWS] Attempt to connect to broker with 00-01-A2-0B-00-A1-02-33 from: /root/.awscerts/

21 Mar 09:33:08 - [error] [aws-mqtt in:23215990.b98496] Error: Invalid "keyPath" option supplied.

To view this discussion on the web, visit https://groups.google.com/d/msgid/node-red/CAF%3DvhqendV%3D5DyKf9Of8_hLtRcp%3D9%2Bz6RxWD%2Boi6NfVciGNF-w%40mail.gmail.com.

[Nick O'Leary]

That suggests to me you've updated the version of node.js you are using after you installed node-red.

How did you install node-red?

Whilst not on topic, also worth saying that you should avoid running as root if you don't need to... but lets tackle one thing at a time.

Nick

To view this discussion on the web, visit https://groups.google.com/d/msgid/node-red/CAD5DeLAaTVWCiHu-c%2B7hGBap5xGtut_JS8pjUGkZAUPy4CMhcw%40mail.gmail.com.

[Graph Sam]

I have followed the instructions on this page.

http://nodered.org/docs/getting-started/installation

To view this discussion on the web, visit https://groups.google.com/d/msgid/node-red/CAF%3DvhqdKkPgYBwcY_nHYeKpBy1s7DOsbH%2B6syNSKd1JWvDBQUg%40mail.gmail.com.

[Nick O'Leary]

So if you rerun the install command:

   sudo npm install -g --unsafe-perm node-red

it will rebuild the binary modules that need to be updated for node 6

Nick

To view this discussion on the web, visit https://groups.google.com/d/msgid/node-red/CAD5DeLBf5NzwJSNT3h9LNCMxOrgQxJk2m8aPuROCfJN1PFurzg%40mail.gmail.com.

[Graph Sam]

Nick,

It doesn't work with sudo since it gives me errors and stops.

npm ERR! Linux 4.4.41-36.55.amzn1.x86_64

npm ERR! argv "node" "/usr/local/bin/npm" "install" "-g" "--unsafe-perm" "node-red"

npm ERR! node v0.6.8

npm ERR! npm  v2.15.11

npm ERR! Object #<Object> has no method 'exists'

npm ERR!

npm ERR! If you need help, you may report this error at:

npm ERR!     <https://github.com/npm/npm/issues>

I tried then the same command without sudo and it worked and now I can find the original mqtt node and used it in the flow.

The sudo problem looks at different place to start npm namely from /usr/local/bin/npm ... I think I have to remove npm from that path. 

ooooh I remember now that I did a node-red installation previously using nvm, I don't know if that installation though it's stopped might be causing problems to me. If you know how to remove that nvm installation just let me know ... the path for that in /root/.nvm/versions/node/v6.2.1/bin/node

Please let me know if I need more configurations to get the environment set correctly.

Thanks a lot for your help!

To view this discussion on the web, visit https://groups.google.com/d/msgid/node-red/CAF%3DvhqfG%2BRF-XtaGLOhg7g1EeY%3DwtXsZsOyzKvZCiYC9TSH2_A%40mail.gmail.com.

[Nick O'Leary]

I suggest you read the nvm docs for how to tidy it up. Our docs don't cover nvm so I can't really help on that specifically.

Glad to hear you've got the mqtt nodes back.

Nick

To view this discussion on the web, visit https://groups.google.com/d/msgid/node-red/CAD5DeLA%3DoZL9zDnhPo7gjtmn%3DVu7i_%2BohLiTXX7DPUPq173KBQ%40mail.gmail.com.

[Dave C-J]

Yes your underlying node installation seems to be 

which is well out of support... so yeah... sort out nvm .

[Graph Sam]

Thanks Dave!

Yes I understand it and I will do clean up the nvm installations.

However, after running the following commands 

npm -v

it displays 4.4.2

and 

node -v

it displays  

v6.2.1

Hence, the stopped installation using nvm works fine unless I use sudo then it would read from nvm.

 

--

http://nodered.org
 
Join us on Slack to continue the conversation: http://nodered.org/slack
---
You received this message because you are subscribed to a topic in the Google Groups "Node-RED" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/node-red/RJDesFhFzec/unsubscribe.
To unsubscribe from this group and all its topics, send an email to node-red+unsubscribe@googlegroups.com.
To post to this group, send email to node...@googlegroups.com.
Visit this group at https://groups.google.com/group/node-red.

To view this discussion on the web, visit https://groups.google.com/d/msgid/node-red/CACXWFwJ1OZELqcVV0EA3oxMrBPCXwUqgiB95QUnJHOVVY193Eg%40mail.gmail.com.

[Graph Sam]

Nick, Julian and Dave,

Thanks a lot for your suggestions!.... Now it works as expected.

I have now Node-RED installed on the end-device and another instance is installed on the application server. They communicate with each other using the native MQTT node. The messages are passed in both directions.

Node-RED version on end-device: v0.10.x

Node-RED version on the application server: v0.16.2