No way to specify url using command line client? #1831

matthewadams · 2024-03-29T07:45:05Z

matthewadams
Mar 29, 2024

My VerneMQ MQTT broker has a path portion of the connection url, which is similar to wss://the.server.name.here/mqtt. I'm trying to test using the command line client, but I don't see a way to specify the full url:

npx [email protected] publish --help
Usage: mqtt publish [opts] topic [message]

Available options:

  -h/--hostname HOST    the broker host
  -p/--port PORT        the broker port
  -i/--client-id ID     the client id
  -q/--qos 0/1/2        the QoS of the message
  -t/--topic TOPIC      the message topic
  -m/--message MSG      the message body
  -r/--retain           send a retained message
  -s/--stdin            read the message body from stdin
  -M/--multiline        read lines from stdin as multiple messages
  -u/--username USER    the username
  -P/--password PASS    the password
  -C/--protocol PROTO   the protocol to use, 'mqtt',
                        'mqtts', 'ws' or 'wss'
  --key PATH            path to the key file
  --cert PATH           path to the cert file
  --ca PATH             path to the ca certificate
  --insecure            do not verify the server certificate
  --will-topic TOPIC    the will topic
  --will-payload BODY   the will message
  --will-qos 0/1/2      the will qos
  --will-retain         send a will retained message
  -H/--help             show this

How do I specify the hostname & path?

matthewadams · 2024-03-29T07:45:48Z

matthewadams
Mar 29, 2024
Author

...same for 4.3.7:

npx [email protected] publish --help
Usage: mqtt publish [opts] topic [message]

Available options:

  -h/--hostname HOST    the broker host
  -p/--port PORT        the broker port
  -i/--client-id ID     the client id
  -q/--qos 0/1/2        the QoS of the message
  -t/--topic TOPIC      the message topic
  -m/--message MSG      the message body
  -r/--retain           send a retained message
  -s/--stdin            read the message body from stdin
  -M/--multiline        read lines from stdin as multiple messages
  -u/--username USER    the username
  -P/--password PASS    the password
  -C/--protocol PROTO   the protocol to use, 'mqtt',
                        'mqtts', 'ws' or 'wss'
  --key PATH            path to the key file
  --cert PATH           path to the cert file
  --ca PATH             path to the ca certificate
  --insecure            do not verify the server certificate
  --will-topic TOPIC    the will topic
  --will-payload BODY   the will message
  --will-qos 0/1/2      the will qos
  --will-retain         send a will retained message
  -H/--help             show this

4 replies

robertsLando Mar 29, 2024
Maintainer

@matthewadams -h the.server.name.here/mqtt ?

matthewadams Mar 29, 2024
Author

No, it treats the string the.server.name.here/mqtt as the entire hostname and fails DNS lookup. Error is

# Note: I've changed the actual hostname with "the.server.name.here" below

$ DEBUG=mqttjs* npx [email protected] publish -C wss -h the.server.name.here/mqtt -p 443 -i matthew_mqttjs_cli -t foo -u admin -P password  -m "hello from mqttjs-cli @ $(date)"

  mqttjs connecting to an MQTT broker... +0ms
  mqttjs:client MqttClient :: options.protocol wss +0ms
  mqttjs:client MqttClient :: options.protocolVersion 4 +0ms
  mqttjs:client MqttClient :: options.username admin +0ms
  mqttjs:client MqttClient :: options.keepalive 60 +0ms
  mqttjs:client MqttClient :: options.reconnectPeriod 1000 +0ms
  mqttjs:client MqttClient :: options.rejectUnauthorized undefined +0ms
  mqttjs:client MqttClient :: options.topicAliasMaximum undefined +0ms
  mqttjs:client MqttClient :: clientId matthew_mqttjs_cli +0ms
  mqttjs:client MqttClient :: setting up stream +0ms
  mqttjs:client _setupStream :: calling method to clear reconnect +1ms
  mqttjs:client _clearReconnect : clearing reconnect timer +0ms
  mqttjs:client _setupStream :: using streamBuilder provided to client to create stream +0ms
  mqttjs calling streambuilder for wss +2ms
  mqttjs:ws streamBuilder +0ms
  mqttjs:ws createWebSocket +0ms
  mqttjs:ws protocol: MQTT 4 +0ms
  mqttjs:ws creating new Websocket for url: wss://the.server.name.here/mqtt:443/ and protocol: mqtt +0ms
  mqttjs:client _setupStream :: pipe stream to writable stream +20ms
  mqttjs:client _setupStream: sending packet `connect` +2ms
  mqttjs:client sendPacket :: packet: { cmd: 'connect' } +0ms
  mqttjs:client sendPacket :: emitting `packetsend` +1ms
  mqttjs:client sendPacket :: writing to stream +0ms
  mqttjs:client sendPacket :: writeToStream result true +9ms
  mqttjs:client streamErrorHandler :: error Unexpected server response: 404 +461ms
  mqttjs:client nop :: Error: Unexpected server response: 404
    at ClientRequest.<anonymous> (/Users/matthewadams/.asdf/installs/nodejs/20.9.0/.npm/lib/node_modules/mqtt/node_modules/ws/lib/websocket.js:783:7)
    at ClientRequest.emit (node:events:514:28)
    at HTTPParser.parserOnIncomingClient [as onIncoming] (node:_http_client:693:27)
    at HTTPParser.parserOnHeadersComplete (node:_http_common:119:17)
    at TLSSocket.socketOnData (node:_http_client:535:22)
    at TLSSocket.emit (node:events:514:28)
    at addChunk (node:internal/streams/readable:376:12)
    at readableAddChunk (node:internal/streams/readable:349:9)
    at Readable.push (node:internal/streams/readable:286:10)
    at TLSWrap.onStreamRead (node:internal/stream_base_commons:190:23) +0ms
  mqttjs:client (matthew_mqttjs_cli)stream :: on close +1ms
  mqttjs:client flushVolatile :: deleting volatile messages from the queue and setting their callbacks as error function +0ms
  mqttjs:client stream: emit close to MqttClient +0ms
  mqttjs:client close :: connected set to `false` +0ms
  mqttjs:client close :: clearing connackTimer +0ms
  mqttjs:client close :: clearing ping timer +0ms
  mqttjs:client close :: calling _setupReconnect +0ms
  mqttjs:client _setupReconnect :: emit `offline` state +0ms
  mqttjs:client _setupReconnect :: set `reconnecting` to `true` +0ms
  mqttjs:client _setupReconnect :: setting reconnectTimer for 1000 ms +0ms
  mqttjs:client reconnectTimer :: reconnect triggered! +1s
  mqttjs:client _reconnect: emitting reconnect to client +1ms
  mqttjs:client _reconnect: calling _setupStream +0ms
  mqttjs:client _setupStream :: calling method to clear reconnect +0ms
  mqttjs:client _clearReconnect : clearing reconnect timer +0ms
  mqttjs:client _setupStream :: using streamBuilder provided to client to create stream +1ms
  mqttjs calling streambuilder for wss +1s
  mqttjs:ws streamBuilder +1s
  mqttjs:ws createWebSocket +0ms
  mqttjs:ws protocol: MQTT 4 +0ms
  mqttjs:ws creating new Websocket for url: wss://the.server.name.here/mqtt:443/ and protocol: mqtt +0ms
  mqttjs:client _setupStream :: pipe stream to writable stream +4ms
  mqttjs:client _setupStream: sending packet `connect` +0ms
  mqttjs:client sendPacket :: packet: { cmd: 'connect' } +0ms
  mqttjs:client sendPacket :: emitting `packetsend` +0ms
  mqttjs:client sendPacket :: writing to stream +0ms
  mqttjs:client sendPacket :: writeToStream result true +0ms
  mqttjs:client streamErrorHandler :: error Unexpected server response: 404 +351ms
  mqttjs:client nop :: Error: Unexpected server response: 404
    at ClientRequest.<anonymous> (/Users/matthewadams/.asdf/installs/nodejs/20.9.0/.npm/lib/node_modules/mqtt/node_modules/ws/lib/websocket.js:783:7)
    at ClientRequest.emit (node:events:514:28)
    at HTTPParser.parserOnIncomingClient [as onIncoming] (node:_http_client:693:27)
    at HTTPParser.parserOnHeadersComplete (node:_http_common:119:17)
    at TLSSocket.socketOnData (node:_http_client:535:22)
    at TLSSocket.emit (node:events:514:28)
    at addChunk (node:internal/streams/readable:376:12)
    at readableAddChunk (node:internal/streams/readable:349:9)
    at Readable.push (node:internal/streams/readable:286:10)
    at TLSWrap.onStreamRead (node:internal/stream_base_commons:190:23) +1ms
  mqttjs:client (matthew_mqttjs_cli)stream :: on close +0ms
  mqttjs:client flushVolatile :: deleting volatile messages from the queue and setting their callbacks as error function +0ms
  mqttjs:client stream: emit close to MqttClient +0ms
  mqttjs:client close :: connected set to `false` +0ms
  mqttjs:client close :: clearing connackTimer +0ms
  mqttjs:client close :: clearing ping timer +0ms
  mqttjs:client close :: calling _setupReconnect +0ms
  mqttjs:client _setupReconnect :: setting reconnectTimer for 1000 ms +1ms
  mqttjs:client reconnectTimer :: reconnect triggered! +1s
  mqttjs:client _reconnect: emitting reconnect to cli

Notice the line:

mqttjs:ws creating new Websocket for url: wss://the.server.name.here/mqtt:443/ and protocol: mqtt +0ms

The port follows /mqtt. The strange thing is that the error is reported as a 404, when it should really be a DNS failure.

robertsLando Apr 2, 2024
Maintainer

Want to submit a PR? The cli bin are not a priority for me right now as there are many alternatives like mosquitto pub for example

matthewadams Apr 2, 2024
Author

I will if I find the time.

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

No way to specify url using command line client? #1831

{{title}}

Replies: 1 comment 4 replies

{{title}}

{{title}}

{{editor}}'s edit

{{editor}}'s edit

{{title}}

{{title}}

{{title}}

Select a reply

No way to specify url using command line client? #1831

matthewadams Mar 29, 2024

Replies: 1 comment · 4 replies

matthewadams Mar 29, 2024 Author

robertsLando Mar 29, 2024 Maintainer

matthewadams Mar 29, 2024 Author

robertsLando Apr 2, 2024 Maintainer

matthewadams Apr 2, 2024 Author

matthewadams
Mar 29, 2024

Replies: 1 comment 4 replies

matthewadams
Mar 29, 2024
Author

robertsLando Mar 29, 2024
Maintainer

matthewadams Mar 29, 2024
Author

robertsLando Apr 2, 2024
Maintainer

matthewadams Apr 2, 2024
Author