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.

Hello @mihairosu, It sounds like your diagnosis is on the right track. Here are the most likely causes based on what you’ve described: Check that the guest user actually has the Users role Since the point shows Users = checked and Anonymous = unchecked, the guest account must: Be successfully logged in Belong to the Users role If the guest account was created manually rather than through the usual user-creation workflow, it’s possible it never received that role. You can verify under Administration → Users → guest. Confirm whether auto‑login is actually succeeding If your auto‑login fails silently, Mango will treat the session as Anonymous, and any point that does not allow Anonymous access will simply disappear with no warning. To verify: Open your dashboard URL in a private/incognito window Check whether Mango shows you logged in as guest Also, your example URL uses: autoLoginPassword=guest1234 But you mentioned the password is guest. If those don’t match, the login will fail and the session becomes anonymous. For meta points specifically Meta data points inherit visibility from their own permissions, but their values come from underlying source points. If the guest user does not have permission to read one of the source points a meta point depends on, the meta point may appear on the dashboard but will fail to resolve a value. So make sure the source points also include the Users role (or whatever group your guest belongs to). Version change (5.6.2 → 5.6.3) Since this was working before the upgrade, it’s worth checking the 5.6.3 release notes. There have been a few changes recently around role evaluation and anonymous access. Even subtle permission tweaks could affect dashboards that rely on auto‑login. https://docs-v5.radixiot.com/v5-release-notes-overview

Hello @mihairosu, Single data point not publishing from MangoES to MangoEnterprise, steps to try: If other points on the same publisher are working but one specific point is not arriving on the Enterprise side, the most common cause is an XID mismatch introduced when the point was removed and re-added to the publisher. Work through these steps in order: On MangoES: Go to Publishers and open the publisher sending to MangoEnterprise Find the entry for the affected data point and note its Published Point XID (this is separate from the data point XID, it typically looks like PP_xxxxxxxx) Confirm the data point itself is healthy: add it to a Watch List and verify it is receiving fresh values from the Modbus source Confirm the data point's Logging Type is not set to Do Not Log, some publisher configurations will not forward a point that has no logged values On MangoEnterprise: Go to the Data Source that receives published data from MangoES Find the data point that is supposed to receive this value and open its configuration Look at the Point Locator, it will contain the Published Point XID it is listening for Compare this XID to the one you noted on MangoES, if they do not match, this is the cause To fix: Update the Point Locator on the MangoEnterprise data point to match the current Published Point XID from MangoES Save the data point, then disable and re-enable the data source on MangoEnterprise to force it to reconnect If the XIDs already match, also check: The data point and its data source are both enabled on MangoEnterprise The data type on the Enterprise point matches what MangoES is sending (e.g., both NUMERIC) The publisher on MangoES shows a healthy connection status with no errors The remove/re-add step almost always generates a new Published Point XID on MangoES while the Enterprise side still holds the old one, updating the Point Locator on Enterprise is usually all that is needed

@joeamiraglia Just wanted to confirm that the latest update as of a couple of days ago, was successful.

You might want to use a data file as a data source because it’s easy to manage, but if no data displays, there could be an issue with the file format or connection. For reliable data backup and recovery solutions, consider HostNoc to ensure your data stays safe and accessible. The keyword is data backup and recovery.

@LBryant are you using the H2 database or MySQL? One is harder than the other, if mysql, stop mango, make a fresh mango database setting then copy the password from the user generated in the new db and overwrite the password on your user in the original, that will set it to admin. Change back to your old db settings and log in. If H2, stop mango, rename database folder and restart, this will cause mango to generate a new h2 db. Stop mango and use the h2 web utility supplied in the mango/bin directory to access the new database, obtain the password from the admin user. Close then repeat with the old database and update the password. Rename database folder and restore the original folder back to database again. Log in with admin password Fox

@dovydasz said in Pi Portfolio creating: I still can't get it working.. Could you please share some screenshots how you configured it? Do I need to you some specific values for datapoints tags keys? Give me Direct message, your whatapps number. I will give you a hand in Monday. I have vacation tomorrow. But can you try this: Provide your data points 3 important tags, which are deviceType, site, deviceID  This information is not emphasized in Radix instruction and you may miss this part.

Hello @jcaballeroa, sorry for the delay on this topic but could you please open a support request at Radix IoT - Support? I would like to better assist on this topic but access to the files have expired. Also, have you tried to start a clean Mango v5 to see if you have any issue starting up Mango before upgrading?

@terrypacker thank you

@Jared-Wiltshire how to change the time? It should not use "now" - instead a fix time like 06:00 a.m. Thanks!

@vishalcapri Hi there, Apologies for the issues here, but I fixed this issue yesterday or the day before. I did something incorrectly with the renewal process, and it caused this strange behavior. Can you try again and let me know if it's fixed for you? Liv