EMQX v5.4.1 - Connector configuration (bridge egress): missing config. options? about emqx HOT 10 OPEN

@alexdelprete
Hi, Sorry for confusing you, I believe the document is outdated. In the new mechanism, the connector only acts as a connection, you need to configure the path in the rules. With this new mechanism, different rules can share the same connector.

from emqx.

Hi @lafirest,

I read about the new approach, but right now I have no rules, I only configured the "new" connector by duplicating an "old" bridge configuration:

The problem is that both in new connector and old bridge configuration, I am not able to configure WS/WSS, because the scheme and the path is missing. Furthermore, if you choose TLS you're forced to upload the CA certificate but that shouldn't be the case when the remote broker uses a working SSL cerrtificate. MQTTX works beautifully and the configuration is very straightforward. It has the scheme and the path fields to configure WS/WSS and it doesn't force you to upload the CA cert to connect to broker.emqx.io.

Thanks a lot for your support. :)

from emqx.

@alexdelprete
Sorry, I seem to have misread your feedback, please let me correct my comment, now the MQTT connector does not support WS ingress, this could be an enhancement.

from emqx.

Sorry, I seem to have misread your feedback, please let me correct my comment, now the MQTT connector does not support WS ingress, this could be an enhancement.

I'm using egress. It doesn't support it? I need to bridge my local EMQX to the public one.

from emqx.

Sorry, I seem to have misread your feedback, please let me correct my comment, now the MQTT connector does not support WS ingress, this could be an enhancement.

I'm using egress. It doesn't support it? I need to bridge my local EMQX to the public one.

the logic for both are the same

from emqx.

the logic for both are the same

is there a reason why the connector doesn't support WS/WSS? And also, why is the CA cert mandatory when using a destination broker with an official ssl cert, not self-signed? Shouldn't be needed.

from emqx.

@alexdelprete MQTT TCP can get better performance than ws. Why do you need to use ws/wss for transport?

from emqx.

@alexdelprete about certs. you can type in file paths in dashboard UI (does not have to be PEM content) if you can make sure the files exists in all EMQX nodes (when clustered).

MQTT bridge does not support websocket so far, MQTT over websocket for bridge is current not in our plan.

from emqx.

about certs. you can type in file paths in dashboard UI

question was not how it's configured, but why it's mandatory. it should be mandatory only when used vs a broker with self-signed certificate, that needs the CA cert to be validated. With the bridged broker using a valid trusted certificate, it shouldn't be needed.

MQTT over websocket for bridge is current not in our plan.

Understood. Am I wrong or in past versions (before connectors) it supported websocket also in bridge?

from emqx.

@alexdelprete Not supported before

from emqx.