mosquitto_sub -h broker.mqttdashboard.com -p 1883 -t EdgeXEvents shows time out for edgex-app-mqtt container service

[chiranjivSharma]

app-service-mqtt: container_name: edgex-app-mqtt depends_on:

• consul
• data environment: CLIENTS_CORE_COMMAND_HOST: edgex-core-command CLIENTS_CORE_DATA_HOST: edgex-core-data CLIENTS_CORE_METADATA_HOST: edgex-core-metadata CLIENTS_SUPPORT_NOTIFICATIONS_HOST: edgex-support-notifications CLIENTS_SUPPORT_SCHEDULER_HOST: edgex-support-scheduler DATABASES_PRIMARY_HOST: edgex-redis EDGEX_PROFILE: mqtt-export EDGEX_SECURITY_SECRET_STORE: "false" MESSAGEQUEUE_HOST: edgex-redis REGISTRY_HOST: edgex-core-consul SERVICE_HOST: edgex-app-mqtt TRIGGER_EDGEXMESSAGEBUS_PUBLISHHOST_HOST: edgex-redis TRIGGER_EDGEXMESSAGEBUS_SUBSCRIBEHOST_HOST: edgex-redis WRITABLE_PIPELINE_FUNCTIONS_MQTTEXPORT_PARAMETERS_BROKERADDRESS: tcp://broker.mqttdashboard.com:1883 WRITABLE_PIPELINE_FUNCTIONS_MQTTEXPORT_PARAMETERS_TOPIC: EdgeXEvents hostname: edgex-app-mqtt image: edgexfoundry/app-service-configurable:2.0.0 networks: edgex-network: {} ports:
• 127.0.0.1:59702:59702/tcp read_only: true security_opt:
• no-new-privileges:true user: 2002:2001

Used it inside docker compose file and started edgex-app-mqtt container.But con -h broker.mqttdashboard.com -p 1883 shows timeout.Tried mosquito as well- mosquitto_sub -h broker.mqttdashboard.com -p 1883 -t EdgeXEvents. But that also timeouts.

[lenny-goodell]

Have you looked at the docker logs for app-service-mqtt ?

[lenny-goodell]

Closing due to no response