Nodiaque

Hello everyone, I've had a Windows server 2022 VM for the past year or so. Everything was always great, daily reboot with blueiris on it no problem. But for the past I think month or two, I notice that sometime, the VM is UP but the OS is down. I have to force shutdown and start it back up. Once I log, I have Windows asking me why I crashed. Looking at the log, I see ESENT errors. While the os is loaded, I found out that nearly all of my 32gb of ram are used and that it's nearly all from the driver I'm unsure if that's the root cause but it is something weird. I'm using virtiofsmode with manual unraid share mapped. Unraid 6.12.8, no GPO passthrough. Anyone know how to fix this freezing problem? Thank you edit: just remember that the ram problem is because of ballooning in the virtio drivers under Windows that doesn't work well and the easy fix is to set min and max value for ram as the same in the configuration. I'm sure I did do that in the past so unsure why it's back to difference value. But I don't think that was the freezing problem, time will tell.

Hello, Enshrouded is highly unoptimized, specially running on non native platform like docker does. There's not much we can do about it unfortunately. The fact you had a plugin froze all your unraid before is concerning, never had that. It might be the same case here, something is strange with your unraid. The log you posted is only the creation log, not the log of the server itself. But you can see through this forum and only that many struggle with enshrouded performance even at low count.

Hello everyone, I have an ongoing issue that I though was to a specific docker container but turns out that when I checked on my other unraid, it doesn't have the same issue. What happen is from the webgui, I press stop on the container and it will sit there. Looking at the docker monitor, the docker is still running and doing it's job. Once the timeout is reach, I get an error on the webgui and the docker get killed. I still see it as running on the webgui until I refresh the page. Whatever stop the docker from the webgui, it will behave like that. Container Restart, stop, apply update / change config, backup plugin, server shutdown/restart, they all end up killing it If I open a cli and do docker stop container, the container stop in seconds. So I know it's not the container itself, something in unraid is badly working. I looked at my syslog, there's nothing at all. I need a way to have more verbose logging or a way to diagnose this problem. It's not tied to a specific container, it happen to many container even new one just downloaded for the first time. It's not all container. Same container on other unraid server doesn't have the problem. Issue existed since at least 6.9.x. Currently on 6.12.8. Thank you!

A port forward is suppose to have internal destination ip, which is your unraid server ip (or docker if it has an ip directly on your network which mean same 3 part address as your unraid server and your computers). Pretty sure this is the problem in the screenshot cause home ip doesn't begin with 212. It should be something like 192.168.y.z or 10.x.y.z.

Where are you trying from when you try from the internet? Some router doesn't allow loopback connection from the wan (which mean coming out from the lan to the internet than coming back in in the same connection). If you are trying from a remote computer on the internet, there's 2 possibility. The port forwarding isn't properly done (screenshot you showed seems to be port opening and not port forwarding) or your ISP is blocking it

network configuration is in the docker configuration of the application itself (enshrouded). It's one of the many configuration. You need to first check if you can connect directly to it using local ip (the unraid server ip OR the docker ip if it's an ip from your local network). You can do this by following instruction here If this doesn't work, either your connection information are wrong or you have something miss configured. Normally, you wouldn't need any port open / forwarded to do this since you are on the same network. You might wanna try using both port, I don't know which one is the one used to connect to the game.

if you can't connet directly with the ip of your server and port, it means there's something badly configured. By the logfile ou provided, we see HostOnline (up) which mean the docker is running properly. Did you change any of the port mapping in the configuration? What network configuration is the docker running on?

Connect to your unraid ip from the game and not your public ip. There's a feature in my knowledge to connect by ip (I don't own the game)

Hello, just to be sure, you shutdown the server before editing the config file? The game might not appear in the game server browser. Sometime it take a very long time. If you connect to ip directly to your unraid server (not public ip), does it work? Try without a username/password first just to check if the config is properly done. According to log file,server seems running fine

Hello, I have some docker that when I stop them, they will simply error out (timeout) than report stopped. If I stop them by cli, it nearly instantly close like any other docker. This seems to either happen randomly or always on some. I'm unsure how to fix that. Thank you

Hello, Wine isn't made to run a server, it's a "compatibility layer" for windows application. We cannot have a working Windows OS under docker, it's not made for that and performance would be horrible. If that's what you want, you could simply run a OS VM in unraid. Also, all Wine version of server are inferior version of real linux version. Once a linux native problem is made, we stop using wine and run native version because there's much less problem with a native version.

I honestly never saw that. Could it be out of memory from docker itself? Do you see something else like docker image full? Maybe corrupted memory? Could also have corrupted data, maybe try saving your data and starting from scratch. Just some idea to see if it help. Didn't get any other report about that

Install old version driver in unraid, don't use latest.

Change it into steam

Your missing a crucial extra param --runtime=nvidia