Fantastic, thank you very much! I'll pass this along to the developers and let you know if we run into any issues. I appreciate the quick help.

Re: Password Expiry and Complexity

We're working to deploy Mango in environments where customers require an enforced minimum password complexity. The reference topic above mentions the back-end supports it but it's not yet configurable. I checked our Mango settings and indeed see a setting to expire passwords, but there's nothing for enforced complexity.

Is enforced complexity still in the pipeline? Is there a way to manually set enforcement through the back-end if the GUI won't support configuration for a while?

@phildunlap,
I tried JDBC URL jdbc:h2:./databases/mah2-199 and still get a database not found error. While we were able to solve the topic issue through the legacy UI, let me know if you still want to chase this down to figure out why we can't connect to the DB through the H2 console.

@Jared-Wiltshire,
Bingo! That got us into the legacy UI. It seems obvious now in hindsight.

I executed your SQL command to purge the changes, and the main GUI is back online.

Thanks for the help!

It looks like if I try to manually point to a legacy UI url, or navigate directly to /sqlConsole.shtml, it redirects me back to /ui/login, which is where it does is show me the error output. I should note that we just updated the modules before this happened, and it appears most or all of the legacy UI has been migrated to the new UI?

I also tried to work through the web based H2 client, and I can get the client up, but it errors "/opt/mango/databases/mah2 not found." Note that username and password in env.preferences and the console are both blank.

I also tried running your sql command from a local terminal, but am not having luck getting a local H2 console to run.

I'm working on applying corporate theming to a MangoHTS, which involved applying a custom mangoUI-settings config in the JSON Store. Unfortunately, I missed some typos on a copy/paste, and now the system hangs on startup with cascading errors:

Error bootstrapping Mango UI app: [$injector:modulerr] Failed to instantiate module maUiBootstrap due to: Missing colors 100, 200, 300, 400, 500, 600, 700, 800, 900, A100, A200, A400 in palette primaryTeal! v@http://166.148.232.96:8081/modules/mangoUI/web/mangoUi~ngMango.js?v=735aeb62157e97f73c30:77:67161 definePalette@http://166.148.232.96:8081/modules/mangoUI/web/mangoUi~ngMango.js?v=735aeb62157e97f73c30:77:66478 h/this.registerThemes@http://166.148.232.96:8081/modules/mangoUI/web/mangoUi.js?v=91d25ee92ad5356e3e50:1:171852 h/this.setUiSettings@http://166.148.232.96:8081/modules/mangoUI/web/mangoUi.js?v=91d25ee92ad5356e3e50:1:171693 1987/</<@http://166.148.232.96:8081/modules/mangoUI/web/mangoUi.js?v=91d25ee92ad5356e3e50:1:227854 invoke@http://166.148.232.96:8081/modules/mangoUI/web/mangoUi~ngMango~ngMangoServices.js?v=410f3b6e2f95e70c04f3:78:26209 r@http://166.148.232.96:8081/modules/mangoUI/web/mangoUi~ngMango~ngMangoServices.js?v=410f3b6e2f95e70c04f3:78:25378 f/<@http://166.148.232.96:8081/modules/mangoUI/web/mangoUi~ngMango~ngMangoServices.js?v=410f3b6e2f95e70c04f3:78:25003 y@http://166.148.232.96:8081/modules/mangoUI/web/mangoUi~ngMango~ngMangoServices.js?v=410f3b6e2f95e70c04f3:78:1537 f@http://166.148.232.96:8081/modules/mangoUI/web/mangoUi~ngMango~ngMangoServices.js?v=410f3b6e2f95e70c04f3:78:24864 Kt@http://166.148.232.96:8081/modules/mangoUI/web/mangoUi~ngMango~ngMangoServices.js?v=410f3b6e2f95e70c04f3:78:24200 o@http://166.148.232.96:8081/modules/mangoUI/web/mangoUi~ngMango~ngMangoServices.js?v=410f3b6e2f95e70c04f3:78:10352 we@http://166.148.232.96:8081/modules/mangoUI/web/mangoUi~ngMango~ngMangoServices.js?v=410f3b6e2f95e70c04f3:78:10665 1987/<@http://166.148.232.96:8081/modules/mangoUI/web/mangoUi.js?v=91d25ee92ad5356e3e50:1:227967 https://errors.angularjs.org/1.7.8/$injector/modulerr?p0=maUiBootstrap&p1=Missing%20colors%20100%2C%20200%2C%20300%2C%20400%2C%20500%2C%20600%2C%20700%2C%20800%2C%20900%2C%20A100%2C%20A200%2C%20A400%20in%20palette%20primaryTeal!%0Av%40http%3A%2F%2F166.148.232.96%3A8081%2Fmodules%2FmangoUI%2Fweb%2FmangoUi~ngMango.js%3Fv%3D735aeb62157e97f73c30%3A77%3A67161%0AdefinePalette%40http%3A%2F%2F166.148.232.96%3A8081%2Fmodules%2FmangoUI%2Fweb%2FmangoUi~ngMango.js%3Fv%3D735aeb62157e97f73c30%3A77%3A66478%0Ah%2Fthis.registerThemes%40http%3A%2F%2F166.148.232.96%3A8081%2Fmodules%2FmangoUI%2Fweb%2FmangoUi.js%3Fv%3D91d25ee92ad5356e3e50%3A1%3A171852%0Ah%2Fthis.setUiSettings%40http%3A%2F%2F166.148.232.96%3A8081%2Fmodules%2FmangoUI%2Fweb%2FmangoUi.js%3Fv%3D91d25ee92ad5356e3e50%3A1%3A171693%0A1987%2F%3C%2F%3C%40http%3A%2F%2F166.148.232.96%3A8081%2Fmodules%2FmangoUI%2Fweb%2FmangoUi.js%3Fv%3D91d25ee92ad5356e3e50%3A1%3A227854%0Ainvoke%40http%3A%2F%2F166.148.232.96%3A8081%2Fmodules%2FmangoUI%2Fweb%2FmangoUi~ngMango~ngMangoServices.js%3Fv%3D410f3b6e2f95e70c04f3%3A78%3A26209%0Ar%40http%3A%2F%2F166.148.232.96%3A8081%2Fmodules%2FmangoUI%2Fweb%2FmangoUi~ngMango~ngMangoServices.js%3Fv%3D410f3b6e2f95e70c04f3%3A78%3A25378%0Af%2F%3C%40http%3A%2F%2F166.148.232.96%3A8081%2Fmodules%2FmangoUI%2Fweb%2FmangoUi~ngMango~ngMangoServices.js%3Fv%3D410f3b6e2f95e70c04f3%3A78%3A25003%0Ay%40http%3A%2F%2F166.148.232.96%3A8081%2Fmodules%2FmangoUI%2Fweb%2FmangoUi~ngMango~ngMangoServices.js%3Fv%3D410f3b6e2f95e70c04f3%3A78%3A1537%0Af%40http%3A%2F%2F166.148.232.96%3A8081%2Fmodules%2FmangoUI%2Fweb%2FmangoUi~ngMango~ngMangoServices.js%3Fv%3D410f3b6e2f95e70c04f3%3A78%3A24864%0AKt%40http%3A%2F%2F166.148.232.96%3A8081%2Fmodules%2FmangoUI%2Fweb%2FmangoUi~ngMango~ngMangoServices.js%3Fv%3D410f3b6e2f95e70c04f3%3A78%3A24200%0Ao%40http%3A%2F%2F166.148.232.96%3A8081%2Fmodules%2FmangoUI%2Fweb%2FmangoUi~ngMango~ngMangoServices.js%3Fv%3D410f3b6e2f95e70c04f3%3A78%3A10352%0Awe%40http%3A%2F%2F166.148.232.96%3A8081%2Fmodules%2FmangoUI%2Fweb%2FmangoUi~ngMango~ngMangoServices.js%3Fv%3D410f3b6e2f95e70c04f3%3A78%3A10665%0A1987%2F%3C%40http%3A%2F%2F166.148.232.96%3A8081%2Fmodules%2FmangoUI%2Fweb%2FmangoUi.js%3Fv%3D91d25ee92ad5356e3e50%3A1%3A227967%0A
Show stack trace

I'm working under the assumption that the best course is to undo the applied configuration. I can't get into the Mango UI to get back to the JSON Store. I can SSH into the device and have been researching and scouring the file structure but cannot locate where the mangoUI-settings information is stored.

Is this something that's stored in plain text somewhere that I can get to and wipe out? Is there a better option than wiping the device and starting over?

Thanks for the help.

Phil,

The 5V power supply was being used for the barrel jack directly on the single board computer (SBC) in the ES. The first unit we received from IAS actually came with a similar power supply, and we've been using them for powering ES devices on the lab bench while we configure them.

Moving forward, we're going to switch to using the screw terminal block power input with a compatible power source.

I believe we've isolated the cause of our problems to the new power supply. It's a 5V 2A power supply, which should be sufficient per the SBC's spec, but I suspect that it may be a switching supply or we're pulling more load than expected or some other issue is causing it to fault.

Moving forward, I'd prefer to power our device through the screw terminal inputs. I have some more detailed technical questions on that front, but I'll reach out over email since this might be beyond the scope of the forums.

Thanks for all the responses. I'm out of the office the rest of this week, but can try to debug when I'm back on Tuesday.

What I can tell you at the moment is...

I'm accessing the interface over the LAN. It was working prior to importing the JSON config, and nothing about the setup changed on the browser end.

I tried SSH with port 2222 using PuTTY. It would try to establish a connection, and Mango ES would actively refuse. Sometimes, if I caught it at the right time, I could establish a connection and log in, but after 10-15 seconds, it would stop responding.

The system crash was that, when refreshing the browser, all lights on the device would turn off except for power, then the lights would go through the normal bootup pattern, finishing with two or three flashes of the three aux lights. During this time, the web interface would show boot up output, before going back to the spinning ring. I can check the ma.log when I'm back in the office.

I did rename/delete the individual H2 database and it created a new one, but with no effect. I'll check it out again when I'm back.

It seems I spoke too soon. After configuring the device a bit (adding users, etc), updating modules, and restarting, it's back to misbehaving. The GUI load circle spins indefinitely, then when refreshing the page, the device crashes and repeat.

Well, as seems to be my luck on this forum, the moment I posted, I tried to refresh the device again after it's been idling for a good 15 minutes, and now it seems to be working again. The GUI loaded okay and I'm able to login, and it's behaving as though it's a fresh install as expected after clearing the H2 database.

Not sure what was going on, but I'm not going to try the config import again for now since we critically need this device working tomorrow. I'm just going to manually set it up.

Either way, if I didn't use the recommended method for migrating configuration between devices, and there's a suggested way to do it, I'm all ears. Otherwise, I'm curious if there's a theory on why the GUI became unusable after importing a configuration JSON.