clb92

Yes, I'm having this issue too now. No problems two days ago, but it takes forever to start up now. I'm seeing it stuck exactly like in your first screenshot. Haven't waited long enough for it to reach "MineOS-node started" yet. I'm actually looking for an alternative to MineOS, as it also no longer has PaperMC profiles built-in anyway.

It's already in the issue tracker, it seems: https://github.com/hexparrot/mineos-node/issues/446

Yeah, I just noticed that too a few days ago when my server wouldn't run, and I couldn't find PaperMC anywhere. I just manually downloaded the .jar, put it in the mineos/games/servers/SERVERNAME/ folder and selected it in the dropdown "Change runnable .jar to:" and it seems to work for now.

It simply means that you are already using that port (8443) for something else, maybe another docker or another program running on the server. A port can only be used by one program at a time. If you have multiple dockers that use this port, only one of them can run at a time.

My temporary solution has been to just delete the existing symlink (pointing to java 1.8 by default) rm /usr/sbin/java and create the new symlink to newer included java binary ls -s /usr/lib/jvm/java-11-openjdk/bin/java /usr/sbin/java to point to the newer included java 11 instead. I'm only running a single PaperMC server, but so far it works fine. This solution probably doesn't persist through reboots, so you'll likely need to redo it either if you reboot or update this container.

The solution should be to update Unraid, or if that's not possible, install a newer version of 'runc' yourself (search and you'll find a how-to somewhere around here by binhex)

Are you accessing the web interface through a reverse proxy or something that maybe adds HSTS?

I'm sure someone will post it.

Do not run it as privileged. It's a big security risk. Binhex posted in the MinecraftServer (not MineOS) support thread that it can be temporarily fixed with a simple command (after every reboot), until it's permanently fixed in a future Unraid update:

Unfortunately, it did not work. Same error as earlier.

Has not been resolved yet. If it works for you now, just stay on that version for a while longer. Binhex made a new test image of binhex-minecraftserver (not MineOS) yesterday and is waiting for feedback, since he's not able to reproduce the issue himself.

Oh, so that an image from before whatever changed and ruined things?

OMG, based on your post here I guessed that you'd have an "arch-mineos-node:test" image too, so I tried it (and remembered to turn off privileged) and it seems to work for me! What was the issue?!

I just tried making that change to my template XML, but it changes nothing for me. Same error as before. Am I reading it right that you needed both this XML change AND to run as privileged to get it working? If so, that's strange. Simply running as privileged without the XML change works for me (but obviously that's a terrible solution!)

I found this itzg/docker-minecraft-server issue where the title alone caught my attention. Could it be related, or am I just grasping at straws?