2.0.1 error (networking?)

Are you using the speedtest node?

Can you try disabling it (under the manage pallet option and restart) and then retest please

2 Likes

Yes, that worked! Well done. I'll remove that node completely.

Thanks for your help. I also had to remove the speedtest node too.
But now, I don't know if because of that, when I try to edit the http request node, some texts are missing.
node-red@2.0.1

Copy the image to your clipboard and the simply paste it in
e.g

image

Let's see if it worked...
Thanks!

You need to copy the image itself to your clipboard- e.g do a screengrab

Or use the upload button (I've not tried it myself but it should work)
image

The copy/paste method worked BUT on Firefox (I don't know why I keep using the Brave Browser) :frowning:


Another picture. This time uploaded using the 'upload' toolbar.
It shows that text is missing the dropdown too.

Same issues here with the http request node after upgrading to 2.0.1 (Docker). However, I do not have any Speedtest node installed...

How can I help to trace this? :slight_smile:

I did the command suggested as above and got this:

NR

Can you run the same command in /data to check the extra nodes you have installed?

We have a fix prepared for 2.0.2 that will undo the damage done by the old version of agent-base - at the possible cost of breaking the nodes that use the old version. On balance, that's a preferable way to approach it so we can more easily identify affected nodes and help get them updated.

1 Like

Good news on my side!
After watching your video from today I installed everything again with "bash <(curl -sL https://raw.githubusercontent.com/node-red/linux-installers/master/deb/update-nodejs-and-nodered)" but this time including the nodejs 14 option.
Now the http request node works like a charm (texts are back, as they should)
Thanks a lot for your hard work!!!

Here you go:

Same problem here with multiple HTTP request nodes in use. I don't have speedtest installed.
RequestError: connect ECONNREFUSED 127.0.0.1:443

Looks like a DNS problem? Hostnames resolve to 127.0.0.1

Follow the instructions here, and then report back the results. Then, probably disable that node type.

node-red-docker@2.0.1 /usr/src/node-red
-- node-red@2.0.1 -- @node-red/nodes@2.0.1
-- https-proxy-agent@5.0.0 -- agent-base@6.0.2

Is this correct?

and also run it in /data directory.

bash-5.0$ pwd
/data
bash-5.0$ npm list agent-base
node-red-project@0.0.1 /data
`-- node-red-contrib-chatbot@0.19.7
  +-- chat-platform@1.2.2
  | `-- npm@6.14.8
  |   `-- npm-registry-fetch@4.0.7
  |     `-- make-fetch-happen@5.0.2
  |       +-- http-proxy-agent@2.1.0
  |       | `-- agent-base@4.3.0
  |       +-- https-proxy-agent@2.2.4
  |       | `-- agent-base@4.3.0  deduped
  |       `-- socks-proxy-agent@4.0.2
  |         `-- agent-base@4.2.1
  +-- dialogflow@0.7.0
  | `-- google-gax@0.20.0
  |   `-- google-auth-library@2.0.2
  |     `-- https-proxy-agent@2.2.4
  |       `-- agent-base@4.3.0  deduped
  +-- node-nlp@4.13.3
  | `-- @nlpjs/request@4.13.2
  |   +-- http-proxy-agent@4.0.1
  |   | `-- agent-base@6.0.1
  |   `-- https-proxy-agent@5.0.0
  |     `-- agent-base@6.0.1
  `-- recastai@3.7.0
    `-- superagent-proxy@1.0.3
      `-- proxy-agent@2.3.1
        +-- agent-base@4.3.0
        +-- http-proxy-agent@2.1.0
        | `-- agent-base@4.3.0  deduped
        +-- pac-proxy-agent@2.0.2
        | +-- agent-base@4.3.0  deduped
        | `-- http-proxy-agent@2.1.0
        |   `-- agent-base@4.3.0  deduped
        `-- socks-proxy-agent@3.0.1
          `-- agent-base@4.3.0  deduped