XMPP node issue (follow #1135)

[ioukos]

Which node are you reporting and issue on?

node-red-node-xmpp 0.7.0

What are the steps to reproduce?

node-red-node-xmpp 0.7.0

and

nodered/node-red:latest (Docker)

Broken after a general update.

But XMPP server is still running, as I'm still using it with other devices. XMPP server doesn't run on same server.

What happens?

at connexion XMPP has errors and is not able to connect to server and of course is not able to send messages 👍

log export :

 Jul 11:25:35 - [info] [mqtt-broker:593c6bafe4935895] Connected to broker: mqtt://mqtt:1883
7 Jul 11:25:36 - [error] [xmpp out:toto xxxx] Unknown error: AggregateError
7 Jul 11:25:36 - [error] [xmpp out:toto xxxx] Bad xmpp configuration; service: xmpp://xxxx.ovh:5222 jid: toto@xxxx.ovh
7 Jul 11:25:36 - [warn] [xmpp out:toto xxxx] AggregateError
7 Jul 11:25:36 - [warn] [xmpp out:toto xxxx] AggregateError [ETIMEDOUT]:
    at internalConnectMultiple (node:net:1193:18)
    at internalConnectMultiple (node:net:1269:5)
    at Timeout.internalConnectMultipleTimeout (node:net:1810:5)
    at listOnTimeout (node:internal/timers:607:11)
    at process.processTimers (node:internal/timers:541:7)

What did you expect to happen?

at connexion XMPP has no errors and is able to connect to XMPP server and of course is able to send messages

Example flow

 {
        "id": "MYYYYYYYYYYIDDDDDDD",
        "type": "xmpp-server",
        "server": "xxxx.ovh",
        "port": 5222,
        "user": "toto",
        "nickname": "",
        "resource": ""
    },

Environment

• Node-RED version: v5.0.0
• Node.js version: v24.16.0
• npm version: 11.16.0
• Platform/OS: Debian 6.1.128-1
• Browser: Firefox and Edge

Thank you

[hardillb]

This is a generic error about a timeout and we have lost the actual stack trace, it will probably need a little bit of surgery to unpick..

Please edit the following into the 92-xmpp.js file (probably in /data/node_modules/node-red-node-xmpp in the container

At line 340 insert the following

        if (err instanceof AggregateError) {
             for (const e of error.errors) {
                  console.log(e)
             }
        }

You will then need to stop and restart the container (do not delete the running container as this will undo the file changes (unless you have a volume mounted on /data)

[ioukos]

This is the new output :

9 Jul 14:28:00 - [error] [xmpp out:toto xxxx] Unknown error: AggregateError
[red] Uncaught Exception:
9 Jul 14:28:00 - [error] ReferenceError: error is not defined
    at errorHandler (/data/node_modules/node-red-node-xmpp/92-xmpp.js:342:38)
    at Client.<anonymous> (/data/node_modules/node-red-node-xmpp/92-xmpp.js:718:13)
    at Client.emit (node:events:509:28)
    at Socket.error (file:///data/node_modules/node-red-node-xmpp/node_modules/@xmpp/connection/index.js:79:30)
    at Socket.emit (node:events:521:24)
    at emitErrorNT (node:internal/streams/destroy:170:8)
    at emitErrorCloseNT (node:internal/streams/destroy:129:3)
    at process.processTicksAndRejections (node:internal/process/task_queues:90:21)

I hope I will help you !

[hardillb]

Sorry, typo in the suggestion

the start of the for loop should be

     for (const e of err.errors) {

[ioukos]

Sorry ,I'm not of any help :

here is the output :

9 Jul 14:49:12 - [error] [xmpp out:Nono Pouet] Unknown error: AggregateError
[red] Uncaught Exception:
9 Jul 14:49:12 - [error] ReferenceError: error is not defined
    at errorHandler (/data/node_modules/node-red-node-xmpp/92-xmpp.js:342:38)
    at Client.<anonymous> (/data/node_modules/node-red-node-xmpp/92-xmpp.js:718:13)
    at Client.emit (node:events:509:28)
    at Socket.error (file:///data/node_modules/node-red-node-xmpp/node_modules/@xmpp/connection/index.js:79:30)
    at Socket.emit (node:events:521:24)
    at emitErrorNT (node:internal/streams/destroy:170:8)
    at emitErrorCloseNT (node:internal/streams/destroy:129:3)
    at process.processTicksAndRejections (node:internal/process/task_queues:90:21)
9 Jul 14:50:02 - [info]

[hardillb]

Hi, that's the same output as before, please show me the changes you have made to the file so I can help correct it.

[ioukos]

Here is the file :

[ioukos]

Other output :

9 Jul 15:32:11 - [error] [xmpp out:toto xxxx] Unknown error: AggregateError
Error: connect ETIMEDOUT IP.IP.IP.IP:5222
    at createConnectionError (node:net:1746:14)
    at Timeout.internalConnectMultipleTimeout (node:net:1805:38)
    at listOnTimeout (node:internal/timers:607:11)
    at process.processTimers (node:internal/timers:541:7) {
  errno: -110,
  code: 'ETIMEDOUT',
  syscall: 'connect',
  address: ' IP.IP.IP.IP',
  port: 5222
}
Error: connect ENETUNREACH IPPPPPPPPPVVVVV6:5222 - Local (:::0)
    at internalConnectMultiple (node:net:1265:16)
    at Timeout.internalConnectMultipleTimeout (node:net:1810:5)
    at listOnTimeout (node:internal/timers:607:11)
    at process.processTimers (node:internal/timers:541:7) {
  errno: -101,
  code: 'ENETUNREACH',
  syscall: 'connect',
  address: ' IPPPPPPPPPVVVVV6',
  port: 5222
}
9 Jul 15:32:11 - [error] [xmpp out:toto xxxx] Bad xmpp configuration; service: xmpp://xxxx.ovh:5222 jid: toto@xxxx.ovh
9 Jul 15:32:11 - [warn] [xmpp out:toto xxxx] AggregateError
9 Jul 15:32:11 - [warn] [xmpp out:toto xxxx] AggregateError [ETIMEDOUT]:
    at internalConnectMultiple (node:net:1193:18)
    at internalConnectMultiple (node:net:1269:5)
    at Timeout.internalConnectMultipleTimeout (node:net:1810:5)
    at listOnTimeout (node:internal/timers:607:11)
    at process.processTimers (node:internal/timers:541:7)

[hardillb]

OK, This is a network problem.

The server is resolving to both IPv4 and IPv6 addresses and the IPv6 address is not reachable, this implies that your docker setup either doesn't have IPv6 configured or isn't routing IPv6 properly.

The IPv4 is timing out, but I have a recollection of the IPv4 being triggered early by the IPv6 failure for some reason from a HTTP issue recently.

Can you run ip a in a shell in the running container?

Node-RED should be setup to pick IPv4 first iirc (it was in NR 4.x, need to check if that got removed as part of the 5.0 release, EDIT: it is still there)

[hardillb]

To be clear I think this is a change in behaviour in the underlying NodeJS version

[hardillb]

Try adding -e NODE_OPTIONS=--no-network-family-autoselection to the docker run command line

[ioukos]

is this the way on Docker Compose ?

  node-red:
    image: nodered/node-red:latest
    environment:
      - NODE_OPTIONS=--no-network-family-autoselection

If yes, I always have the error on node.

I believe you when you say it's a network issue, but I still have this error :
"Bad xmpp configuration; service: xmpp://xxxx.ovh:5222 jid: toto@xxxx.ovh"
Which doesn't seems to be related to network.

[hardillb]

Do you still get the stack traces or just that line?

[ioukos]

Sorry I still have the stack with ETIMEDOUT related to IP V4.
Then ENETUNREACH related to IPV6.
Finally, [error] [xmpp out:toto xxxx] Bad xmpp configuration; service: xmpp://xxxx.ovh:5222 jid: toto@xxxx.ovh

[hardillb]

OK, this is looking very similar to node-red/node-red#4968 (comment)

Can you run the ip a command in the container to confirm there is no IPv6 configured?

[ioukos]

here is the output :

user@host:~/DockerAutomation# docker exec -it 8x9xbx1xax8x sh
~ $ ip a
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host
       valid_lft forever preferred_lft forever
2: eth0@if259: <BROADCAST,MULTICAST,UP,LOWER_UP,M-DOWN> mtu 1500 qdisc noqueue state UP
    link/ether 3x:ax:5x:0x:2x:dx brd ff:ff:ff:ff:ff:ff
    inet 172.xx.xx.xx/16 brd 172.x.x.x scope global eth0
       valid_lft forever preferred_lft forever

• I tried to disable IPV6 on Docker HOST (not container) : ❌
• I tried to ping IPV4 from container : ✔️
• I tried to ping domain (xxxx.ovh) from container : ✔️ it pickes IPV4