January 25, 201610 yr Pretty new to unRAID and dockers here and was hopping for some guidance. I found hernandito’s mineos (https://github.com/hernandito/docker-mineos) but it would not load in unRAID for me. Rather than troubleshooting, I went looking for alternatives. I found (https://github.com/hexparrot/mineos-node) which conveniently had a Dockerfile created 14 days ago by mjeries (https://github.com/mjeries/mineos-node). (Using Community Apps to ‘template’ it) This one did download, setup, appeared to complete, and it even started. Not knowing what arguments/configurations to use, I just basic settings for its install. Once it was running, I saw (through the unRAID log) that MineOS was bound to 0.0.0.0:8443. At this point is where I could not connect to the web config GUI. 192.168.10.110 is the unRAID host IP. Any recommendations for troubleshooting this? I really have no idea where to start. Could it be a bad Community Apps dockerfile template conversion? Do I need to get into the docker install/config for MineOS and make some changes? If so, where/how? My use-case will be a locally available MC server for several computers to connect to. In the future I may expand the availability to the public through my firewall, but I will have to learn a bit more about MC security.
January 25, 201610 yr Once it was running, I saw (through the unRAID log) that MineOS was bound to 0.0.0.0:8443. At this point is where I could not connect to the web config GUI. 192.168.10.110 is the unRAID host IP. Pretty sure MineOS defaults to SSL, did you try https://192.168.10.110:8443? Also, you will need to create port mappings for the server itself, which are normally 25565 or something like that. You can customize the ports if you want, but that means you will need to specify the ports in the client as well (not that that is a bad thing).
January 25, 201610 yr Author You were right! I just assumed that the webUI selection from the docker app would have the right url. Enable advanced view, and set Additional Fields: WebUI: (from: http://[iP]:[PORT:8443]) to https://[iP]:[PORT:8443] fixed it. Now on to logon problems. tried using PASSWORD variable to set a password on the default minecraft user. Browsed around the net a bit and tried various combinations of 'mc' 'root' 'minecraft' with lots of different passwords. Found something odd, if I try 'root' with the password I specify in the variables section, MineOS immediately goes offline/stops. Same thing happens if I remove the password variable and try to guess a root password. root without a password does not cause this behavior. Any chance someone wants to take a crack at properly unraiding the MineOS distro?
January 26, 201610 yr Author Well, I took another look at the dockerfile that started all this for me... Looks like I missed this line: RUN useradd mc; \ echo "mc:admin" | chpasswd When I get home I will try mc. On this line, does it set password to 'admin' or 'chpasswd'? It was admin. Had one more problem in that I set an IP when configuring the server, now its all up and running. Thanks for the help!
Archived
This topic is now archived and is closed to further replies.