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.

Categories

  • The latest news in the Mango world

    424 Topics
    558 Posts
    joeamiragliaJ
    Three patch releases have shipped on each line since the last advisory (5.6.12 / 5.7.5). Affected versions: all 5.6.x releases prior to 5.6.15, and all 5.7.x releases prior to 5.7.8. We recommend upgrading to 5.6.15 or 5.7.8. Full changelogs: 5.6.x / 5.7.x. Mango 5.6.x 5.6.13 (Sep 28, 2026) Security: BouncyCastle upgraded to 1.86, resolving CVE-2026-8763 and CVE-2026-13506 (neither exploitable in Mango's configuration). Apache SSHD, used by Cloud Connect, upgraded to 2.19.0, resolving CVE-2026-56624. Security: FreeMarker upgraded to 2.3.35, hardening template loading against directory traversal, XML-escaping xmlns, and restricting a template's ability to list Java system properties. Breaking change: Mango may now reject private keys or certificates with unusually expensive key-derivation parameters or malformed subject names at startup, due to stricter BouncyCastle limits on untrusted input. Fixed an event-acknowledgement rollback bug, and a failing event handler blocking every handler after it, on the Events page. 5.6.14 (Oct 5, 2026) Security: Fixed CVE-2026-84939, a path traversal via a malformed locale identifier, by upgrading the bundled Moment.js UI dependency to 2.31.0. Security: Jackson (jackson-databind) upgraded to 2.21.7, fixing two denial-of-service CVEs (2026-91777, 2026-91776). Mango doesn't use the feature behind the first; the second can only be triggered by the remote source a Persistent TCP publisher connects to. Fixed the Cloud Connect proxy filter intercepting requests for any hostname under its configured proxy domain even while the proxy itself was disabled, a regression present since 5.6.0. The filter now only registers when the proxy is explicitly enabled. Fixed several data sources and publishers (BACnet COV, VMStat, SNMP traps, MQTT Sparkplug, Modbus IP publisher) running on background threads without a security context, which silently dropped event detectors, meta point updates, and reconnect handling. 5.6.15 (Oct 14, 2026, latest) Security: Fixed CVE-2026-106451, a local privilege escalation in lz4-java. On a server where Mango connects to ClickHouse, another local user could replace the native library Mango extracts to its temp directory and run code inside Mango. If you can't upgrade immediately, set paths.temp in mango.properties to a directory only the Mango user can write to. A BACnet device writing to a published object's non-presentValue properties (e.g. description) no longer sets the corresponding Mango point value; only writes to presentValue do. Fixed events raised by non-superadmin users, or by a data source/publisher with no signed-in user, failing to notify configured event handlers and alarm recipients. Fixed acknowledging an event as a non-superadmin user stopping its handlers from firing when the event returns to normal. Mango 5.7.x 5.7.6 (Sep 23, 2026) Security: Same BouncyCastle and Apache SSHD fixes as 5.6.13 above. Security: Watch-list maintenance events previously evaluated the watch list as superadmin, regardless of who configured the event, so it could suppress alarms on points the configuring user couldn't even read. A new "Roles used to resolve watch list points" setting scopes this correctly. Existing events are migrated to superadmin to preserve current behavior; review them if that's broader than intended. (5.7.x only, not backported to 5.6.x) New OAuth 2.0 / OIDC extraClaims feature: fetch additional claims (groups, roles) from an HTTP endpoint for identity providers that can't include them directly in the token. (5.7.x only) gRPC connections now send keepalive pings, detecting a vanished peer in about 90 seconds instead of stalling indefinitely. (5.7.x only) Breaking change: Same stricter BouncyCastle key/certificate validation as 5.6.13. 5.7.7 (Oct 5, 2026) Security: Same FreeMarker hardening as 5.6.13 (lands one release later on this line). Security: Same Moment.js (CVE-2026-84939) and Jackson (CVE-2026-91777, CVE-2026-91776) fixes as 5.6.14. Same Cloud Connect proxy filter fix and background-thread security context fix as 5.6.14. 5.7.8 (Oct 14, 2026, latest) Security: Same lz4-java fix as 5.6.15 (CVE-2026-106451). Also upgrades Spring Framework to 7.0.9, fixing CVE-2026-47884 and CVE-2026-47890 - Mango isn't affected by either, since it doesn't use XSLT views or render view fragments as server-sent events. (Spring upgrade is 5.7.x only) Fixed authentication tokens being rejected once a user's password expired, which broke token-based integrations (e.g. polling engines) with no visible error. Token validity no longer depends on password age. (5.7.x only) Same BACnet publisher property-write fix and non-superadmin event-handling fixes as 5.6.15. As always, back up your database and configuration before upgrading, and test in a non-production environment first.
  • For questions regarding Mango configuration and operation.

    2k Topics
    10k Posts
    joeamiragliaJ
    Good catch on the Jetty default. That requestHeaderSize limit comes from Jetty itself (the embedded web server Mango runs on), and Mango doesn't currently expose a mango.properties setting that maps to it. Mango exposes other web server tuning properties (web.threads.maximum, web.requests.queueSize, file upload and websocket buffer sizes, etc.), but request header size isn't wired through. A couple of options: Trim the proxy's injected headers. If your in-house proxy is adding several large headers, reducing what it injects (or moving some of that data to a request body/cookie instead) addresses the actual cause rather than working around a limit. Terminate at a reverse proxy in front of Mango. Nginx or Apache in front of Mango (see our HTTP and HTTPS Settings guide) gives you a layer where header size limits are configurable (large_client_header_buffers in nginx, for example) before the request reaches Mango's embedded Jetty server at all. This is likely your most practical fix given the limit is coming from Jetty's defaults.
  • An area to discus and learn to create custom dashboards, web apps and pages.

    447 Topics
    2k Posts
    No new posts.
  • Installation, Getting Started and Basic Configuration Tutorials. Please only post request for new tutorial here and all other user help in the appropriate forum below.

    113 Topics
    596 Posts
    No new posts.
  • Show other users how to get interesting things done.

    431 Topics
    2k Posts
    joeamiragliaJ
    Re: Copying/recreating a Meta Data source from project to project @SGAF apologies for the long delay on this; here’s a complete walkthrough. Exporting the Meta Data Source Go directly to the Meta Data Source itself (Data Integration > Data Sources, select it). Click the ⋮ menu in the top right and choose Export with points, this exports the data source and all its meta points together as JSON in one step, without going through the full Import/Export page. Preparing the JSON for the new site In the exported JSON, give the Meta Data Source a new, unique xid for the new site (e.g. META_SITEB), unless you intend to overwrite an identical one already on the target. For every meta point under dataPoints, update its dataSourceXid to match the new Meta Data Source’s xid, and give each point its own unique xid as well (e.g. prefix with the site name, like SITEB_DP_ZoneTemp). This is the step you already identified: each meta point’s script references context points by XID (the real underlying data points it reads). Those context XIDs need to be remapped to the equivalent real points on the new site before importing. Importing Go to Administration > Import/Export, paste or upload the edited JSON, and import. You need an admin account, non-admin users get a “Permission denied” error on import. On the error you hit The most common causes of an import failing are: A data point’s dataSourceXid doesn’t match any data source in the import or on the target (often from a typo when reassigning XIDs) A duplicate XID that collides with something unrelated already in the system Malformed JSON from a manual edit (missing comma/bracket), which shows up as a generic “Bad Request” instead of a specific error If you still have the exact error message or result summary Mango gave you, paste it here and we can pinpoint it directly. One more option: if you’re doing this for many similar sites, it may be worth scripting the XID remap with something like jq against the exported JSON rather than editing by hand each time, this avoids the typo/bracket issues above. Happy to help put that together if it’d save you time.
  • Do you have concerns, opinions or suspect you found a bug? We want to know!

    191 Topics
    820 Posts
    No new posts.
  • What do you want to see that you don't already? All requests are seriously considered. Let us know by posting your enhancement description along with a clever fruit metaphor.

    171 Topics
    744 Posts
    No new posts.
  • Anything goes section for developers to discuss issues regarding Mango source code

    151 Topics
    874 Posts
    No new posts.
  • Discussions of hardware and vendors that work with Mango

    97 Topics
    534 Posts
    joeamiragliaJ
    The RD201C is a higher-performance edge gateway for demanding industrial environments: an Intel quad-core processor, dual Gigabit Ethernet, isolated digital I/O, and expandable storage, running Mango by Radix IoT for enterprise-grade edge data collection and control. Specs: Processor Intel Celeron J6412, Quad-Core 2.0 GHz Memory 8 GB DDR4 (expandable to 32 GB) Storage 1 TB M.2 SSD (expandable) Ethernet 2x Gigabit RJ-45 (Intel i226-V) Serial 2x RS-485, 2x RS-232 USB 2x USB 3.0, 2x USB 2.0 Wireless Wi-Fi 6 + Bluetooth 5.2 (optional) Digital I/O 8x DI, 4x DO (isolated) Power 9-36 VDC, < 15 W typical Operating Temp -30 C to +70 C Dimensions 200 x 120 x 42 mm Mounting DIN rail, wall, or VESA mount OS Embedded Linux (Debian-based) Enclosure Fanless aluminum, IP40 Expansion 1x Mini PCIe, 1x M.2 (B-Key) Display HDMI 2.0 output Supported protocols: BACnet IP, BACnet MS/TP, Modbus TCP, Modbus RTU, DNP3 IP, DNP3 Serial, MQTT Sparkplug B, SNMP, HTTP JSON, SQL, gRPC, InfluxDB Line Protocol, Serial, SSH (additional protocols available via Mango by Radix IoT modules). Also includes TPM 2.0 for hardware-rooted secure boot and credential storage. Full details and datasheet: radixiot.com/hardware/rd201c
  • How are you using Mango? What equipment do you have it connected to? Let others know about the possibilities!

    23 Topics
    109 Posts
    No new posts.
  • Whatever you want to know about this package.

    151 Topics
    600 Posts
    Tasha MakseT
    Re: [using Modbus4j](Jumping values while reading value from secure elite 440-447 energy meter) thanks for the information!
  • Whatever you want to know about this package.

    336 Topics
    1k Posts
    joeamiragliaJ
    @dev1-spl-hk Thanks for the detailed report, and for pinpointing the exact fix. You’re right on both counts: the BACnet spec (ANSI/ASHRAE 135-2024, clause 21 and clause 13.9.1.1.13) marks Event Values as optional/conditional, and the encoder in UnconfirmedEventNotificationRequest already uses writeOptional for it, so this is a real inconsistency, BACnet4J currently can’t decode a message it’s able to send. This is tracked internally and will be fixed in the next release of BACnet4J (targeted for 7.0.0): the fix decodes tag 12 with readOptional instead of read Oh yeah, matching what ConfirmedEventNotificationRequest already does correctly. For bug reports like this going forward, the [BACnet4J GitHub repo](https://github.com/RadixIoT/BACnet4J Why) is the best place to file them, the developers who work on the library monitor issues there more closely than the forum. Appreciate you taking the time to trace this down to the exact line and commit.
  • Forum for discussions regarding the Mango Scripting environment within Meta Data Points and Scripting Data Sources.

    145 Topics
    913 Posts
    MattFoxM
    @tungthanh500 get rid of the runtime sleep call. Set the context point related to the data point you are validating and set the script to trigger from one of them for a start. Alternatively use a cron timer setting set to 15 seconds. Fox
  • General discussion for Mango Automation

    428 Topics
    2k Posts
    No new posts.
  • For question and help with installing Mango Automation

    128 Topics
    735 Posts
    No new posts.
  • An area for professional brewers to learn how to use the Brewers Dashboard System based on the Mango Automation software.

    10 Topics
    26 Posts
    No new posts.
  • Discussions and help with the Mango Embedded Hardware

    71 Topics
    472 Posts
    No new posts.