The problem I’m seeing here in the log seems to be a connectivity issue, moreso than a setup issue of the webui itself. We can verify my suspicion with a few commands:
1) Is the process running?
# supervisorctl status mineos
2) Is the webui serving?
# netstat -ntlp
Active Internet connections (only servers)
Proto Recv-Q Send-Q Local Address Foreign Address State PID/Program name
tcp 0 0 127.0.0.53:53 0.0.0.0:* LISTEN 633/systemd-resolve
tcp 0 0 0.0.0.0:22 0.0.0.0:* LISTEN 800/sshd
tcp 0 0 0.0.0.0:8443 0.0.0.0:* LISTEN 9007/mineos
tcp6 0 0 :::22 :::* LISTEN 800/sshd
# telnet 0.0.0.0 8443
Trying 0.0.0.0...
Connected to 0.0.0.0.
Escape character is '^]'.
^]
If it says “Connected to 0.0.0.0”, then the webui is actually running. There’s no components with the webui that failed to install, and the npm modules reflecting “WARN” are also only warnings, not errors.
Let me know if these tests all report back what we’re expecting. If our tests report the same, it’s a connectivity issue external to the webui we need to address.
With that said, I have just started up my own Welcome to Ubuntu 18.04.4 LTS (GNU/Linux 4.15.0-101-generic x86_64) Virtual machine, and it worked without issue.
One thing I noticed is that I used the wikipage for Ubuntu + systemd (the wikipage indicated for Ubuntu 16 and later).
I don’t think this is the cause of the problem, of course, but for thoroughness I’m including that detail, since it just worked as expected, no deviations from the instructions.
Edit: Just brought up a new vm to use the supervisord instructions, and it also worked without issue.
With regards to why you’re getting all the console errors, my immediate suspicion is that the webui is actually cached in your browser, so it knows enough to know it’s failing to connect to the webui backend, which is why you can see all the parts of the screen that are not fed by the webui service.
Each attempt to the webui after a restart should be the login page, after all.