Get Started

You can visit our online address to use MQTTX Web, or private deployment to your server.

Creating connections, subscribing, and publishing messages follow the same basic workflow as MQTTX Desktop. See the Desktop Getting Started guide for these steps, and use the Advanced guide only for features available in Web. The differences below describe the Web version’s limits.

Differences Between Web and Desktop Versions

  • The Web version only supports connecting to the MQTT Broker via WebSocket and does not support TCP connections. For more information, please refer to the WebSocket connection guide.
  • In the online version of MQTTX Web, we use the https:// protocol for security reasons. Therefore, it is impossible to use the ws:// protocol to connect to the MQTT Broker; the wss:// protocol must be used. If you need to use the ws:// protocol, you can deploy it over HTTP or download the desktop and command line clients. For more details, please visit the migration announcement.
  • MQTTX Web cannot configure client certificate and private key files for mutual TLS authentication. Use MQTTX Desktop or CLI for connections that require these files.

MQTTX Web supports managing connections and subscriptions and viewing sent and received messages. Desktop features such as MQTTX Agent and Viewer (Topic Tree, Dashboard, and Traffic Monitor) are not available in Web.

Self-hosting does not remove browser transport restrictions: a deployment served over HTTPS still requires wss://.

Privatization Deployment

We provide Docker image for users who want to privatize deployment, you can quickly deploy it through the following command, you can also refer to Development Guide to build and deploy by yourself.

docker pull emqx/mqttx-web

docker run -d --name mqttx-web -p 80:80 emqx/mqttx-web