I had a working MineOS setup on Ubuntu, but with some software issues and drawbacks with the system (especially the bloat) I decided to move my server over to Arch. The pleasantries of systemd and having a lean system were well worth a few hours of backups (originally I had just used Ubuntu because I was lazy). However, there is one issue that completely hinders me from using MineOS.
Now, I never came across this on my old setup, but right away with the new one I come across this when I try to connect to the WebUI (after accepting the SSL certificate):
Secure Connection Failed
An error occurred during a connection to [IP Address]:8080. SSL received a record that exceeded the maximum permissible length. (Error code: ssl_error_rx_record_too_long)
The page you are trying to view cannot be shown because the authenticity of the received data could not be verified.
Please contact the website owners to inform them of this problem.
Of course, my first thought was to clear the cert in my browser and try again. That did not work (on various operating systems and browsers, not to mention, even one of my admins tried and failed the same). Generating new certs has done nothing as well. I can also clarify that I am set to use HTTPS, as I have not changed a single line in the mineos.conf. There doesn’t seem to be anything wrong here:
server.socket_host = “0.0.0.0”
server.socket_port = 8080
server.commit_delay = 10
log.error_file = “/var/log/mineos.log”
server.ssl_module = “builtin”
server.ssl_certificate = “/etc/ssl/certs/mineos.crt”
server.ssl_private_key = “/etc/ssl/certs/mineos.key”
misc.server_as_daemon = True
misc.pid_file = “/var/run/mineos.pid”
misc.require_https = True
misc.base_directory = “/var/games/minecraft”
misc.localization = “en”
webui.mask_password = False
As noted in this unresolved post, it is questioned as to whether the person is using HTTPS. Just as their mineos.log does, mine says the WebUI is started on HTTP. Here is an excerpt:
[26/Aug/2014:02:48:27] ENGINE Bus STARTING
[26/Aug/2014:02:48:27] ENGINE Forking once.
[26/Aug/2014:02:48:27] ENGINE Daemonized to PID: 636
[26/Aug/2014:02:48:27] ENGINE Forking twice.
[26/Aug/2014:02:48:27] ENGINE Started monitor thread ‘_TimeoutMonitor’.
[26/Aug/2014:02:48:27] ENGINE PID 636 written to ‘/var/run/mineos.pid’.
[26/Aug/2014:02:48:27] ENGINE Started monitor thread ‘Monitor’.
[26/Aug/2014:02:48:27] ENGINE Started monitor thread ‘Autoreloader’.
[26/Aug/2014:02:48:27] ENGINE Serving on http://0.0.0.0:8080
[26/Aug/2014:02:48:27] ENGINE Bus STARTED
Naturally, this leads me to believe that a recent release has botched something in regards to the SSL, as my previous working install was from March and this latest install (from yesterday as well as repeated reinstalls) have only resulted in this error. Is it possible I am missing a dependency or something of that nature? I am sure the ports are open as I have Minecraft and Murmur running right now, despite this (I just manually launched the server in the meantime). If the answer is unknown, are there any recommended alternatives to MineOS I can use for now?
For further clarification, the MineOS is on Arch Linux with kernel x86_64 Linux 3.16.1-1-ARCH, no Xorg installed. MineOS was installed by hand using the guide.
I hope this can be resolved, thank you.