Custom Widget does not connect to HiveMQ MQTT broker over secured websocket

Support, Troubleshooting, & Help
,
1

Hi,
I Have integrated the custom widget with MQTT broker using the code you have given me in [Custom Widget with MQTT broker(Networking understanding for connecting mqtt broker to tulip - #5 by Beth)

My MQTT broker is Hive MQ, it is setup using a CA signed certificate to allow secured WebSocket server.

When I run custom widget, it does not connect to Secured MQTT broker directly. It runs into privacy error.

The fix to this is - Open https://<mqtt broker ip address>:8000 in a browser, click on Advanced, and proceed past the certificate warning. After that, the connection works fine. Find attached screenshot.

image
image1422×876 51.4 KB

image
image1433×905 72.7 KB

When I click on proceed it custom widget connects with MQTT broker and data starts coming.

But when I integrate this in a Tulip App and try to run the app in tulip player installed on my machine, custom widget does not work and there is no option to browser URL and bypass certificate warning.

I need help with 2 things:

  1. How to handle this on tulip player?
  2. We do not want user to follow above process to get custom widget working what is the solution to trust server certificate in Tulip?

We have faced this issue with other front-end application like react js, who was facing issue with Self-signed certificates, When CA signed certificate was added at server side, front-end started working without any privacy warning.