I just installed Mineos on a new installation of Ubuntu Server 18.04 and accessing the WebUI from my computer it only partially loads.
This is what it looks like https://drive.google.com/file/d/1_sLXH43-QWgb_kTJEF9yOv8s4z8Ss-pu/view?usp=sharing
Can anyone help me with this?
This is the same thing that I’m getting on my WebUI. Please see my post here: Updated Web-UI got broken
And I have attempted to run the reset commands posted in that thread as well, with no luck. I have not yet scrapped my server and restored. But your post may have confirmed that I would still run into the same issue. I will attempt just the same, as the commit is an older version on the backup.
As is the case all the time, seeing the webui not working isn’t sufficient for me to diagnose.
Share with me error output.
Whether its the error output from your browser’s javascript console, or the /var/log/mineos.log file, I need something that tells me what the problem is.
In the linked thread, I had supplied both the javascript console error and the mineos.log file. I would be interested if Hunter gets the same error messages in both.
Does this help?
Javascript console:https://drive.google.com/file/d/1zr9wTOvlaFdrX9mZOdETg8OxCQ8bsASU/view?usp=sharing]
mineos.log:https://drive.google.com/file/d/1VnuVCyhl9DOYlJ-QiqqLclJLSRg8SZ5l/view?usp=sharing
According to your javascript console:
Certificate error: net::ERR_CERT_AUTHORITY_INVALID
MineOS uses a self-signed certificate to allow HTTPS, but one of the side-effects of self-signed certs is that browsers need deliberate approval to use them (because by default, it distrusts them).
According to your console error, you’re getting angular issues.
According to the console error, the browser is not loading the angular javascript sources because of the cert error. It suggests to me that the security part of Chrome is unhappy here:
- is the system time wrong on your workstation?
- is the system time wrong on your MineOS host?
- did you change any security-related functionality to reject self-signed certificates?
- are you experiencing a browser related problem from non-mineos related errors?
Regarding #4, look at the first errors you’re getting: “Devtools failed to load sourcemap” and this is regarding a chrome-extension “ERR_UNKONWN_URL_SCHEME”.
It seems like the browser might benefit from a reset to default settings and then a gradual locking down as needed. If you don’t want to reset it, can you confirm the same issues happen on a different browser?
Having the same issue, clean install of ubuntu-18.04.4-live-server-amd64, actually tried it twice with the same result.
Not sure if it is notable, but I had some errors of depreciated files during the install, after running “npm install --unsafe-perm”
npm WARN deprecated node-uuid@1.4.8: Use uuid module instead
npm WARN deprecated request@2.88.2: request has been deprecated, see https://github.com/request/request/issues/3142
npm WARN deprecated code@1.5.0: This version has been deprecated in accordance with the hapi support policy (hapi.im/support). Please upgrade to the latest version to get the best features, bug fixes, and security patches. If you are unable to upgrade at this time, paid support is available for older versions (hapi.im/commercial).
npm WARN deprecated hoek@2.16.3: This version has been deprecated in accordance with the hapi support policy (hapi.im/support). Please upgrade to the latest version to get the best features, bug fixes, and security patches. If you are unable to upgrade at this time, paid support is available for older versions (hapi.im/commercial).
npm WARN deprecated json3@3.2.6: Please use the native JSON object instead of JSON 3
npm WARN deprecated json3@3.3.2: Please use the native JSON object instead of JSON 3
npm WARN deprecated natives@1.1.6: This module relies on Node.js’s internals and will break at some point. Do not use it, and update to graceful-fs@4.x.
npm WARN deprecated nodeunit@0.11.3: you are strongly encouraged to use other testing options
Here is the Mineos screen with the java console in Chrome. I added the server IP as a trusted site in Java, so I don’t see any certificate errors.
The Firefox console is a little different:
Not really anything useful in the mineos log, that I can see:
{“level”:“info”,“message”:“Starting up server, using commit: 83c095f fixed issue: gracefully handle symlink servers that point nowhere\n”,“timestamp”:“2020-06-06T05:14:25.682Z”}
{“level”:“info”,“message”:“Starting up server, using commit: 83c095f fixed issue: gracefully handle symlink servers that point nowhere\n”,“timestamp”:“2020-06-06T05:16:36.757Z”}
{“level”:“info”,“message”:“Starting up server, using commit: 83c095f fixed issue: gracefully handle symlink servers that point nowhere\n”,“timestamp”:“2020-06-06T05:23:09.084Z”}
{“level”:“info”,“message”:“Starting up server, using commit: 83c095f fixed issue: gracefully handle symlink servers that point nowhere\n”,“timestamp”:“2020-06-06T06:00:56.501Z”}
{“level”:“info”,“message”:“Starting up server, using commit: 83c095f fixed issue: gracefully handle symlink servers that point nowhere\n”,“timestamp”:“2020-06-06T15:03:20.123Z”}
Any guidance would be greatly appreciated.
Thanks.
Can you check which version of Java is installed and try to update? I don’t remember if node-js requires JDK or not.
java -version
openjdk version “11.0.7” 2020-04-14
OpenJDK Runtime Environment (build 11.0.7+10-post-Ubuntu-2ubuntu218.04)
OpenJDK 64-Bit Server VM (build 11.0.7+10-post-Ubuntu-2ubuntu218.04, mixed mode, sharing)
I spun up a server running Ubuntu 18.04 and installed the MineOS-nodejs. The webui looks fine, but the buttons don’t function at all. I tried to manually start in the terminal but no go there either. I also updated the commit and same. the Java version is the same as yours too. Changing the ownership didn’t help.
I might suggest setting up the server using the ISO process instead, if possible. Mine has been working fine since I upgraded to Stretch.
Run the ./reset_webui.sh script, because what your console seems to indicate is that there are more npm related issues that didn’t get copied over here to this thread.
After resetting, can you share /var/log/mineos.log in entirety? (or send the full thing to me here privately)
Didn’t seem to make any difference. Got a bunch of depreciated file errors again.
sudo ./reset_webui.sh
Script execution started on: Sun Jun 7 13:22:34 PDT 2020
Updating mineos-node repository…OK
Checking out master branch…Already on ‘master’
OK
Resetting directory to official contents…OK
npm WARN deprecated node-uuid@1.4.8: Use uuid module instead
npm WARN deprecated request@2.88.2: request has been deprecated, see https://git hub.com/request/request/issues/3142
npm WARN deprecated code@1.5.0: This version has been deprecated in accordance w ith the hapi support policy (hapi.im/support). Please upgrade to the latest vers ion to get the best features, bug fixes, and security patches. If you are unable to upgrade at this time, paid support is available for older versions (hapi.im/ commercial).
npm WARN deprecated hoek@2.16.3: This version has been deprecated in accordance with the hapi support policy (hapi.im/support). Please upgrade to the latest ver sion to get the best features, bug fixes, and security patches. If you are unabl e to upgrade at this time, paid support is available for older versions (hapi.im /commercial).
npm WARN deprecated json3@3.2.6: Please use the native JSON object instead of JS ON 3
npm WARN deprecated json3@3.3.2: Please use the native JSON object instead of JS ON 3
npm WARN deprecated natives@1.1.6: This module relies on Node.js’s internals and will break at some point. Do not use it, and update to graceful-fs@4.x.
npm WARN deprecated nodeunit@0.11.3: you are strongly encouraged to use other testing options
OK
Setting node javascript files to executable…OK
Script execution ended on: Sun Jun 7 13:23:12 PDT 2020
I bounced the service when I was done, with supervisorctl stop/start mineos,
Web UI looks the same, as does the Chrome java console, but the Firefox consloe has some new stuff.
Here is the log.
http://www.shedracing.net/imgmisc/forums/minecraft/mineos.log
Thanks.
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.
Service is running:
sudo supervisorctl status mineos
mineos RUNNING pid 6793, uptime 21:03:18
sudo 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 719/systemd-resolve
tcp 0 0 0.0.0.0:22 0.0.0.0:* LISTEN 1066/sshd
tcp 0 0 0.0.0.0:8443 0.0.0.0:* LISTEN 6793/node
tcp 0 0 0.0.0.0:445 0.0.0.0:* LISTEN 4289/smbd
tcp 0 0 0.0.0.0:139 0.0.0.0:* LISTEN 4289/smbd
tcp6 0 0 :::22 :::* LISTEN 1066/sshd
tcp6 0 0 :::445 :::* LISTEN 4289/smbd
tcp6 0 0 :::139 :::* LISTEN 4289/smbd
It is interesting that the PID reflected in the status query shows as “node” in the Netstat on my host, but in yours it shows as Mineos.
telnet 0.0.0.0 8443
Trying 0.0.0.0...
Connected to 0.0.0.0.
Escape character is '^]'.
To check the browser thing, I cleared my history/cache in Chrome, and reconnected and nothing changed, got the login screen, and once logged in the broken webUI screen. I do have to log in each time I restart the service.
Do I need to actually log in a root do get this to work? I did SUDO for every step.
Thanks.
Wait, could this be a firewall issue? the server is headless with no GUI, I am connecting to the console from a Windows PC.
Thanks
Alright, well, that’s good–also interesting. Let’s dig deeper.
Do you have a /var/log/mineos.auth.log?
It should indicate successful and failed attempts to the webui.
I am curious though why none of the successful attempts to authenticate have been indicated in the mineos.log file you mentioned. E
It certainly could, and I was far more inclined to think that was the issue originally, but you’re telling me it’s working enough to get you into the login prompt and it accepts the password. That tells me that the firewall seems less likely now–because 8443 seems to be working.
Ubuntu 18 for me also had a firewall enabled, but no restricting rules (all ALLOW/ACCEPT). SELinux was also off for me by default.
mineos.auth.log:
Sat Jun 06 2020 05:15:01 GMT+0000 (UTC) - success from: 192.168.30.7 user: tom
Sat Jun 06 2020 05:16:48 GMT+0000 (UTC) - success from: 192.168.30.7 user: tom
Sat Jun 06 2020 05:23:38 GMT+0000 (UTC) - success from: 192.168.30.7 user: tom
Sat Jun 06 2020 05:30:17 GMT+0000 (UTC) - success from: 192.168.30.7 user: tom
Fri Jun 05 2020 23:01:47 GMT-0700 (PDT) - success from: 192.168.30.7 user: tom
Fri Jun 05 2020 23:03:38 GMT-0700 (PDT) - success from: 192.168.30.7 user: tom
Fri Jun 05 2020 23:05:52 GMT-0700 (PDT) - success from: 192.168.30.7 user: tom
Sat Jun 06 2020 08:14:42 GMT-0700 (PDT) - success from: 192.168.30.7 user: tom
Sat Jun 06 2020 09:38:57 GMT-0700 (PDT) - success from: 192.168.30.7 user: tom
Sat Jun 06 2020 09:43:53 GMT-0700 (PDT) - failure from: 192.168.30.10 user: Tom
Sat Jun 06 2020 09:44:08 GMT-0700 (PDT) - success from: 192.168.30.10 user: tom
Sat Jun 06 2020 10:04:45 GMT-0700 (PDT) - success from: 192.168.30.7 user: tom
Sat Jun 06 2020 10:19:00 GMT-0700 (PDT) - success from: 192.168.30.7 user: tom
Sun Jun 07 2020 13:24:40 GMT-0700 (PDT) - success from: 192.168.30.7 user: tom
Sun Jun 07 2020 13:25:49 GMT-0700 (PDT) - success from: 192.168.30.7 user: tom
Mon Jun 08 2020 10:23:41 GMT-0700 (PDT) - success from: 192.168.30.7 user: tom
Mon Jun 08 2020 10:26:14 GMT-0700 (PDT) - success from: 192.168.30.7 user: tomCircling back to this, I have to time to try and get it going again.
When you got it working on the Ubuntu VM, did you reset the Root password and SU to it, or use Sudo?
Thanks.
If the Ubuntu install didn’t ask for the root password, then yes, you’ll need to reset the password and log in directly as root. I just used another tty to enter the commands.
su is just providing the root account password, which could be a security risk, in my opinion. But for these instructions, the root account should be used.