• Edited

Wondering is it applicable to have custom domain mapping to mqtt.flespi.io api endpoint.
So as to connect to my domain e.g. mqtt.mydomain.com ?

Thanks

    Abdozy, you can register your own domain name as a CNAME pointing to the mqtt.flespi.io, but this will work only for plain (non-SSL) mqtt connections.
    And a more universal solution will be to start a mqtt bridge service on your own server.

      • Edited

      Got it, thanks for your reply, already did, but when connecting to wss://mqtt.mydomain.com, it did not work, that's why as you said, it only work for non-SSL mqtt conenction.
      for the second solution you mean to enable streams to third party mqtt which is the bridge, right ? for the WSS connections
      I was thinking, in addition to the CNAME config, why not in future having it as a feature in Flespi Control Panel, like e.g. Vercel dashboard, instead of setting up a proxy mqtt service.

      Thanks

        Abdozy

        Got it, thanks for your reply, for the second solution you mean to enable streams to third party mqtt which is the bridge, right ? for the WSS connections

        No, if you need a broker with SSL support (WSS requires SSL) but with a custom domain name, you have to start your own broker on that domain name. And additionally with bridge functionality to the mqtt.flespi.io to provide access to it. flespi streams is not related here in any way.

        I was thinking, in addition to the CNAME config, why not in future having it as a feature in Flespi Control Panel, like e.g. Vercel dashboard.

        Because only DNS registrar of your domain name allows you to manage your domain's CNAME.

          kial Aha got it, I think the bridging feature might add a bit of latency for receiving messages

            Abdozy Yes, but depending on the round-trip from your broker to mqtt.flespi.io it can be very small

              Write a Reply...