node-red / node-red/node-red-nodes

XMPP node issue (follow #1135)

Open
#1,141 15 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
JavaScript
Stars
1.1k
Forks
612
Avg merge
13h 57m
Merged PRs (30d)
3

Description

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

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the node-red-node-xmpp 0.7.0 connection path using the supplied example flow and the AggregateError/ETIMEDOUT log, then compare behavior across the listed Node-RED, Node.js, npm, and Debian versions. Done means the node connects to the remote XMPP server on port 5222 without errors and can send messages.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript, node.js
Domain
backend, networking
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.