• Posts

  • Joined

  • Last visited

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

BlackHornet's Achievements


Newbie (1/14)



  1. The new Ripper update is borked for me, I get this error looping and the docker shuts down: 11.08.2020 15:02:03 : Unexpected makemkvcon output: 11.08.2020 15:02:03 : Too many errors, ejecting disk and aborting makemkvcon: error while loading shared libraries: cannot open shared object file: No such file or directory *** /etc/my_init.d/ failed with status 1 *** Killing all processes... I tried reinstalling from scratch and get the same issue.
  2. Thank you @ich777 for resolving the wget URL issue. I am able to start the SCP server now. One other issue @Atomic Bomb mentioned above, I have noticed is that the config files in appdata\scp-secretlaboratory\ConfigTemplates are only read once during docker creation, or recreation. If you reboot the server, any changes to these files are not read. The workaround is to edit the docker template, and once applied these files are read from. Is there a different location we should be editing the configs? SteamCMD: /mnt/user/appdata/steamcmd Container Path: /serverdata/steamcmd ServerFiles: /mnt/cache/appdata/scp-secretlaboratory Container Path: /serverdata/serverfiles EDIT: It looks like MultiAdmin pulls from the ConfigTemplates folder initially, but you need to edit scp_multiadmin.cfg to point to a specific config location. I then created \appdata\scp-secretlaboratory\Config and rebooted the container. Edit the content of scp_multiadmin.cfg: config_location: "Config" How to configure MultiAdmin: Now changes to the server config files take after a reboot!
  3. When I run the docker: ich777/steamcmd:scp-secretlaboratory for the first time I get an error in the logs. ---Installing MultiAdmin--- wget: missing URL Usage: wget [OPTION]... ... Try `wget --help' for more options. ---Couldn't download MultiAdmin, putting server into sleep mode--- I see on the MultiAdmin github that there was a recent URL change, could this be the problem?