FORUM CTRLX AUTOMATION
ctrlX World Partner Apps for ctrlX AUTOMATION
02-07-2023 01:30 PM
Hello,
I'm trying to install node-red-node-email in the Node-Red for ctrlX.
But there is always an error. The protocol is down below.
I also tried to run the px.exe, set up the firewall entrance rules and restart the ctrlX. But the error still scours.
Attached the screenshots of the Settings.
The browser is running on a vMware and connected in a local network with the ctrlX. The vMWare have also a connection to the internet.
Node Red protocol:
-----------------------------------------------------------
2023-02-07T12:04:35.163Z Installieren : node-red-node-email 1.18.4
2023-02-07T13:04:07.002Z npm install --no-audit --no-update-notifier --no-fund --save --save-prefix=~ --production --engine-strict node-red-node-email@1.18.4
2023-02-07T13:05:21.516Z [err] npm
2023-02-07T13:05:21.518Z [err]
2023-02-07T13:05:21.519Z [err] ERR!
2023-02-07T13:05:21.519Z [err]
2023-02-07T13:05:21.520Z [err] code
2023-02-07T13:05:21.520Z [err] ECONNREFUSED
2023-02-07T13:05:21.522Z [err] npm
2023-02-07T13:05:21.522Z [err]
2023-02-07T13:05:21.523Z [err] ERR!
2023-02-07T13:05:21.523Z [err]
2023-02-07T13:05:21.523Z [err] errno
2023-02-07T13:05:21.524Z [err] ECONNREFUSED
2023-02-07T13:05:21.582Z [err] npm ERR!
2023-02-07T13:05:21.582Z [err] FetchError: request to https://registry.npmjs.org/node-red-node-email failed, reason: connect ECONNREFUSED 192.168.100.80:3128
2023-02-07T13:05:21.582Z [err] npm ERR! at ClientRequest.<anonymous> (/snap/ctrlx-node-red/327/lib/node_modules/npm/node_modules/node-fetch-npm/src/index.js:68:14)
2023-02-07T13:05:21.582Z [err] npm ERR! at ClientRequest.emit (events.js:400:28)
2023-02-07T13:05:21.582Z [err] npm ERR! at onerror (/snap/ctrlx-node-red/327/lib/node_modules/npm/node_modules/agent-base/index.js:101:9)
2023-02-07T13:05:21.582Z [err] npm
2023-02-07T13:05:21.583Z [err] ERR! at callbackError (/snap/ctrlx-node-red/327/lib/node_modules/npm/node_modules/agent-base/index.js:123:5)
2023-02-07T13:05:21.583Z [err] npm ERR! at processTicksAndRejections (internal/process/task_queues.js:95:5)
2023-02-07T13:05:21.583Z [err] npm
2023-02-07T13:05:21.583Z [err] ERR! FetchError: request to https://registry.npmjs.org/node-red-node-email failed, reason: connect ECONNREFUSED 192.168.100.80:3128
2023-02-07T13:05:21.583Z [err] npm ERR!
2023-02-07T13:05:21.583Z [err] at ClientRequest.<anonymous> (/snap/ctrlx-node-red/327/lib/node_modules/npm/node_modules/node-fetch-npm/src/index.js:68:14)
2023-02-07T13:05:21.583Z [err] npm ERR!
2023-02-07T13:05:21.583Z [err] at ClientRequest.emit (events.js:400:28)
2023-02-07T13:05:21.583Z [err] npm ERR! at onerror (/snap/ctrlx-node-red/327/lib/node_modules/npm/node_modules/agent-base/index.js:101:9)
2023-02-07T13:05:21.584Z [err] npm ERR!
2023-02-07T13:05:21.584Z [err] at callbackError (/snap/ctrlx-node-red/327/lib/node_modules/npm/node_modules/agent-base/index.js:123:5)
2023-02-07T13:05:21.584Z [err] npm ERR! at processTicksAndRejections (internal/process/task_queues.js:95:5) {
2023-02-07T13:05:21.584Z [err] npm ERR!
2023-02-07T13:05:21.584Z [err] type: 'system',
2023-02-07T13:05:21.584Z [err] npm ERR! errno: 'ECONNREFUSED',
2023-02-07T13:05:21.584Z [err] npm ERR! code: 'ECONNREFUSED'
2023-02-07T13:05:21.585Z [err] npm ERR!
2023-02-07T13:05:21.585Z [err] }
2023-02-07T13:05:21.585Z [err] npm
2023-02-07T13:05:21.585Z [err] ERR!
2023-02-07T13:05:21.585Z [err] npm
2023-02-07T13:05:21.585Z [err] ERR! If you are behind a proxy, please make sure that the
2023-02-07T13:05:21.585Z [err] npm ERR!
2023-02-07T13:05:21.586Z [err] 'proxy' config is set properly. See: 'npm help config'
2023-02-07T13:05:21.605Z [err]
2023-02-07T13:05:21.606Z [err] npm ERR! A complete log of this run can be found in:
2023-02-07T13:05:21.606Z [err] npm ERR! /root/snap/ctrlx-node-red/327/.npm/_logs/2023-02-07T13_05_21_589Z-debug.log
2023-02-07T13:05:21.640Z rc=1
Solved! Go to Solution.
02-08-2023 10:23 AM - edited 02-08-2023 01:25 PM
There are always three steps to check to install pallets on Node-RED:
[{"id":"10a5a811c614f55e","type":"http request","z":"c380b51e3414b962","name":"","method":"GET","ret":"txt","paytoqs":"ignore","url":"http://time.jsontest.com","tls":"","persist":false,"proxy":"","insecureHTTPParser":false,"authType":"","senderr":false,"headers":[],"x":410,"y":180,"wires":[["0ed778586c17659e"]]},{"id":"fd31f8c17afc3fc3","type":"inject","z":"c380b51e3414b962","name":"","props":[{"p":"payload"},{"p":"topic","vt":"str"}],"repeat":"","crontab":"","once":false,"onceDelay":0.1,"topic":"","payload":"","payloadType":"date","x":240,"y":180,"wires":[["10a5a811c614f55e"]]},{"id":"0ed778586c17659e","type":"debug","z":"c380b51e3414b962","name":"debug 2","active":true,"tosidebar":true,"console":false,"tostatus":false,"complete":"true","targetType":"full","statusVal":"","statusType":"auto","x":580,"y":180,"wires":[]}]
I tested your use case and extended the how tos for connecting the ctrlX CORE(virtual) to the internet via proxy on a PC.
02-08-2023 01:18 PM
The vMware has internet. The browser can reach any website also the "http://time.jsontest.com".
It was not possible for me to paste your code in NodeRed.
I tried to rebuild the code in this way:
[
{
"id": "8bb1e01ca545be55",
"type": "tab",
"label": "Flow 1",
"disabled": false,
"info": "",
"env": []
},
{
"id": "5b540730dbbf58f6",
"type": "inject",
"z": "8bb1e01ca545be55",
"name": "",
"props": [
{
"p": "payload"
},
{
"p": "topic",
"vt": "str"
}
],
"repeat": "",
"crontab": "",
"once": false,
"onceDelay": 0.1,
"topic": "",
"payloadType": "date",
"x": 180,
"y": 200,
"wires": [
[
"dccd0e4f6e9a1556"
]
]
},
{
"id": "1d23585a8cfa4c47",
"type": "debug",
"z": "8bb1e01ca545be55",
"name": "debug2",
"active": true,
"tosidebar": true,
"console": false,
"tostatus": false,
"complete": "payload",
"targetType": "msg",
"statusVal": "",
"statusType": "auto",
"x": 560,
"y": 200,
"wires": []
},
{
"id": "dccd0e4f6e9a1556",
"type": "http request",
"z": "8bb1e01ca545be55",
"name": "",
"method": "GET",
"ret": "txt",
"paytoqs": "ignore",
"url": "http://time.jsontest.com",
"tls": "",
"persist": false,
"proxy": "",
"authType": "",
"senderr": false,
"credentials": {},
"x": 370,
"y": 200,
"wires": [
[
"1d23585a8cfa4c47"
]
]
}
]
But the request throws an error.
RequestError: connect ECONNREFUSED 192.168.100.80:3128 : https://time.jsontest.co
02-08-2023 01:30 PM
Changed the data type of my code to JSON, so at my side importing is working fine now.
Did you check the how to that I mentioned above?
Did you set up your proxy properly to listen to your request IP?
Is the proxy running in your virtual operating system?
02-10-2023 08:33 AM
The constellation that the computer is connected to the ctrlX in the local network and has Internet access via W-Lan, it did not work. The ctrlX could not get a connection to the Internet. I tried it with a connection via the company network but also via the free network. The possibility of getting the ctrlX on the Internet with the host computer and not with the virtual machine did not work either.
In my case the only solution was to connect the ctrlX directly to a router and give the router free internet access. So I was able to install the required node in NodeRed.
02-10-2023 09:16 AM - edited 02-10-2023 09:19 AM
For me the question about the used proxy settings is still open but if you like we also could have a look together to the topic and check why the how tos did not work for you. Please send me a private message with your contact data if you want to do so.
04-14-2023 10:51 AM
Hi,
my colleague and I have had some trouble getting pallettes installed ourselves, especially because of network issues / rules that would prohibite our core from communicating outwards.
We have found a work-around, where we download a .tgz file and upload it manually in the pallette manager.
The manual can be found here:
https://forums.opto22.com/t/install-older-version-specific-version-of-a-node-red-node/3796/4
Combine the URL as shown in the example, and it will directly download the .tgz file.