Jump to content

Goobaroo

Members
  • Posts

    235
  • Joined

  • Last visited

Posts posted by Goobaroo

  1. On 7/7/2022 at 3:58 PM, DarthLlama said:

    Now running into a new error however. Now every time the server starts it is modifying my server.properties file and changing the Port I have allocated (I'm running 4 different minecraft dockers, so I allocated a non-standard port for this in the docker settings, and the server.properties file).  Where is the script that is changing the server port and changing the server. properties file? I've been poking around and can't find it. Also since I deleted the start.sh file, uninstalled the docker, and reinstalled it, the start.sh file is still gone, and this is happening. Sorry for all the issues!

    + sed -i 's/server-port.*/server-port=25565/g' server.properties

    @DarthLlama You should be setting the PORT in the config for the application under Unraid.  The port that the server runs on inside the container is static at 25565.

     

    When docker containers start up, they map the port defined in the config from docker to the containers internal port.  That is configurable in the docker container settings.

  2. 4 hours ago, GonjaT said:

    Hi. It appears that "All the Mods 7" is now 2 updates behind and the container hasn't pulled the new updates yet since they released.  Not sure why but just wanting to let you know.

    Thanks.

    @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.

  3. @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 :) 

  4. On 6/18/2022 at 2:34 PM, mfreeman451 said:

    I'm also having permissions issues after the latest Unraid upgrade of 6.10.3 and latest docker image, the container is unable to start.

    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.

  5. 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.

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

     

    21 hours ago, Goobaroo said:

    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.  

     

  7. @Siggz Looks like there was a change in the FTB server installer. I've updated the container.

     

    1. Empty the /mnt/user/appdata/ftbdirewolf20_118 directory you can keep the world directory if you already have a world.
    2. Under your docker tab, in Unraid, switch to Advanced (top right corner).  Then do a force upgrade for the FTBDirewolf20_118 container.
    3. Start the container and it should be okay.
    • Haha 1
×
×
  • Create New...