@robertkohl125 did you ever encounter this when/while installing and/or resetting the MineOS web ui?
https://i.imgur.com/IabgNfG.png
I’m currently doing some testing now and is what I was referring to previously
Edit 1: nodejs 4 does not have this looping problem, though I did catch a portion of it asking for nodejs version greater than or equal to 5, which is the version that my site had previously shown before I updated it to match the version 8 that the official wiki uses/shows. Nodejs 4’s installer though now says to use nodejs 8 or nodejs 10, though nodejs 8 has that looping problem (I’ve not tried changing permissions or anything and am using snapshots currently to make life easier for testing).
https://i.imgur.com/OlsZWTn.jpg
Edit 2: Nodejs 10 also does not have that looping issue however it does fail:
https://i.imgur.com/gVPp0Il.png
After rebooting the system (after the failure) the web ui does launch and all however is not functional;
@robertkohl125 I imagine this is probably what your web ui looks like in it’s current state:
https://i.imgur.com/mffMVhN.jpg
Simple solution for now for the time being would be reverting back to using nodejs 4 or maybe nodejs 5; I’ll try nodejs 5 and report back on whether it works or not. @hexparrot
Edit 3: Nodejs 5 also works just fine, don’t really know what the differences between nodejs 4 vs nodejs 5 are so I can’t really recommend one over the other, that should be @hexparrot’s call. Nodejs4 I believe was the previous “LTS” release and I think it had at one point or at some point recommended v5 users move/switch to v4 when it came to new installations, but other than that can’t really tell without looking more into nodejs itself.
https://i.imgur.com/Zrtu4aK.jpg
Edit 4: Alright, I’m officially done here testing and all, I also just did a little more research into the NodeJS versioning and all and would have to say that I’d recommend going with NodeJS 4 over NodeJS 5 based on my findings. Using the official installation wiki here for Ubuntu 16.04 LTS you can follow those steps, replacing/substituting the setup_8.x entry for nodejs v8 back again instead to setup_4.x for nodejs v4 though you may have to completely remove any/all traces of ever having nodejs installed first, and then once you’re done and you’ve got nodejs v4 installed you can follow the wiki here for resetting the web ui in order to fully fix/resolve this altogether.