Most MQTT Explorer connection errors can be narrowed down by testing the path in order: address, transport, authentication, encryption, then topic permissions.
Check the broker address and port
Confirm you are using the broker host—not the Home Assistant dashboard address or another service. Standard MQTT, MQTT over TLS, and WebSocket endpoints can use different ports.
Separate authentication from authorization
A broker can accept a username and still deny subscriptions. If connection succeeds but the tree is empty, inspect ACL rules before changing unrelated settings.
TLS and certificate mistakes
If the broker requires TLS, verify hostname matching, certificate trust, and whether a client certificate is required. Avoid disabling certificate validation as a permanent workaround.
Firewall and network routing
Local DNS, VLAN rules, container networking, and host firewalls can all block a correct broker configuration. Test reachability from the same machine that runs the client.
Use a one-change-at-a-time checklist
- Host
- Port and protocol
- Username/password
- TLS details
- ACL/subscription scope
Related next steps
For a broader setup view, return to the installation section, check the FAQ, or browse the full guide library.