The broker should talk with clients via secured communications.

[sacco221]

Chrome rejects to initialize the communication with the MQTT broker via WebSocket due to mixed-content restrictions.
It prevents the use of insecure ws:// URLs in web apps served over HTTPS.

As of now, the broker can talk with Microcontrollers via MQTT(TCP) and the front end via Web Socket.
However, the broker should talk with them under secured communication like MQTT with TLS and WebSocket Secure.

[sacco221]

We switch from Aedes, the MQTT broker that runs on Node.js to CloudMQTT for our production.