@white-piano-73111 @rich-agency-14084 I did not mean websockets instead of MQTT, I meant MQTT over websockets, as explained here: http://www.steves-internet-guide.com/mqtt-websockets/. The inner data is still the MQTT data packet, with an added websocket enveloppe. The reason websockets exist is to use the HTTP handshake to establish a connection (to overcome the initial problem that started this discussion where firewalls only have port 443 open), and to allow bidirectional communication. Websocket support comes out of the box with Mosquitto (and many other MQ brokers). The netmaker team would need to make the netclient compatible with adding a websocket enveloppe. Example code is here: https://github.com/zhengjia/go-mqtt-websocket. The TLS side of the connection does not need to change: TLS is supported, also client certs are.