Please Note This forum exists for community support for the Mango product family and the Radix IoT Platform. Although Radix IoT employees participate in this forum from time to time, there is no guarantee of a response to anything posted here, nor can Radix IoT, LLC guarantee the accuracy of any information expressed or conveyed. Specific project questions from customers with active support contracts are asked to send requests to

Radix IoT Website Mango 3 Documentation Website Mango 4 Documentation Website

  • I am quite new to MangoES V3 and trying to learn more.
    Currently, I am using a router modem (D-Link DWR-921) with 4G sim card in it. My PC and the MangoES V3 are connected through the LAN ports of the DWR-921. I am able to access the MangoES as well as internet and also my mobile phone can access MangoES through WiFi too.
    For the mobile phone access, I am hoping to access also remotely through the 4G network. I am not sure if this can be possible with this configuration. I think the DWR921 has 4G network connected, so I think mobile phone shall be able to connected through the router to access MangoEs somehow. Am I right or wrong? If it is possible, how can I set it up to allow such remote access from mobile phone? If not possible, any suggestions what I should use for remote access? Thanks

  • Hi @ozone

    you have a couple of options to make your MangoES publically available.

    1. Get an m2m sim card with a static IP address from your provider. You can then register a domain name and route it to your static IP address. On your router settings, you will need to forward port 80 to port 8080 on your mangoES IP address.

    2. Use a dynamic DNS service such as You will then need to set up the DNS settings on your router. This might be the easiest solution for small scale. You normally get a free account with up to 3 hostnames.

    3. Use a VPN service, each cellphone that needs to access the MangoES will need to login to the VPN server.

    for any of the above options, you will need to configure your router to forward all traffic incoming on port 80 to your MangoES.

    A more robust solution would be to set up an instance of mango on a cloud server. copy your dashboards over to the cloud server and then publish all your points with the mango persistence publisher to the cloud server.

    The advantages of this would be that your MangoES is not publically accessible, making it more secure. Your cloud server has much higher speeds and your 4g router won't have to upload all the dashboard data to each user on every login, so less data costs.

  • I use 1 and 3 combined with a cloud server myself. Works well where internet connection is a requirement. Also provided data redundancy.
    Best of luck


  • @craigweb
    Thanks for all the suggestions. Like the cloud server option.
    In the MangoES V3 I have, I found there is the cloud connect module installed but shows unlicensed. Is that what is required for cloud connect functions to work? I assume it allows to connect to mango cloud server, right? If I go head to use mango cloud server for the remote access, what is the cost for the cloud connect module license? and anything else required? costs for the cloud server?

  • @ozone

    In order to send data points to another Mango instance, you will use a Mango PTCP publisher(on the MangoES) to send points to a Mango PTCP data source on the cloud server.

    Cloud connect does not send data point data to another instance it sets up a VPN connection between the 2 instances. This will allow you to, from within your cloud server to navigate into the MangoES's webpage without doing any routeing on your router.
    An unlicensed cloud connected host can have up to 3 clients connected to it. The restrictions are only on the host side.

  • Cloud connect will allow you to act as a client if you have a non-free core license, but will not allow you to connect to a cloud connect server from an unlicensed core with an unlicensed cloud connect module. There would be a message in the Mango/logs/ma.log file when the client fails to start.