Mango dashboards running as custom pages could fail to reconnect after a Mango server restart. The confirmed cause was not the Raspberry Pi or Chromium browser: custom pages that did not inherit from the dashboard state lacked the reconnect behavior. Dashboards v3.2.4 includes the fix.
Identify the affected configuration
The reported system used Chromium on Raspberry Pi devices running fullpageOS, with auto-login enabled. The failure also appeared during a Windows 7 test with Chrome and Firefox: after Mango restarted, open screens neither displayed the bottom notification nor reconnected when the server returned.
| Component | Reported value | Diagnostic relevance |
|---|---|---|
| Mango core | 2.7.12 build 481 | Server version in the affected installation |
| mangoApi | 1.1.7 | API module version in the affected installation |
| Dashboards | 3.2.2 with a prior patch | Version present when the failure was investigated |
| Page structure | Custom pages without dashboard state inheritance or toolbars |
Confirmed trigger for the reconnect defect |
| Corrected release | Dashboards v3.2.4 | Release containing the reconnect fix |
Correct the reconnect failure
- Update the Dashboards module to v3.2.4.
- Delete any copy of the earlier reconnect patch from the overrides area. Leaving an obsolete override in place could prevent the installed module code from being used.
- Clear the browser cache on each dashboard client so Chromium, Chrome, or Firefox loads the corrected dashboard files.
- Reload the custom dashboard and confirm that auto-login still opens the intended page.
Verify recovery after a restart
Keep the custom dashboard open, restart Mango, and wait for the server to return. Pass the test only if the existing page reconnects without restarting the Raspberry Pi or client computer. The reported installation successfully reconnected after applying the correction.
Do not use the presence of the bottom notification as the sole acceptance criterion. In the failed state, the notification was absent, and its later disappearance appeared related to restored reconnect behavior rather than a separate notification change.
FAQ
Why does my Mango dashboard not reconnect after a server restart?
For the reported configuration, the cause was a custom page that did not inherit from the dashboard state and had no toolbar. That page structure bypassed the reconnect behavior in Dashboards v3.2.2.
Which Mango Dashboards version fixes custom-page reconnection?
Dashboards v3.2.4 includes the fix. After updating, remove the earlier override patch and clear every dashboard browser's cache.
How do I test Mango dashboard reconnection?
Open the custom dashboard, restart Mango, and confirm that the existing page reconnects when the server returns. The test fails if recovering the display requires restarting the Raspberry Pi or browser computer.