Replies: 5 comments
-
Hey! The |
Beta Was this translation helpful? Give feedback.
-
Thanks, @jszwedko. Is that just for self-signed certificates? I tried connecting to an MQTT server (Emitter) that's using a Let's Encrypt certificate and couldn't connect whereas MQTTX connected fine. |
Beta Was this translation helpful? Give feedback.
-
Some troubleshooting info:
Emitter host was able to successfully retrieve and install a Let's Encrypt cert for the host domain:
MQTTX can connect, subscribe, and publish: But Vector can't connect:
One guess is since Emitter requires MQTT version 3.1.1 and Vector supports MQTT version 5.0 perhaps that's the issue? Is there a way to tell Vector's sink to use MQTT version 3.1.1? |
Beta Was this translation helpful? Give feedback.
-
Using the https://www.emqx.com/en/blog/how-to-use-mqtt-in-rust guide, I created a simple rumqtt program and tried to connect to the Emitter host and got this error message, in case it helps:
|
Beta Was this translation helpful? Give feedback.
-
Using MQTT CLI, I was able to identify the key conditions where my MQTT broker (Emitter) works and doesn't work:
As inferred by my MTTQX experience, Emitter only works with protocol 3.x, not 5.x. In addition, the client must be made aware of the local system certificate store is required. Since I'm not sure how to force Vector to use MQTT protocol 3.x I can't troubleshoot the certificate store so I'll just close this for now. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Does the Vector MQTT sink support MQTTS (MQTT over TLS)?
I see https://github.com/vectordotdev/vector/blob/master/src/sinks/websocket/sink.rs#L463 exists for
wss
but I don't see an equivalent on https://github.com/vectordotdev/vector/blob/master/src/sinks/mqtt/sink.rsBeta Was this translation helpful? Give feedback.
All reactions