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.

@jared-wiltshire Oh I know... that's a whole other issue. I'm painfully aware how silly this is!

Hi, Terry, Is the comment you made here: https://forum.mango-os.com/topic/4691/virtual-serial-client/24 still valid? This seems like the exact situation we have. This device is a black box, and cannot connect to our IP:port, we have to open a socket to it and just listen to capture packets that it sends out. Based on your note, it sounds like using a Virtual Serial Client with a Serial data source won't work. If that's the case, is the only real solution to create some middleware/applet that connects to the host and reads the data, then pass it along to Mango in a way it can read? We thought that if the device passes data every 6 seconds, and we use a TCP/IP Data Source to poll it every 3 seconds, we'd be guaranteed to get all of the packets, but that actually made the results worse, and we got fewer packets than when we had it polling every 6.3 seconds. (Don't know why adding the 0.3 seconds makes a difference, but it definitely does.) Thanks, Chad

@dan I have the same issue after updating Mango to the core v3.7.7 Chrome version is 92.0.4515.131 (Official Build) (64-bit) When I switch to the old interface and switch to the Datasources tab, the list of data sources does not appear, just the empty white space. The data point tab works well. In the new interface, everything is alright. When checking the browser's console I found there a bunch of errors like this ones: Note: The actual IP address is removed and changed with <IP_address> tag. DevTools failed to load source map: Could not load content for http://<IP_address>/resources/dijit/layout/TabController.js.map: HTTP error: status code 404, net::ERR_HTTP_RESPONSE_CODE_FAILURE DevTools failed to load source map: Could not load content for http://<IP_address>/resources/dijit/layout/StackController.js.map: HTTP error: status code 404, net::ERR_HTTP_RESPONSE_CODE_FAILURE DevTools failed to load source map: Could not load content for http://<IP_address>/resources/dijit/Menu.js.map: HTTP error: status code 404, net::ERR_HTTP_RESPONSE_CODE_FAILURE DevTools failed to load source map: Could not load content for http://<IP_address>/resources/dijit/DropDownMenu.js.map: HTTP error: status code 404, net::ERR_HTTP_RESPONSE_CODE_FAILURE DevTools failed to load source map: Could not load content for http://<IP_address>/resources/dijit/_MenuBase.js.map: HTTP error: status code 404, net::ERR_HTTP_RESPONSE_CODE_FAILURE DevTools failed to load source map: Could not load content for http://<IP_address>/resources/dijit/_KeyNavContainer.js.map: HTTP error: status code 404, net::ERR_HTTP_RESPONSE_CODE_FAILURE DevTools failed to load source map: Could not load content for http://<IP_address>/resources/dijit/_KeyNavMixin.js.map: HTTP error: status code 404, net::ERR_HTTP_RESPONSE_CODE_FAILURE DevTools failed to load source map: Could not load content for http://<IP_address>/resources/dijit/MenuItem.js.map: HTTP error: status code 404, net::ERR_HTTP_RESPONSE_CODE_FAILURE DevTools failed to load source map: Could not load content for http://<IP_address>/resources/dijit/layout/ScrollingTabController.js.map: HTTP error: status code 404, net::ERR_HTTP_RESPONSE_CODE_FAILURE DevTools failed to load source map: Could not load content for http://<IP_address>/resources/dijit/PopupMenuItem.js.map: HTTP error: status code 404, net::ERR_HTTP_RESPONSE_CODE_FAILURE DevTools failed to load source map: Could not load content for http://<IP_address>/resources/dijit/_WidgetsInTemplateMixin.js.map: HTTP error: status code 404, net::ERR_HTTP_RESPONSE_CODE_FAILURE DevTools failed to load source map: Could not load content for http://<IP_address>/resources/dijit/CheckedMenuItem.js.map: HTTP error: status code 404, net::ERR_HTTP_RESPONSE_CODE_FAILURE DevTools failed to load source map: Could not load content for http://<IP_address>/resources/dijit/MenuSeparator.js.map: HTTP error: status code 404, net::ERR_HTTP_RESPONSE_CODE_FAILURE

@robmalone said in SSL/HTTP Post error: Once the Mango environmental properties file was pointing to the keystore it worked. So you are all good now? Or still having issues? If you are still stuck you should follow the recommendations in that StackTrace link about enabling SSL logging by adding this to the java command that is starting mango: -Djavax.net.debug=SSL And seeing what the details of the problem are.

@holzatelier Just a little update on this. It seems the data points are indeed updated on my system when timestamps are passed along with the JSON data. What I didn't realize is that if the timestamp predates the last entry in the point value history then the browser window needs to be refreshed to show the added historic data value. So this works for me now besides the missing JSON parsing Error. Thank you again for your attention.

Too tough a question?

@malaguena unfortunately this is not supported. It is possible but would need to be added as a new feature in a future release. If this is something important to you I suggest contacting our support team and making a feature request through them to see what can be done.

@joelhaggar Thanks Joel, that would be great, thanks. Cheers Dan

@ottawa_admin on many linux distros resolv.conf tends to have a blurb similar to this "# This file is managed by man:systemd-resolved(8). Do not edit." I can't remember how the ES works but that's something that will burn you if it's not configured correctly. Restarting the mango service itself would not affect it since this is a system level function. What you'd need to do is restart the whole ES so that Linux reboots and then have a look to see if your entries are still there.

@psysak It me a bit to figure out the right Java version for the Mac M1 but this is the version I installed: java -version openjdk version "11.0.11" 2021-04-20 LTS OpenJDK Runtime Environment Zulu11.48+21-CA (build 11.0.11+9-LTS) OpenJDK 64-Bit Server VM Zulu11.48+21-CA (build 11.0.11+9-LTS, mixed mode)

@holzatelier Not your fault :) I reviewed the help document and found the information was missing. Glad we got it resolved.

@fusepl What version of Mango are you using: e.g. 3.7.7 What version of Java are you using: Oracle Java 8, or Adopt OpenJDK 11 What is your operating system: e.g. Windows x64, Ubuntu Linux 20.04 How did you install Mango: e.g. install script, or manual install, updated from 3.6.0 How did you start Mango: e.g. systemctl start mango, or ma.sh start Include the log file: post ma.log What browser are you using? e.g. Chrome 91.0.4472.124