ich777

Nothing to worry about, his is just a warning from WINE qnd appeats on every instance from the container. This is the Docker network when the container is on bridge mode, also nothing to worry about. Yes. I would suggest that you start over again, delete the container, delete the wreckfest folder that is located in your appdata directory and pull a fresh copy from the CA App. One question about your settings file, have you specified somewhere you LAN IP? If yes, don't do that, always specify 0.0.0.0

No worries! Just saying... I'm not really into mods... But I apprechiate everything you post here that will help others. My best guess is that some mods need Windows libraries that are not or at least not fully supported in WINE.

Das würd ich so echt nicht behaupten... Die meisten meiner Container funktionieren Grundlegend anders, fängt bei den updates schon an. Deine beschriebenen Probleme hatte ich früher auch teilweisr. Bist du dir da 100%ig sicher? Kommt auch auf die Größe der einzelnen Pakete, ob sie Passwortgeschützt usw. sind.

Das hab ich schon öfter gehört. Meine container basieren all auf Debian u für SABnzbd kompilier ich par2-multicore und unrar selbst dediziert und nehm nicht die von den offiziellen repos, vielleicht liegts daran?

Please make sure that you are on the latest BIOS version, enable "Above 4G Decoding" & "Resizable BAR" support in your BIOS and also disable C-States.

Your iGPU isn't enabled. Install the Radeon TOP plugin from the CA App and it should work after you've installed the plugin.

My server is running the 510 beta driver just fine. You only see drivers that are already compiled for unRAID. What do you mean exactly with this?

I don't think so. I'm not familiar with modding wreckfest servers, maybe there is another issue, maybe some mods are not compatible with WINE?

Exactly like the description of the ports tells you to.

Go to your Docker page -> click on the OpenVPN-Client container -> click "Edit" -> at the bottom click "Add another Path, Port, Variable, Label or Device" -> from the drop down select "Port" -> enter the ports from the container you want to route through at Host and Container port (like it is in the original template for the routed through container) -> click "Add" -> click "Apply". The container that you've routed through should now be reachable again.

Whats the exact issue? Have you followed the instrucions step by step? What FritzBox are you using?

Can you send me a screenshot please, I will look into this.

May I ask what the exact issue is that you've experiencing?

First of all I would try to connect through the Steam Server browser if you can see the game, please do the following: Open up Steam and click on "View" -> "Server": Then click on "Favorites" and in the bottom right on "Add Server": In the next dialogue enter UNRAIDIP:27015 (of course please replace "UNRAIDIP" with the IP from your unRAID server) and on "Add to Favorites": After you have done that you have to click one more time the "Refresh" button in the lower right corner and you should hopefully see your server. If you see your server you can go to the next step and try the exact same thing as mentioned above with the only difference that you have to enter your Public IP instead of you unRAID IP. Please disable this immediately, this will change nothing and should not be enabled anyways! Your server is running just fine but there is somewhere a miss configuration or another little thing that prevents your server from showing up in the list but keep in mind that this doesn't mean that it isn't reachable from outside your network. Set it back to what it was, if Valheim works this container will also work if you've forwarded the ports properly.

Why would you want to reinstall SteamCMD? You don't have to shutdown any container since the files in the SteamCMD directory are only accessed at container startup when the containers check for updates. No, just stop any container that you want, delete the contents of the steamcmd directory and start the container again (you can keep the other containers running while doing this). May I ask why you want to do this?

So the issue is solved now?

Exactly, I would recommend to start over and delete the container and also the directory for this container. Also this seems more like an issue with the Prometheus container so I would recommend that you ask in the support forums from the container iteslf. Are you on 6.9.2 then it could be possible that if you have certain application files from Docker on ZFS that it simply doesn't work.

I will try it when I got home from work on my server and report back. From what I see in the logs everything looking good for the Caves and Overworld, maybe some setting was changed so that the Caves are now a separate Dedicated server? The default settings that I ship the container with are that a cluster is created and both the Overworld and the Caves are started as two separate instances but are only visible as one, however if something was changed in the config that no cluster is created it is possible that you see two instances running. Hope that makes sense to you. Will get back to you when I've tried it on my server.

On what unRAID version are you? For 6.9.2 and all versions above OpenZFS 2.1.2 is already compiled and ready to install, I think you have to delete the old package on your USB Boot device and reboot your server (make sure that you've got a active internet connection on boot, otherwise the download will fail). To remove the old package run this command from a unRAID console: rm /boot/config/plugins/unRAID6-ZFS/packages/*

You have to wait, a long, long really long time and after that you can pull the log, Firefox actually doesn't crashes. If you are running it with caves then yes, if you are running it without caves than not. I can't change the instructions for how to get/create your cluster_token.txt since this is hard coded in the game. Anyways, if you Google for something like: "dont starve togehter cluster_toke.txt" you should get plenty of results. If you want that the description how to create such a token you have to make a post on the Don'tStarveTogether forums: Click Maybe the developers from the game will change it. If you only got one container running without the Caves then it should only be one server visible. Maybe you have accidentally changed the config from the server so that it actually creates a second instance.

I think that is not possible for a iSCSI volume, at least not easily. One thing that can help is that you remove the FileIO volume from iSCSI and assign it new, but it can also happen that the existing one is overwritten, really not to sure if it will work anyways.

This is really strange... Is one maybe for the Caves or did you deactivated the Caves? Can you restart the server and send me the log output please after restarting the server until it's fully started?

Yes, this is also mentioned in the description from the container. What execution error? Please post a screenshot or the log. I've also run multiple servers with one SteamCMD directory and it works flawlessly. On what unRAID version are you?

I think the server is crashing and not restarted because the files are moved from the Cache to the Array, you prevent this by setting it to "Prefer"

Already compiled and updated. 🙂