Nodiaque

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

Start by looking what is filling up. What folder take all the space. Then you will know where to look

Try installing proton ge. Sometime, I had to toy with the option and bang it start working. Not all game work too

What do you mean by updated my game docker? I haven't push any update to it. Unless you mean steam downloaded an update? I just tried rebooting mine to see if any update and everything work fine. Seems like a corruption somewhere. You can try copy your config file and savegame data, erase everything, start a fresh new container and once it has properly started, stop and restore your file

So someone finally did it, OS as a subscription. No one did it yet, not even Microsoft, Apple or Android. It already exist in software for a while, but not OS. I'm glad I bought they key in the past, but I'm sure I'm not the only one that would go another route if they had to pay yearly to be able to update the OS.

Don't forget it's an early access game that's been out maybe a month. Yes there will be improvement by the Devs. Also, this is not a native Linux release, it runs over wine and proton (if you use the proton container) thus not native. This will add some performance issue. The server is highly unoptimized. People saw 20gb of ram usage with 4 players. I myself don't here about lags from my 6 players, but I have a very beefy server. Unfortunately, there's nothing me or you can do to make it more optimized.

pass only --requirepass password

You install multiple instance with different docker namer, server name, ports (must change both the config file and delete and recreate port forwarding) and the server path (not steamcmd).

unsure of you checked the documentation in the Community App page Config file should have only like 8 entries in it. If not, stop, delete, start, wait for it to be created, stop then edit.

It's all in the config file once the server is created. If it's blank, you didn't had the permission to read the file when you copied or the server didn't start properly.

You can check permission on your share and your file. Normally, the user nobody which is default unraid have access and you should be able to edit like any other file in appdata. If not, you might have a permission issue. There's multiple app you can use to edit from the community app like code-server and such.

In the folder where your path is mapped when you created the docker.

Do not use you steam account, leave this blank.