But your clients do not connect over MQTT to thingsboard correct? They use the webUI 8080? (which is why that port was taken) If so I’d assume you can disable the whole broker, I’ll look into it and get back to you.
I looked into it, the MQTT broker with Thingsboard is optional, and from what you have explained of your use case you don’t need it.
If changing the port doesn’t help, or you decide you don’t want this extra overhead and potential vulnerability. Try setting tb-mqtt-broker.enabled: false in the thingsboard.yml file. It will disable ThingsBoard from starting its internal MQTT broker (TBMQ) entirely. This setting stops the broker component itself, rather than merely stopping ThingsBoard from trying to communicate with it.