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 support@radixiot.com.

For anyone saw this topic, solution is: Changing ssl.on=true to ssl.on=false

@benjamin-perez Thanks Benjamin, looking forward to know if it's my mistake somewhere or a bug.
I've also asked @MattFox to take a look at this. His thoughts, bug.

Regards,
Rodrigo

@rob987 This is the most detail instruction regarding MQTT for new user. I highly recommend using his instruction. New user should check ma.log to check if data source is correct setup to read data from MQTT broker before working on data point.

I found the BACnet local devices menu in the Utilities section under "Admin Home". Here you can create or modify the local devices. Once you create a local device there, it is available in the add new data sources section

@cbyrne I think it is a side affect of why we implemented the 'Sets historical' feature. That is there to allow importing or generating large amounts of historical data which bypass the point-value event system. This prevents an overload of web socket messages and event detectors raising events.

@jared-wiltshire Well, I just face same problem with v4 today. And since V4 no longer allow legacy UI. I don't know how to correct the mangoUI-settings Json! Any suggestion?

@jim-betsinger

https://forum.mango-os.com/topic/1150/importing-large-numbers-of-data-points-from-an-excel-spreadsheet

https://docs-v3.mango-os.com/using-data-point-templates

I wanted to provide another round of updates as we've run into this issue two more times.

The most recent time we had the issue an app restart did stop the error from being written to the ma.log, but the corrupt file was still hanging around. After several days it did go away, so it seems whatever process Mango uses to clean up the files eventually worked.

While working with the support team we were pointed to look for other programs that could possibly lock one of the data files while NoSQL is trying to write to it. If that happens, this issue could occur.

I checked with our infrastructure team and they had an antivirus program that was performing checks on the NoSQL database directory. The antivirus has been disabled for that folder now.

I also found this post about Windows Indexing locking files: https://techcommunity.microsoft.com/t5/windows-blog-archive/the-case-of-the-mysterious-locked-file/ba-p/723349 Because of this I made sure to uncheck the "Allow files in this folder to have contents indexed..." option as that could have also contributed to the file being locked when NoSQL needed to write to it.
88a06ac2-35a1-4ca0-a3ef-b3af0d1263fa-image.png

So far things are good since making those updates. Hopefully this helps anyone that may run into this.

Thanks,
Chad

I have the same issue with the Mango 3.7 version

Thanks for feedback,
we just used TCP profile on rev proxy , without http then and it works all right. We will do SSL termination on server then.

br

Hi!

This issue was solved today.
The Exchange 2016 server opened port 25 with TLS.
Tested mail was sent success.

Thanks Terry, that worked

@dennisbetty201 Phillip's instructions will not fix this issue. Please see https://forum.mango-os.com/topic/3551/data-sources-does-not-appear/14 or download an old web browser (e.g. standalone Firefox)

@jared-wiltshire Ah I figured out what it is.

I expected the historian GUis to be native on HTTPS, but I forgot I let them be on HTTP...

The other issue is with my HAProxy, which I figured out as well.

What confused me is that I attempted to reach the GUI via HTTPs and thought they were down.