
Fast MQTT Broker - Technical Support Information
Technical Support Guide
Thank you for choosing Fast MQTT Broker, your easy-to-use solution for setting up and managing MQTT servers on mobile devices. This guide will help you configure the broker, connect clients, and resolve common issues.
Using Fast MQTT Broker:
- Server Setup – Start and configure your MQTT broker:
- Server Status: Check if the broker is running (Started/Stopped)
- Start Server: Tap to launch the MQTT broker with current settings
- Settings (Gear Icon): Customize protocol version and ports
- Protocol Version Selection:
- Choose between MQTT v3.0.0, v3.1.1, and v5.0 to match your client compatibility needs
- Port Configuration:
- TCP Port: Default 1883 (standard MQTT client connection port)
- WebSocket Port: Default 1882 (for web browser client connections)
- HTTP Info Port: Default 8080 (provides server status and statistics)
- Real-time Logs: Monitor client connections and message transfer details once the server is running
Troubleshooting:
- Server Fails to Start:
- Verify ports (1883, 1882, 8080) are not occupied by other applications
- Check if your device has sufficient resources to run the broker
- Try restarting the app and reattempting to start the server
- Client Connection Issues:
- Ensure the client uses the correct protocol version matching the broker’s setting
- Verify the client’s host address is your device’s IP and the correct port (1883 for TCP, 1882 for WebSocket)
- Check if your device’s firewall or network settings are blocking incoming connections
- Test with a simple MQTT client tool to isolate the issue
- Missing Logs or Statistics:
- Confirm the server is running (status should be "Started")
- Check if clients have successfully connected and transmitted messages
- Restart the server and reconnect clients to trigger log generation
- Protocol Compatibility Errors:
- Ensure the client and broker use the same MQTT protocol version
- Review the client’s protocol version documentation for compatibility details
- Try switching to a different protocol version in the broker settings
Important Notes:
- The broker runs locally on your mobile device, so client devices must be on the same network (or your device must have a public IP with port forwarding)
- Always check port availability to avoid conflicts with other services
- Real-time logs help in debugging connection and message transfer issues