ich777

Which game?

From what I know it is and back when I created the container it was working fine, it is also in the description from the container: Yes, because the name in the Docker template overrides the config file.

Just to let you know, I've installed the container (complete fresh install) with the new update and it is running as expected.

Since my containers are self maintaining and download updates on every start/restart you shouldn't have to do much, just restart it. You can set validation to "true" but that shouldn't be necessary. Please don't forget to set ti to false after updating the container or simply leave it empty <- you never should set validation to "true", only if you have issues when updating the container. I don't know much about V-Rising but as long as they don't change how the dedicated server is started or the binary name everything should work as always with this container, let me know if you are experiencing any issues but I think you will let me know anyways...

I didn't even noticed that this is a issue since I don't use that, I will look into that, thanks for the report! Would that be sufficient for you: Of course this would be also possible: I think just for consistency the second would be better, what are your thoughts on this @primeval_god?

@supawiz6991 & @ezhik thank you both for the report, sorry that it took so long, the issue should now be fixed. Please update the plugin to the latest version and let me know if you experiencing any issues after the upgrade.

I would recommend that you use the support thread over here:

No. How do you try to connect, through your internal or external IP address? Please also read the description from the port again, this is not a web server or a database, game server most of the times work differently. You have to delete the port entry in the template if you want to change it like in your case from 27015 to 27018 and create a new port entry in the template with the host and container port set to the same port of course for this game UDP. A simple port forwarding wont working because the dedicated server sends it's port (27015) in the initial handshake with it and since you are forwarding the port from 27015 to 27018 the client tries to connect to the port 27015 and not on 27018. Also don't forget to change the config from the dedicated server so that the container actually uses the port 27018 inside the container and not the default 27015.

Thanks, I will look into that, this will take a few days.

And please disable validation! This is only for troubleshooting reasons in there when the game won't update and this will slow down the start from the container significantly. Validation should never be enabled if it isn't needed.

Please change the path for the game files from the FUSE path (/mnt/user/…) to the real path where the files are like /mnt/cache… or /mnt/disk2/… It has a reason why the container template points to the real file path by default.

On what Unraid version are you. Please post a screenshot from your container template. Please make sure that your path to the game files points to the real path and not the FUSE path /mnt/user/…

I really don't know but I'm assuming this is a game issue and there is nothing I can do about: SteamLog [SDR k_ESteamNetworkingSocketsDebugOutputType_Msg] [Data] Ignored bad REDACTED:52386. Stray data packet from host with no connection. Ignoring. UnityEngine.Logger:Log(LogType, Object) UnityEngine.Debug:Log(Object) Stunlock.Network.Steam.Wrapper.SteamSocketNetworkingLogs:OnLog(LogSource, ESteamNetworkingSocketsDebugOutputType, IntPtr)

From where do you have that information, can you give me a link to the tutorial maybe this would make my life much easier since I even don't know that game...

Please read the first recommended post on top of this thread. There are some 11th gen CPUs out there which doesn't support GVT-g nor SR-IOV.

I think this game does not have a dedicated server or am I wrong about that? This game seems online only.

I will look into that, please stick to the static version numbers for now.

No that I'm aware of, you are the first one who is reporting that. Please post your Diagnostics. Have you yet tried the official Plex container if that is working? Do you have screenshots from nvidia-smi, the Dashboard and so on?

I could of course compile this driver but I‘m not soo sure if it compiles against newer Kernel versions thatn 5.18 In my personal oppinion this is a thing that ESXi sould solve or at least workaround.

You should use du -sh /var/log: root@Tower:~# du -sh /var/log 9.4M /var/log root@Tower:~# df -h /var/log Filesystem Size Used Avail Use% Mounted on tmpfs 128M 9.4M 119M 8% /var/log As you can see both values are the same on my server. Do you maybe have any symlinks manually made which are pointing to /var/log? Please also include your Diagnostics for further help.

No, this is not possible in the debian-bullseye container or at least not how it ships OOB because it is not intended for that use case but you could maybe do that if you install everything that is needed. You have to install all dependencies/packages to compile the Kernel first, after that you have to compile the driver, then you have to pack it and after that you have to place it in the correct directory on the USB Boot device. Please also note that you have to do this each time you upgrade your Unraid version. The point that I'm trying to make is that this is not practicable for most users.

Yes and no. You can do it yourself, you'll find how I do it in my GitHub repo for the driver here: Click

Maybe it's a PSU issue but I can't tell for sure, maybe try to switch the PCIe slots if there are any which are suitable for the card. If the card fell from the bus this indicates usually a Motherboard issue or PSU issue.

Can you please post your Diagnostics with that I can tell what's going on and usually it's not tied to the VBIOS.

For Unraid itself? You could also do that in a Docker container... I know the template that you've linked but I haven't got time yet to wrap my head around it.