Goobaroo

@GonjaTThat is because they release pretty much daily, and there was a nation wide internet outage that prevented me from doing anything. But it should be caught up now.

@DarthLlama It seems to be an upgrade issue. Just delete the start.sh and the install should upgrade correctly. This was due to a bug in the FTB installer, the serverinstall_4_2115 file that is pulled down from FTB.

@DarthLlama The start.sh is generated by the forge install that is run as part of the container. If it is running behind by 4000ms it seems like it may be starved for resources. The Stone Block 2 container requires 6GB of memory. I will take a look at the install again tonight and see if I can find any issues in the install script. @RedRobo The permissions need to be set on that directory under appdata. 777 means that owner, group and all users will have read, write and execute on that directory. You need execute on a directory in linux in order to change to that directory, otherwise you will not be able to. Opening a terminal and running chmod 777 /mnt/user/appdata/sevtechages will set the permission on that directory. There is nothing extra to be installed, the container downloads and installs the appropriate files for that modpack on startup. Provided it can actually write to the required directory

Java only. There are bedrock containers available in the Unraid App Store. But I’m not aware of modded bedrock. Sent from my iPhone using Tapatalk

Same solution, check the settings for the server and make sure that the path assigned to `/data` is set to 777 permissions. That should allow the container to write to that space.

I've been managing any console commands by putting myself in the OPS list and that allows me to run any server commands. That should work for any of the existing containers. I'll see about adding the whitelist to the server config though, just like the Ops list. It should be pretty straight forward. For the RCON, I'll see if I can add config management for it. Enable/Disable and setting a password, & port.

@racingsquirrel The pack versions are available on Docker Hub. But DireWolf 20 1.8 is the latest 1.4.1, put up about a week ago. The first post lags behind a bit as the rest of the server version updates is for the most part automated.

@ItsNotNick I can't verify Pixelmon 9.0.2 because I can't get it to launch on my M1 Mac. But if you want to give it a try, it should work. If not, I'll pull it down. FYI: @ptchernegovski @Maxi531 FTB Infinity Evolved 1.7 should be there now, enjoy.

Yep, it's the permissions on the directory that is mapped to /data inside the container. You can try giving `/mnt/user/appdata/plexiglassmountain` 777 and it should be able to install. I'm not sure why some users have permission issues and others don't. I'm going to look into that.

Can you provide some logs, I'll see if I can help out. I found it took a while to start up for me and to get fully running.

Done.

I'm not sure I follow what you were fixing?

@Garden I pushed an update that should fix it if you follow these steps.

You can also switch to the "Advanced" view (top right corner of the docker tab in Unraid) and force an update. I've put in a patch to make sure the server is running on 25565. The container is expecting that port either way, so it always needs to be set to that port number.

@Garden Looks like they shipped a bad port config in their server.properties file. You can edit the servers.properties file and change the port value from `server-port=25569` to `server-port=25565` That should fix it. The error you found can be ignored, I get that too.

Try setting run.sh with 755 permissions. I'll push a fix that does it in the script. chmod 755 /mnt/user/appdata/ftbdirewolf20_118/run.sh

@Siggz Looks like there was a change in the FTB server installer. I've updated the container. Empty the /mnt/user/appdata/ftbdirewolf20_118 directory you can keep the world directory if you already have a world. Under your docker tab, in Unraid, switch to Advanced (top right corner). Then do a force upgrade for the FTBDirewolf20_118 container. Start the container and it should be okay.

@Diviance No, it's a bug in the container. There is a 0.4.4 release now, and there is a new image up that it should work with. Should have nothing to do with 6.10. A little background. Each modpack ships with a similar but unique installation for the server. So I have to script those steps in order to get a working image.

@Diviance it's more likely the permissions on /mnt/user/appdata/allthemods7

Added.

Done.

Done, direwolf20 1.2.0.

Done, should be available for install now.

@C_James thanks, that was my fault, it should clear up in the next sync. Update: All fixed, thanks again for pointing it out.

@k2trf done. I don't usually ship beta modpacks, but this one has been around for a while, so it's now 1.0.5.