I have a trial account of tulip, and I have a Mqtt broker running on my local machine, when I am trying to use mqtt connector to connect to mqtt broker over secured websocket I am not able to connect it. I am trying to connect over port 8000.
Are there network settings needs to be done? like enable port or allow url in tulip. or open port on local machine to connect to tulip?
how does network setting works in this case?
Hi @p.bhagwan.gaikwad and welcome to Tulip Community! 
I want to check first, if you have seen this article and guidance here? How To Build Your First MQTT Connector
When you say you are not able to connect, are you seeing any error messages that you could share?
Hi Beth,
Yes, I have tried above link, in this case my setup is as follow:
- Hivemq-edge mqtt broker running on my local machine which secured websocket on port 8000.
- Tulip instance deployed on cloud - Tulip | Custom widgets
- I am trying to connect to connect to hivemq using following server configuration, server address mentioned is a public IP address of my laptop.
- The error I am getting is - Test failed: [500] Error: Timeout.
Apart from this, my other question was, we want to use custom widget which will connect to mqtt broker using javascript code. for this I want to understand what all network settings are required if tulip instance is on cloud and hivemq-edge is on virtual machine.
Gotcha!
As a first debugging step, can you verify if you can connect to this MQTT broker from a machine outside your network? (To validate that the IP address really is reachable and their ports are forwarded properly). You can use any MQTT cli to check this.
On the question of using a custom widget as a MQTT client, this should be possible and I will look into the specific requirements to do so.