Open fabianotuccillo opened 2 years ago
Same issue for me. When using mosquitto 2.0.14 installed on EC2 instance in eu-west-1 region, bridge connects to IoT Core in the same region with no issues. However, when I install mosquito to the EC2 instance in ap-southeast-2 (Sydney) and trying to connect to the IoT Core in eu-west-1, I get protocol error
I did a small investigation and it showed that a protocol error
started to happen since 2.0.11. Though, in 2.0.10 it shows closed its connection
so it seems like starting from 2.0.11 it was a try to provide some meaningful error reason. I think the issue itself is in some of the earlier versions
1672835117: mosquitto version 2.0.10 starting
1672835117: Config loaded from mosquitto.conf.
1672835117: Starting in local only mode. Connections will only be possible from clients running on this machine.
1672835117: Create a configuration file which defines a listener to allow remote access.
1672835117: Opening ipv4 listen socket on port 1883.
1672835117: Opening ipv6 listen socket on port 1883.
1672835117: Bridge local.thing doing local SUBSCRIBE on topic #
1672835117: Connecting bridge awsiot (aaabbbcccdddee-ats.iot.eu-west-1.amazonaws.com:8883)
1672835117: Bridge thing sending CONNECT
1672835117: mosquitto version 2.0.10 running
1672835119: Client local.thing closed its connection.
When upgrading from 1.5.5 to 2.0.14 the bridge (ssl mode) stops working with a protocol error (this appends when mosquitto broker starts connection out of region where aws service is), the same issue is for both AWS IOT Core and ActiveMQ .
Here log for 2.0.14 version:
here that for 1.5.5:
attached mosquitto config
mosquitto_awsiot.conf.txt
The operating System where mosquitto is installed is Windows 10 Home.
All mosquitto brokers come from official mosquitto site.
Any suggestion?