guyonphone

@HillyBilly Try deleting everything again and then running this from CLI: docker run -d \ --name='ProjectZomboid' \ --net='bridge' \ --pids-limit 0 \ -e TZ="America/Los_Angeles" \ -e HOST_OS="Unraid" \ -e HOST_HOSTNAME="Unraid" \ -e HOST_CONTAINERNAME="ProjectZomboid" \ -e GAME_ID="380870 -beta unstable" \ -e GAME_PARAMS="" \ -e VALIDATE="true" \ -e USERNAME="" \ -e PASSWRD="" \ -e ADMIN_PWD="REDACTED" \ -e UID="99" \ -e GID="100" \ -p 29015:27015/tcp \ -p 16261:16261/udp \ -p 16262:16262/udp \ -p 16262-16326:16262-16326/tcp \ -v /mnt/user/appdata/steamcmd:/serverdata/steamcmd:rw \ -v /mnt/cache/appdata/projectzomboid:/serverdata/serverfiles:rw \ --restart=unless-stopped \ ich777/steamcmd:projectzomboid Modify the password and host info to suit your server, and see if this fixes things. Just to double check you don't have an old servertest.ini anywhere loading up mods do you?

I did the following: - Deleted Container and Image - Deleted /appdata/projectzomboid - Deleted /appdata/steamcmd - Ensured I wasn't doing any port translation from within the container to the host. - Re-did my servertest.ini -Ensure no mods are added

Hooray! I can confirm the server is up and running and I was able to connect to it! Thank You @ich777

@ich777 I apologize, I should have said more. It's my assumption at this time that PZ Unstable Build of 42.13 likely doesn't work yet with standalone multiplayer servers. They even elude to it in the patch notes: - We strongly recommend only playing in coop or on whitelisted servers. I was just trying to get the conversation started, if any changes needed to happen to the container. Also I should have shared the SQL Lite error, but I was having difficulty grabbing it because the container would close my log window when it would reboot. Im hoping a hot patch will eventually come out that might help. Thank you for the work that you do!

ProjectZomboid Version 42.13 is out with multiplayer. I tried to run it by doing this: docker run -d \ --name='ProjectZomboid-The_Boys' \ --net='bridge' \ --pids-limit 0 \ -e TZ="America/Los_Angeles" \ -e HOST_OS="Unraid" \ -e HOST_HOSTNAME="Unraid" \ -e HOST_CONTAINERNAME="ProjectZomboid-The_Boys" \ -e GAME_ID="380870 -beta unstable" \ -e GAME_PARAMS="" \ -e VALIDATE="true" \ -e USERNAME="" \ -e PASSWRD="" \ -e ADMIN_PWD="REDACTED" \ -e UID="99" \ -e GID="100" \ -p 29015:27015/tcp \ -p 16261:16261/udp \ -p 16262:16262/udp \ -p 16262-16326:16262-16326/tcp \ -v /mnt/user/appdata/steamcmd:/serverdata/steamcmd:rw \ -v /mnt/cache/appdata/projectzomboid:/serverdata/serverfiles:rw \ --restart=unless-stopped \ ich777/steamcmd:projectzomboid however it fails even on a fully clean boot there is some sort of issue with the SQLLite DB where it is tripping up on creating a table that already exists.

I am running a game server in a container, I was thinking about how it would be nice to be able to give someone else the ability to login and perform a restart of a container, and then I got to thinking that UnRaid could have a full User Permission system, which could be handled via the GUI. (CLI too of course) Imagine a world... Where you could assign users granular permissions to VM's, Containers, plugins and other permissions. Users with limited rights would only see GUI access for objects they have rights to view. Containers: Permission to Manage\edit a specific container or multiple containers. Permission to add a new container. Permission to stop\restart a container. Permission to see container logs. Virtual Machines Permission to Manage\edit a specific VM or multiple VMs. Permission to provision a new VM. Permission to stop\restart a VM. Permission to see VM logs. Plugins: Permission to install plugins Permission to remove plugins. Unraid Settings: Granular user permissions to allow the ability to manage the array. Start/Stop the array. Essentially extend user permissions past the file system into every aspect of Unraid. Etc, so on and so forth. Now tell me why my idea is a horrible one and I should have never had it

I feel a feature request coming on :). I appreciate the suggestion. Posted one here:

As the title suggests I would like to create a user who's only ability is to reboot a container, is this possible?

I actually got this figured out, and was totally caused by my own issues. First this is absolutley the correct directory to copy the mod to: '\Empyrion - Dedicated Server\steamapps\common\Empyrion - Dedicated Server\Content\Scenarios' My issue was that I was trying to change the scenario on an already existing save game. So once you boot the container the first time and allow it to download all the game files, you then need to turn the server back off and do the following: Navigate to "Empyrion - Dedicated Server\steamapps\common\Empyrion - Dedicated Server\Saves\Games" and rename 'DediGame' to 'DediGame.old' Copy the Scenario you subscribed to and downloaded using your client computer From: '\Steam\steamapps\workshop\content\383120\2550354956' To: '\Empyrion - Dedicated Server\steamapps\common\Empyrion - Dedicated Server\Content\Scenarios' Rename the folder '2550354956' to 'Reforged Eden' Modify the 'dedicated.yaml': Change the field 'Srv_Name' under Server Config from 'DediGame' to anything of your liking. changing the 'CustomScenario:' field from 'Default Multiplayer' to 'Reforged Eden' (Without the quotes) Power the server back on, this time it should load 'Reforged Eden' and create a new save game folder. This is what fixed it for me.

Hello fiR3W4LL, I am running the Empiryon docker container, and I am also interested in installing a scenario mod called 'Reforged Eden'. I have subscribed to the mod and downloaded the files on my game client and then tried to copy the files to the server in this location '\Empyrion - Dedicated Server\steamapps\common\Empyrion - Dedicated Server\Content\Scenarios' I then have modified the 'Dedicated.yaml' file with the new name 'Reforged Eden' for the scenario value. When the mod is installed on my client machine it installs it to '\Steam\steamapps\workshop\content\383120\2550354956' I am unsure where to copy the files and was wondering if you had any pointers or ideas on why it's having issues. Thanks!

Thank You, I ended up rolling back to a previous version and its working now. Must be an issue with the release.

Hi, After updating to 1.22.1.4228-724c56e62 I appear to be unable to play files in firefox or edge. I am able to navigate plex, and click into the info screens for items, but I cannot play an item. I click play and nothing happens. It looks like the browser registers the click but nothing changes. Chrome works just fine with no issues. I have tested on multiple computers. Any ideas, I have removed all ad blockers, and cleared my cookies, etc.

Hello, I am receiving the following error after updating the plex docker to the latest build after upgrading Unraid to 6.9.1. docker: Error response from daemon: Unknown runtime specified nvidia I am running the nvidia driver plugin Any assistance would be appreciated. EDIT: It looks like it was the driver version which was causing the issue. I downgraded the nvidia drivers back down to v455.45.01 and Plex is working again.

I had the same issue as you, I also had to update my ovpn file from the console. Something is clearly wrong with the docker.

Hello, I am interested in using the following script with this docker container: Plex Autoscan I am concerned that if I go through the install and configuration, that it will just be overwritten the next time the docker is updated. Is there a way for me to do this? Thanks

Having issues with Plex Loading after upgrading to newest version: Docker appears to be running, but when I visit the URL via a browser, I just get an empty white page and in chrome the spinning circle in the tab. Tried firefox and that also failed. False alarm, rebooted my local machine and this resolved my issue. Kinda weird, but I'm happy it fixed it.

I do, but that shouldn't be an issue right? Why is Sabnzbd reporting the array free space wrong?

Hello, I have Unraid 6.6.6 I have Sabnzbd 2.3.5 It is reporting incorrect Values for Free Space. Any ideas on how to correct? Thanks

<Redacted> Made a mistake an posted in wrong place

Hello, I am interested in using "Lock for Plex" https://forestfirefly.github.io/lockforplex/ I have installed the plugin but I get errors during the installation of the install.sh script because the docker doesn't seem to be to keen on the use of sudo. I tried removing the sudo commands from the install.sh script, but that didn't seem to resolve the issue either. The plugin is available in plex but the locking just doesn't appear to work. Additionally the file wants to restart the service "plexmediaserver" but that doesn't appear to work inside the docker, as it appears some other modification was made, and I don't know enough linux to determine what that is. Here is the contents of the install.sh script I am trying to run. #!/bin/bash # Init FILE="/tmp/out.$$" GREP="/bin/grep" #.... # Make sure only root can run our script if [[ $EUID -ne 0 ]]; then echo "This script must be run as root" 1>&2 exit 1 fi cd "/config/Library/Application Support/Plex Media Server/Plug-ins" sudo chown -R plex:plex Lock_for_Plex.bundle cd "/config/Library/Application Support/Plex Media Server/Plug-ins/Lock_for_Plex.bundle/Contents/Resources/lock_support/" sudo a+x lock.sh sudo a+x unlock.sh sudo a+x sqlite3 service plexmediaserver restart Any help is appreciated.

Hello hurricanehrndz, I did not see that, I will try out, thanks!

Hello Hurricanehrndz, Just wondering if you had any update to ubooquity. Thanks!

Sweet! Can't wait to see if it fixes my issue!

Thanks CHBMB, It turns out this was an issue with chrome. I dumped my chrome cache settings, and closed and re-opened the browser and everything is working again. admittedly i should have done this prior to writing a forum post. Thanks for your help!