Problem using AmazonMQ (activemq) as MQTT Broker

[happidad]

I have an Amazon MQ broker running activemq as my MQTT broker. AmazonMQ only supports SSL connections. I have successfully connected to this broker with the latest v3 application-server, the latest v3 network-server, the latest v3 gateway-bridge, v4 gateway-bridge and a mosquitto_sub client and mosquitto_pub client.

Using the same credentials, I can not connect to Amazon MQ with the v4 chirpstack. The logs for Amazon MQ are not very informative:

WARN | Transport Connection to: tcp://84.156.217.243:48022 failed: Invalid message encoding | org.apache.activemq.broker.TransportConnection.Transport | ActiveMQ Transport: ssl:///84.156.217.243:48022

This is a similar message that usually seen when attempting to use a SSL enabled port without SSL or vice versa. But since I have successfully connected with SSL from all those other clients, I’m fairly confident the connection should work.

I have wireshark traces for a successful connection from mosquitto_sub (mosquitto_good_activemq.pcap - Google Drive) and an unsuccessful connection from v4 chirpstack (cs_bad_activemq.pcap - Google Drive).

We were originally thinking that maybe the SSL cipher alg selection was failing, but the wireshark traces make it appear that there is successful encryption occurring.

I was wondering if anyone else came across this issue, or is successfully using Amazon MQ with chirpstack v4?

[brocaar]

Does the Amazon MQ broker supports MQTTv5?

[happidad]

Ah yes. That is the issue. Amazon MQ is pretty slow in supporting new versions and they are stuck on an older version that does not support MQTTv5 yet. That explains it. Thanks a lot.

I’m currently working on using AWS IOT core for the MQTT broker. Thanks for the help!