Eclipse Projects Broker: connection details & online test

Public sandbox from the Eclipse IoT working group, with WebSockets on standard web ports.

Endpoints and ports

TransportURLCopy
MQTT (TCP)mqtt://mqtt.eclipseprojects.io:1883
MQTT over TLSmqtts://mqtt.eclipseprojects.io:8883
WebSocketws://mqtt.eclipseprojects.io:80/mqtt
Secure WebSocketwss://mqtt.eclipseprojects.io:443/mqtt

About Eclipse Projects Broker

mqtt.eclipseprojects.io is a public MQTT sandbox maintained by the Eclipse Foundation for the Eclipse IoT community. Its WebSocket listeners use the standard ports 80 and 443, which helps when testing from networks that block uncommon ports.

Highlights

  • WebSockets on ports 80 / 443
  • No sign-up
  • Community-maintained

Limitations

  • Fully public
  • No authentication
  • Best-effort availability

Connect with code

mosquitto CLI
mosquitto_sub -h mqtt.eclipseprojects.io -p 1883 -t 'testmqtt/eclipse/#' -v
MQTT.js (browser or Node.js)
import mqtt from 'mqtt';

const client = mqtt.connect('wss://mqtt.eclipseprojects.io:443/mqtt');

client.on('connect', () => {
  client.subscribe('testmqtt/eclipse/#');
  client.publish('testmqtt/eclipse/hello', 'Hello from MQTT.js');
});

client.on('message', (topic, payload) => {
  console.log(topic, payload.toString());
});

Having trouble? See common MQTT connection errors or learn how to test an MQTT broker step by step.

From the makers of TestMQTT

Outgrown the public sandbox?

Public test brokers are shared with thousands of strangers. ConnectMQ gives you a private MQTT broker you can trust with real devices — set up in minutes.

  • Your own isolated broker — nobody else can read your topics
  • Username / password auth and per-topic access control
  • TLS and secure WebSockets, MQTT 3.1.1 and MQTT 5
  • Same client code from first test to production

Other MQTT brokers