Updated Web-UI got broken

I attempted to update the Web-UI today and after logging in, the site partially loaded. It appears all the sidebar components are all jumbled into one page. The main frame has code, and is partially loaded with elements.
The servers set to run on reboots still load, but can’t be controlled.
Tested in IE, Safari and Chrome.
Can’t even see the commit version number in the username drop-down.

Saw the post on how to roll back the commit, but appears there is a side of caution to that.

No real risks to resetting the scripts.

I attempted the reset commands twice and a reboot, but still is not loading correctly. Also attempted to re-update the commit, but still the same.
I did run the commands as root.
This is what it looks like

1 Like

I’ve got the same issue
I’ve followed the update section but nothing …

What I need is the contents of /var/log/mineos.log–all issues should show up there, so if you can share that, it should be easier to drill down.

Here’s the link to my log file

No apparent errors in the log. Can you successfully log into the webui using a non-mobile browser?

If you’re able to open it from the desktop (even with the same issue persisting), can you verify if the javascript console of the browser reports errors?

Both IE and Chrome give the similar look as the mobile browser.
Here is the JavaScipt Console output.

DOM7011: The code on this page disabled back and forward caching. For more information, see: http://go.microsoft.com/fwlink/?LinkID=291337
HTML1300: Navigation occurred.
HTML1509: Unmatched end tag.
index.html (618,53)
HTML1512: Unmatched end tag.
index.html (1119,65)
HTML1509: Unmatched end tag.
index.html (1289,53)
HTML1509: Unmatched end tag.
index.html (1334,53)
HTML1509: Unmatched end tag.
index.html (1352,53)
SCRIPT5022: [$injector:modulerr] http://errors.angularjs.org/1.7.9/$injector/modulerr?p0=mineos&p1=Error%3A%20[%24injector%3Amodulerr]%20http%3A%2F%2Ferrors.angularjs.org%2F1.7.9%2F%24injector%2Fmodulerr%3Fp0%3DngSanitize%26p1%3DTypeError%3A%20Object%20expected%0A%20%20%20at%20k%20(https%3A%2F%2F192.168.0.20%3A8443%2Fangular-sanitize%2Fangular-sanitize.min.js%3A6%3A255)%0A%20%20%20at%20Anonymous%20function%20(https%3A%2F%2F192.168.0.20%3A8443%2Fangular-sanitize%2Fangular-sanitize.min.js%3A12%3A1)%0A%20%20%20at%20instantiate%20(https%3A%2F%2F192.168.0.20%3A8443%2Fangular%2Fangular.min.js%3A45%3A156)%0A%20%20%20at%20c%20(https%3A%2F%2F192.168.0.20%3A8443%2Fangular%2Fangular.min.js%3A42%3A51)%0A%20%20%20at%20Anonymous%20function%20(https%3A%2F%2F192.168.0.20%3A8443%2Fangular%2Fangular.min.js%3A41%3A495)%0A%20%20%20at%20d%20(https%3A%2F%2F192.168.0.20%3A8443%2Fangular%2Fangular.min.js%3A42%3A435)%0A%20%20%20at%20Anonymous%20function%20(https%3A%2F%2F192.168.0.20%3A8443%2Fangular%2Fangular.min.js%3A43%3A63)%0A%20%20%20at%20r%20(https%3A%2F%2F192.168.0.20%3A8443%2Fangular%2Fangular.min.js%3A8%3A74)%0A%20%20%20at%20g%20(https%3A%2F%2F192.168.0.20%3A8443%2Fangular%2Fangular.min.js%3A42%3A344)%0A%20%20%20at%20Anonymous%20function%20(https%3A%2F%2F192.168.0.20%3A8443%2Fangular%2Fangular.min.js%3A43%3A16) %20%20%20at%20Anonymous%20function%20(https%3A%2F%2F192.168.0.20%3A8443%2Fangular%2Fangular.min.js%3A43%3A175) %20%20%20at%20r%20(https%3A%2F%2F192.168.0.20%3A8443%2Fangular%2Fangular.min.js%3A8%3A74) %20%20%20at%20g%20(https%3A%2F%2F192.168.0.20%3A8443%2Fangular%2Fangular.min.js%3A42%3A344) %20%20%20at%20Anonymous%20function%20(https%3A%2F%2F192.168.0.20%3A8443%2Fangular%2Fangular.min.js%3A43%3A16) %20%20%20at%20r%20(https%3A%2F%2F192.168.0.20%3A8443%2Fangular%2Fangular.min.js%3A8%3A74) %20%20%20at%20g%20(https%3A%2F%2F192.168.0.20%3A8443%2Fangular%2Fangular.min.js%3A42%3A344) %20%20%20at%20fb%20(https%3A%2F%2F192.168.0.20%3A8443%2Fangular%2Fangular.min.js%3A46%3A454) %20%20%20at%20c%20(https%3A%2F%2F192.168.0.20%3A8443%2Fangular%2Fangular.min.js%3A22%3A55) %20%20%20at%20Uc%20(https%3A%2F%2F192.168.0.20%3A8443%2Fangular%2Fangular.min.js%3A22%3A363) %20%20%20at%20Ae%20(https%3A%2F%2F192.168.0.20%3A8443%2Fangular%2Fangular.min.js%3A21%3A45)
angular.js (5062,9)

Should I scrap the build and restore from a backup? I can access the servers and transfer them by sFTP.

Think of MineOS as, say, a single program in a location /usr/games/minecraft, like how Microsoft Office exists.

If Word stops working, you don’t need to scrap the entire build. MineOS is just one program that runs alongside hundreds of others that make up your Linux Distro. As is always the case, scrapping a build is never what I recommend, because a) it is overkill and b) discourages seeking out the actual problem and finding the solution.

That said, do whatever you feel helps get your server back up and running properly most quickly, even if that is scrapping it.

I got the new ISO download and running. All seam fine. Since this version is running on Stretch, and I was on Jessie that it could have been an incompatible version of Java.

Reading other posts with similar issues lead me to that conclusion. And when I attempted to update Linux, the repositories were also broken.