Article - CS332989
MQTT Client Agent in IoT Gateway Not Connecting to MQTT Broker End Point
Modified: 02-Nov-2020
Applies To
- Kepware Server (formerly KEPServerEX) 5.21.236.0 to 6.13
- ThingWorx Kepware Server (legacy) 8.0 to 8.4
Description
Problem: In current versions of KEPServerEX, the MQTT Client Agent can be configured in such a way that it prevents proper connectivity to the target MQTT broker or end point. Solution: Ensure that the URL field in the MQTT Client Agent properties is configured correctly. The URL field MUST be in the format "tcp://:" or "ssl://:" where is the IP address or URL and is the port of the end point target. There should be no additional characters or "/" after the port of the end point.
This is a printer-friendly version of Article 332989 and may be out of date. For the latest version click CS332989