To summarize…what happens is I press “start” it shows as up for a few seconds - no logs get generated in the latest log file though, and then it changes to down. However, I can easily start the server by manually running the run.sh script in the command line.
The MineOS log file looks like this:
{“level”:“info”,“message”:“[NAME] 192.168.2.106 issued command : "start"”,“timestamp”:“2023-02-20T05:53:13.833Z”}
{“level”:“info”,“message”:“[NAME] received request "start"”,“timestamp”:“2023-02-20T05:53:13.833Z”}
{“level”:“error”,“message”:“[NAME] Error with get_increments true”,“timestamp”:“2023-02-20T05:53:15.456Z”}
And then something about not being able to ping the server a few times before going down. That’s all it says. It’s like the run.sh script isn’t even being triggered or something.
I am running this in a FreeBSD 13 Jail on a FreeNAS system. The set up I am trying to run is a mod pack that uses Java 17 with Forge 43.2.3.
I am able to run a vanilla Minecraft server just fine and start it with the WebUI, for some reason the WebUI doesn’t work with this Forge pack though. I am thinking maybe it is a weird permissions issue, but after playing around with the permissions, I can’t seem to figure it out.
Things I’ve tried:
- Re-making the server by importing the mod pack (no impact…same issues. Can run with commandline but Web UI doesn’t run)
- Chmod/Chown on the server files to ensure the right MineOS user/groups owns them (this didn’t seem to have any effect)
- Moving the -universal and -server Jar files to the base folder from the new Forge folder they added and selecting that as the “runnable Jar” (nothing happens, turns out these aren’t runnable without some additional commands that come from somewhere else now)
- Importing/Building the available Forge profiles and trying to run with those instead (they don’t match the version I need for this mod pack though so I didn’t expect this to work. Same results)
- Changing the server port (figured this might fix the ping error messages I was seeing, but when I tested with the Vanilla Minecraft server that actually comes up, I got the same ping errors.)
- Customizing the run.sh script to make it do something else (The WebUI overwrites this script when I press start and all my changes get erased, so this didn’t work)
This is the start command: @user_jvm_args.txt @libraries/net/minecraftforge/forge/1.19.2-43.2.3/unix_args.txt nogui
The selected runnable profile is forge-1.19.2-43.2.3-installer.jar
ram max is 8G, min is 2G
Basically all of the other server settings are default besides the seed, the port, the MOTD, and the world name.
Because it is actually running the log files will come through live in the WebUI, the server just shows as down and no stats come through. Clearly it is running correctly, the WebUI just doesn’t work. People can connect to it remotely and play just fine, but I want to monitor it with MineOS.
Anyone have any advice or anything else to try? I am not really sure what to do. I’m at wits end…I’ve spent 10+ hours on this. I’ve used MineOS for years before this and really don’t want to rebuild. I’ve read dozens of “clicking start does nothing” threads and none of them seem to help me so in desperation I’ve decided to make a new post.
Maybe I need to check some of the other FreeBSD Jail log files. I checked the MineOS and system one, and nothing came up though.