Nodiaque

No it's your firewall that is not configured properly. What you are doing here is this. The docker container run on port 7777, but you expose those port for outside connection as port 7779. That mean now to connect to the server, you specify port 7779 instead of 7777. Your screenshot clearly show container port 7777. The server still listen on port 7777. So if it doesn't work when you change the exposed port to 7777, it means it's a you problem, something is in conflict on your unraid server or network. Instruction clearly state to use the exact same port mapping as the game parameters you use. Yes, you can "cheat" and only change the exposed port and then firewall outside connection to that expose port, I've done it many time which is a very lazy way of doing things and could lead to problem (like game showing in the server list with the wrong port, unless you also forward port 7777 externally to 7779 internally). Also you must change the port in the conf if you change it. In the end, if it's working now, it means your other thing you put on port 7777 that you talked earlier is causing problem. You might have firewall rules in place or other configuration that are making conflict. It's not a container nor a template issue, nor even bad information. 7777 is the official port you can found on the steam page and official game FAQ. The dev are having a hard time updating everything, they themselves said only Udp at first but people found out TCP was needed also.

I cannot say, maybe read back some of the pages, people had the problem and many different thing were done by different user. The container itself does work, there's some networking or configuration issue somewhere.

It's out of my control. Steamcmd is the one doing the installation. Maybe the new version of the server doesn't exist yet. When you delete the acf file, it will force an update check. If nothing is detected there, It's steamcmd problem. That's what just happened with mine. We can see it checked and downloaded something (probably the missing acf files I deleted).

I never saw that. Do you have the game downloaded in appdata? Might be networking issue

Check comments and FAQ. This docker doesn't need update, it download from steamcmd everytime it's started. Problem is sometime (too many time), steamcmd (which is official steam client) doesn't detect file or version change and doesn't update. There's instruction in the 2nd post to force the update You cannot assign an ip when you run host. Host use your unraid server ip What you are talking about is not host but using something like the custom eth0 connection which you can put on your internal ip which is set during your docker network settings (in settings => docker when docker isn't running). It would be an option to run it with it's dedicated ip, I did that in the past for my game server so they were not on the same vlan of my unraid.

you did add those port in the unraid template and added the game_params? Also, the ip in local connection, unless you use a dedicated ip on your lan, should be your unraid server not the docker ip address. I've heard on the steam forum that some had success with DirectConnectionServerAddress and putting their ip on it (would be unraid server ip). Doc says this is not used but the doc on that game isn't very sharp.

Oh yeah permission must be good. That's why I always chmod and chown

Always when it's not running, never while it's running. True for any game server, it's also in the FAQ, the container info and the official moving FAQ on the dev website ;)

What do you mean? The docker doesn't contain enshrouded, it's downloaded when you start. You can read the FAQ on the 2nd post to have more information. If steamcmd doesn't see the update when starting, follow the instruction in that post to force the update. It's not something that I can anything about it unfortunately, it's a steamcmd problem..

Per what I've read here, it's normal and stay there until someone login. Did you do the extra configuration? There's FAQ on the first page to what to do for Direct Connect, which is the default method now. Invite code won't work if you don't change the template.

Yeah, it's a know issue for all of dockers I could find. We use all the same way, even the doc for running docker is made from someone in the community without warranty. It's what happen when you run un-optimize software onto a compatibility layer. If they release a linux native client, it will be way better

I've created a little FAQ on the first page, 2nd post. It should cover all the findings you guys did. I've updated the template but not the docker itself since it's not really possible because of the worldID. I also notice the template default to -dev tag. Unsure why, something badly copied. I restored the configuration properly on the template. Should be in CA in the next hours. Do validate that in your docker, repository says nodiaque/steamcmd:windrose or nodiaque/steamcmd:windrose-xvfb

This page might help From what I see, the WorldIslandId from serverdescription.json must match IslandId in worlddescription.json They also added more documentation, which change again the configuration! The are getting tiresome. I'm updating the guide and template, hold on

Ah weird, doc I found said only Udp. But it's possible, many other game did had TCP and udp

User preference. Some says performance is better with proton other the other one.

Something I saw on another thread is people put either the server on its own ip or when using bridge, they out the unraid server ip in multi home. Might worth a shot. The direct connection feature isn't updated in the doc yet (unless it happened today)

No the data won't be removed. You'll also need to delete the configuration in previous apps, else it will reuse the saved template. You can also just add them directly with the info and screenshot I put. Worst thing is they aren't added properly and it change nothing.

Unraid doesn't update the template.xml when you update the docker, it's a seperate entity. I just notice I made a mistake on the template though, I removed the branch. I just update the templace to fix this issue but will take sometime. Normally, if you go through the apps, you should see the template update when you click install, which mean reinstalling from scratch (you need to delete the custom template under "previous apps" after removing the docker first). But you can simply add the one I've put in the guide, whatever you find easier. edit: until the template get the update I just pushed with the branch, you might not see that it's already installed when going into apps.

You need to update. Delete the file appmanifest_4129620 under steamapps and it will force update. STEAMCMD problem I updated the dockers and the template. If you don't change anything to the template, it will continue working as currently, which mean invite code and uPNP/Relay server. To use direct connection, you must do the following modification in the template (or wait for the template to update in unraid) TO ENABLE DIRECT CONNECT, THE FOLLOWING MUST BE DONE Add a new variable "GAME_PARAMS" with value: -MULTIHOME=0.0.0.0 -PORT=7777 -QUERYPORT=7778 u After, you must add 2 port binding, UDP 7777, TCP 7777 and 7778 (you could simply also create one at 7777:7778 but I prefer having them seperate) After in ServerDescription.json, you must configure the following: "IsPasswordProtected": true, "Password": "yourpassword", "UseDirectConnection": true, "DirectConnectionServerPort": 7777, You can then switch your network configuration to bridge instead of Host. Don't forget to set a password in the config file else anyone can join your server now. You might need to change this in the configuration. No one talk about it thus I'm unsure if it's really needed

I'm currently updating template and docker to implement direct port

You don't see this in the docker template (not in the forum)? I'll have to find out why if you don't Are you not able to connect? Mine always stopped there but I don't own the game so never tried to actually connect. Oh the direct connection info are new parameter, they weren't present before. This mean no more uPNP I guess. I'll have to check if they updated their guide to update to that. Direct is always faster then flimsy upnp.

Thank you. I do have a link but I don't even know if it work. I think I created it like 10 years ago. I'm doing this since I like doing it XD the link is normally in the docker application (like windrose) or on my app profile in unraid.

technically that reinstalled the container. Saving the config and savefile, flushing the folder and restoring only these would yield the exact same result. A bug with steamcmd that linger

Sometime steamcmd doesn't update. You can delete a file to force the update. Look up in the thread, inch specified a file to delete that trigger the update. Else just save the config and map, delete the rest and start a new. It's a steamcmd bug that we can't do anything about it. Happen with any game. I don't think so. You can try, but I'm pretty sure it's EA bug. This docker doesn't have ssh or FTP so sftp won't work. But maybe you can just put the file in the appdata folder directly like anything in unraid.

That's early access game for yeah, specially in a emulation world. If they release a native linux server, it will surely be more efficiant.