RequestError: connect ECONNREFUSED 127.0.0.1:443

General
1

Hello, for the last few days I have been observing such an error on a node that had previously worked normally for a long time.

msg : error
"RequestError: connect ECONNREFUSED 127.0.0.1:443"

Honestly, I am not very strong in Node-red and therefore searches on the Internet did not yield results (I did not quite understand who helped what).
Therefore, I am asking you for help, tell me what to do to eliminate this problem?

p.s.
I checked access to the page both from the network and from home assistant, via ping and via a browser, there is

2024-10-21_17-07-21
2024-10-21_17-07-21507×182 10.4 KB

[{"id":"ab8aa6c5edcb0e0f","type":"inject","z":"2fd58f64dac0768b","name":"каждый 15 минут","props":[{"p":"payload"}],"repeat":"900","crontab":"","once":true,"onceDelay":"5","topic":"","payload":"","payloadType":"date","x":130,"y":60,"wires":[["160a2d3569966107"]]},{"id":"160a2d3569966107","type":"delay","z":"2fd58f64dac0768b","name":"Случайная задержка","pauseType":"random","timeout":"30","timeoutUnits":"seconds","rate":"1","nbRateUnits":"1","rateUnits":"second","randomFirst":"1","randomLast":"5","randomUnits":"seconds","drop":false,"allowrate":false,"outputs":1,"x":360,"y":60,"wires":[["d1e582519e69ec33"]]},{"id":"d1e582519e69ec33","type":"http request","z":"2fd58f64dac0768b","name":"Запрос осадков сейчас","method":"GET","ret":"txt","paytoqs":"ignore","url":"https://www.msn.com/ru-ru/weather/life/in-Ташкент,Узбекистан","tls":"","persist":false,"proxy":"","insecureHTTPParser":false,"authType":"","senderr":false,"headers":[{"keyType":"other","keyValue":"user-agent","valueType":"other","valueValue":"Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/103.0.0.0 Safari/537.36"}],"x":150,"y":160,"wires":[["0304baa9c6c67bb5"]]},{"id":"0304baa9c6c67bb5","type":"debug","z":"2fd58f64dac0768b","name":"debug 4","active":true,"tosidebar":true,"console":false,"tostatus":false,"complete":"false","statusVal":"","statusType":"auto","x":400,"y":160,"wires":[]}]
2

It works for me.
Does it fail continuously or only intermittently? It is difficult to see how that node could be trying to connect to 127.0.0.1 unless you have a DNS problem of some sort.

3

Also please show a screenshot of the debug pane showing the error (and the node id line above the error) and debug output.

4

constantly
I don't think there is a problem with DNS, because the site opens from the browser and ping resolves the name
and everything worked three days ago, I didn't even do an update, today I only updated node-red and that was because I read such a recommendation somewhere, but the update didn't help either

5

And the screenshot?

6

This?

2024-10-21_20-26-46
2024-10-21_20-26-461119×413 27.5 KB

7 
 ping www.msn.com
PING a-0003.a-msedge.net (204.79.197.203) 56(84) bytes of data.
64 bytes from a-0003.a-msedge.net (204.79.197.203): icmp_seq=1 ttl=106 time=101 ms
64 bytes from a-0003.a-msedge.net (204.79.197.203): icmp_seq=2 ttl=106 time=101 ms
64 bytes from a-0003.a-msedge.net (204.79.197.203): icmp_seq=3 ttl=106 time=101 ms
64 bytes from a-0003.a-msedge.net (204.79.197.203): icmp_seq=4 ttl=106 time=101 ms
64 bytes from a-0003.a-msedge.net (204.79.197.203): icmp_seq=5 ttl=106 time=101 ms


docker exec -it 97ac7203d885 ping www.msn.com
PING www.msn.com (204.79.197.203): 56 data bytes
64 bytes from 204.79.197.203: seq=0 ttl=106 time=101.542 ms
64 bytes from 204.79.197.203: seq=1 ttl=106 time=100.826 ms
64 bytes from 204.79.197.203: seq=2 ttl=106 time=101.196 ms
64 bytes from 204.79.197.203: seq=3 ttl=106 time=100.739 ms
8

Weird. What does this command give, using docker exec?
wget https://www.msn.com/ru-ru/weather/life/in-Ташкент,Узбекистан
Post the full command window output please.

9

This is what the chatgpt advised me to check :grinning:

10 
 wget https://www.msn.com/ru-ru/weather/life/in-Ташкент,Узбекистан
--2024-10-21 21:46:51--  https://www.msn.com/ru-ru/weather/life/in-%D0%A2%D0%B0%D1%88%D0%BA%D0%B5%D0%BD%D1%82,%D0%A3%D0%B7%D0%B1%D0%B5%D0%BA%D0%B8%D1%81%D1%82%D0%B0%D0%BD
Resolving www.msn.com (www.msn.com)... 204.79.197.203
Connecting to www.msn.com (www.msn.com)|204.79.197.203|:443... connected.
HTTP request sent, awaiting response... 301 Moved Permanently
Location: https://www.msn.com/ru-xl/weather/life/in-%D0%A2%D0%B0%D1%88%D0%BA%D0%B5%D0%BD%D1%82,%D0%A3%D0%B7%D0%B1%D0%B5%D0%BA%D0%B8%D1%81%D1%82%D0%B0%D0%BD [following]
--2024-10-21 21:46:51--  https://www.msn.com/ru-xl/weather/life/in-%D0%A2%D0%B0%D1%88%D0%BA%D0%B5%D0%BD%D1%82,%D0%A3%D0%B7%D0%B1%D0%B5%D0%BA%D0%B8%D1%81%D1%82%D0%B0%D0%BD
Reusing existing connection to www.msn.com:443.
HTTP request sent, awaiting response... 200 OK
Length: 452131 (442K) [text/html]
Saving to: ‘in-Ташкент,Узбекистан’

in-Ташкент,Узбекистан                     100%[=====================================================================================>] 441.53K   450KB/s    in 1.0s

2024-10-21 21:46:53 (450 KB/s) - ‘in-Ташкент,Узбекистан’ saved [452131/452131]
11

Is that using docker?

12

I think so, I installed it from the official website according to the instructions, but it was a long time ago, but I think it was in docker

13

I don't understand. You posted the ping using docker exec so I assumed you are using docker for node red. If so then you need to use that for the get command.

14

are you talking about this?

wget https://www.msn.com/ru-ru/weather/life/in-Ташкент,Узбекистан

or in the node-red itself?

15

The important question is whether node red is running under docker.

16

If I understand and remember correctly, then no, because I installed it as an add-on from the home assistant interface

and chatgpt offered me this command for testing as one of the options

17

In that case I believe it is running in a docker container, and also it is not the standard node red but is a variant released by HA. My best guess is that it is a HA or Docker issue. You had better ask on an HA forum.