Just now, nerd said:

may i ask why is this docker running Proton??? why dose it not work like ich777?, also i have my running but now i have a bug showing my server 2 times on list..

You don't have to run proton. Go back on the first page or in the unraid app, there's 3 version. One without proton, one with proton mark experimental and one beta with another version of proton. If you go read the thread, you'll see people ask for the proton version and I delivered. Some say they have better performance on the proton version, some don't, and recently someone told me the latest version of proton deliver better performance hence the beta version that I'm waiting for confirmation (see thread).

The proton version is a version from ich777. He did it with me, he did many other container with proton and it's basicly his work.

Yes you don't backup everything under appdata. You only need the savegame and configuration file. You don't even need the backup, it's just a save or the savegame folder (no config).

What you did is exactly what I said to do. You could have just wipe your appdata and refresh your container, then restore once it's downloaded (and stopped). It's exactly what I said to do all this time when the auto-update from the steam client doesn't work.

As for the double server, tell that to the dev, it's not the docker fault. Also, the server browser is a snapshot in time, you might have ran multiple time your server in a small timeline (specially when switching docker container) which created different ID, thus server is there. Game browser on any game is never live, it take time to refresh. I remember when this game got out, people where having a hard time seeing there server in the browser cause there was too much and it took sometime hours. One of them will sooner or later disapear.

Also, please use the edit button instead of doing reply on reply ;)

Also, I don't know what you do but you often put underline in your text.

Edited January 22Jan 22 by Nodiaque

Oh, I will tell the dev this game needs so much work, and the perms need to be fixed big time! It should be like rust! You can add who can use your flame altar!! Not all these stupid perms it has. At the end of the day, what's the point of running a game server when no one can play it? Right now only guests can join and can't do anything. If you give them perms, they can grief your base… Just letting everyone else know I found out the hard way…

Edited January 22Jan 22 by nerd

I don't have the game so I cannot say. My server run with a pass and only my friend play together. As far as I know, you can set role with different permission

https://enshrouded.zendesk.com/hc/en-us/articles/19191581489309-Server-Roles-Configuration

Depending on the password, they get different permission.

Also:

Please note: all user groups have full access to the game world outside the player bases and can engage in combat, collect materials, dig for resources, solve quests etc. 

Yes, they can get to your base, it's a PVP game. Just like Conan Exiles and other game like it. But that's outside the scope of this thread and better discussed on the game social media platform.

Edited January 22Jan 22 by Nodiaque

2 hours ago, Nodiaque said:

Normally in docker, you have versionning.

True but keep in mind that a container with 50 GB is something else and this for each version, I also think that DockerHub wouldn't be happy and don't forget about the copyright violations you are getting into.

1 hour ago, Nodiaque said:

The proton version is a version from ich777.

I think you are mistaken, the normal version is where I helped. :)

I did never understand why anyone wanted the Proton version because Proton has usually just fixes for Desktops and so on.

1 hour ago, nerd said:

not to be rude but installing a new one works, so it has to be something with your docker, it won't update must install a new docker and that means i lose everything

When it doesn't update the game do the following:

1. Stop the container

2. Delete the steamapps folder from the game directory

3. Start the container

4. Wait for the update to finish

This is a common issue with SteamCMD, nothing @Nodiaque or anyone else than Valve could do about that.

7 minutes ago, ich777 said:

True but keep in mind that a container with 50 GB is something else and this for each version, I also think that DockerHub wouldn't be happy and don't forget about the copyright violations you are getting into.

I think you are mistaken, the normal version is where I helped. :)

I did never understand why anyone wanted the Proton version because Proton has usually just fixes for Desktops and so on.

When it doesn't update the game do the following:

1. Stop the container

2. Delete the steamapps folder from the game directory

3. Start the container

4. Wait for the update to finish

This is a common issue with SteamCMD, nothing @Nodiaque or anyone else than Valve could do about that.

Thanks for the input ich777. I don't know where I got the proton from then cause I know nothing about proton. I think I got it from another one of your docker that do have proton and fork from it. Not a big thing, it's been so long.

And yeah, the docker size version and copyright are other thing to consider.

As for delete the steamapps, I had weird behavior on some game that by doing only that, it created some bug. It's why I prefer the start fresh appdata and just migrate the saves.

11 minutes ago, Nodiaque said:

I think I got it from another one of your docker that do have proton and fork from it.

I don't have such a container because I simply don't see a reason for Proton for a dedicated server, however that's not relevant here... :)

12 minutes ago, Nodiaque said:

As for delete the steamapps, I had weird behavior on some game that by doing only that, it created some bug. It's why I prefer the start fresh appdata and just migrate the saves.

That folder is safe to delete and will always trigger a re-verification from the files that are currently installed, this is a known issue and even asked often times on GitHub.
You also can't always delete, I mean you could, but this is basically even more than if you enable verification.

Just downloaded and setup Enshrouded_Proton.
I am able to see the server with the updated name but when I try to login the password does not seem to work.

Looking into the file there was no server password in the json i added "serverpassword: "DipDip", and this does not seem to correct the issue.

am I able to go into the docker console and use a prompt to verify the password or is there another file I need to update?enshrouded_server.json

The format for password isn't that. It changed in a version that I can't remember. Refer to the game documentation for how to setup the password properly. It's now using role base password.

Edit:my bad, I didn't see the json file on my phone and though you just put a password: somewhere in the file. I see now it seems to have roles. I honestly don't own the game so I'm not very sure how to setup the game itself. Maybe start with the demo file on the enshrouded website and go from there?

Also don't forget to edit the file while the docker is stopped.

Edited February 6Feb 6 by Nodiaque

Following up.

So I made the updates restarted up the docker and went back into the file and I noticed it removed the "serverpassword": "dipdip", line. that's weird. i went through the read me file and did not see the base server password within the files. \appdata\enshrouded_proton\enshrouded_server_readme.txt

The file is created by the game if it doesn't detect any file. You said you restarted. Did you change the file while the docker was running? If yes, that's the problem, never edit the config file while it's running.

As for the default config file or exemple, you can find them on enshrouded website.

I'm looking for some help with my Enshrouded docker container it is failing to save i think what happen is i downloaded a mover plugin that moved my save file to a different disk I'm not really sure what happened or what i should do to fix it i just don't want to lose my family's progress in the game in the log file i get this:

[savedata] Unable to write file Z:/serverdata/serverfiles/savegame/3ad85aea.new: file not found

[savedata] Unable to write blob 'Z:/serverdata/serverfiles/savegame/3ad85aea' size 256402.

[savedata] Compression of Blob 0x00000000::CSTR took 20.00 us

[savedata] Unable to write file Z:/serverdata/serverfiles/savegame/3ad85aea.new: file not found

[savedata] Unable to write blob 'Z:/serverdata/serverfiles/savegame/3ad85aea' size 256402.

[savedata] Compression of Blob 0x00000000::WETR took 24.00 us

[savedata] Unable to write file Z:/serverdata/serverfiles/savegame/3ad85aea.new: file not found

[savedata] Unable to write blob 'Z:/serverdata/serverfiles/savegame/3ad85aea' size 256444.

[server] Save Serialization took 378.86 ms over 16 Ticks

[server] Saved

Did you move the file while the server was running? If so, that's the problem. The docker lost the mapping to the files and you can't do much about it. Restarting the server should restart the mapping.

But I don't get why mover would have move those file. Files in appdata should be on ssd cache drive and never moved.

You can use unraid file explorer to see if the file exist where the mapping point to

I did try to reset the server it worked, but we did lose almost all of the progress we made. I was able to use the only backup I had and was able to save some stuff, but it is working and saving properly now. Thanks for the help.

Is there any chance we could get an image for Windrose? It'll need Proton (or Wine) as they currently only have a Windows version of their Dedicated Server tool. The Steam App ID is 4129620

1 hour ago, Sauravisus said:

Is there any chance we could get an image for Windrose? It'll need Proton (or Wine) as they currently only have a Windows version of their Dedicated Server tool. The Steam App ID is 4129620

I was really hoping someone else would ask this first. Apparently from the OPs first post, he's no longer taking requests for any new dockers. Which, is understandable. I hope he comes out of retir4one more time for this one though!!!!

1 hour ago, CoZ said:

I was really hoping someone else would ask this first. Apparently from the OPs first post, he's no longer taking requests for any new dockers. Which, is understandable. I hope he comes out of retir4one more time for this one though!!!!

I think you are talking about ich777 which is in another thread. My work do come from him though. I just have a very busy schedule and doing server for games I don't own isn't easy since I can't test. I'll see what I can do but can't really provide a time-lapse for now

Ok, so I created a windrose app. I see the server start but I cannot say if it's working or not since I don't have the game. According to the documentation and the docker I saw about this game, there's no port forward required. The game use invitation code. You must let the game fully start before closing and editing both files

16 minutes ago, Nodiaque said:

Ok, so I created a windrose app. I see the server start but I cannot say if it's working or not since I don't have the game. According to the documentation and the docker I saw about this game, there's no port forward required. The game use invitation code. You must let the game fully start before closing and editing both files

oh snap. Does it take a moment for it to show up in the community apps?

3 hours ago, Nodiaque said:

I think you are talking about ich777 which is in another thread. My work do come from him though. I just have a very busy schedule and doing server for games I don't own isn't easy since I can't test. I'll see what I can do but can't really provide a time-lapse for now

31 minutes ago, Nodiaque said:

Ok, so I created a windrose app. I see the server start but I cannot say if it's working or not since I don't have the game. According to the documentation and the docker I saw about this game, there's no port forward required. The game use invitation code. You must let the game fully start before closing and editing both files

Damn that was fast!!! It's in the CA App store already? I just arrived home and I am currently installing the game from Steam now.

You are correct, I was thinking about ich777. I'm running game servers from the both of you.

You have no interest in the Windrose game?

Edited April 15Apr 15 by CoZ

it should be I think in the hour? It's a process that does it automatically.

As for the game, I just started yesterday Soulmask so Windrose will have to wait XD

Just now, Nodiaque said:

it should be I think in the hour? It's a process that does it automatically.

As for the game, I just started yesterday Soulmask so Windrose will have to wait XD

I just tried to use the docker pull command in the CMD prompt. It pulled the container down, it just doesn't show up in my docker container tab at all.

I tried searching docker hub for it since C.A. is taking it's sweet time and I see a ton of other Windrose servers but none with your "Tag/Name" on them.

it just appeared.

Docker hub should show it since it's where it's from. You must check in the tag

nodiaque/steamcmd:windrose

But I see it in CA now

Beware of the info. This game is weird. No Port forwarding and configuration is to be done in .cfg file that are created after the whole game is launched. Which mean let it init, and then shutdown, edit, and play

Edited April 15Apr 15 by Nodiaque

Yes. I see it now. Since I ran the docker pull command, I just needed to "install" it so I didn't need to re-download it. Strange. Thanks for getting this up and going so quickly!!!

Connected to it without issue. Thanks!

EDIT: spoke too soon. After the mini tutorial, it dumped me back out to the main screen. It finds the server without any problem (it does take a while for mine to show up)

Tried a few times, goes to the loading screen and then just dumps me back out to the main menu.

!!! R5Ensure happens !!!

Condition: 'false'

Message: Unexpected BL disconnect. AccountId 4E9E699D48B726BCB33017A99F25F30D. BLPlayerSessionId '1474c42483ac4cadaa7cc83dc64fca2d'

Where: UR5DataKeeperForServer::OnAccountBLDisconnected::<lambda_10>::operator () [D:\Source\Build\work\gameRepoCheckoutDir\Source\R5DataKeepers\Private\R5DataKeeperForServer.cpp:267]

LogOutputDevice: Warning: === FR5CheckDetails::PrintCallstackToLog ===

LogOutputDevice: Warning:

LogOutputDevice: Warning: [Callstack] 0x0000000146d19311 WindroseServer-Win64-Shipping.exe!UnknownFunction []

LogOutputDevice: Warning: [Callstack] 0x0000000144e7baec WindroseServer-Win64-Shipping.exe!UnknownFunction []

LogOutputDevice: Warning: [Callstack] 0x0000000144ef9166 WindroseServer-Win64-Shipping.exe!UnknownFunction []

LogOutputDevice: Warning: [Callstack] 0x000000014445f928 WindroseServer-Win64-Shipping.exe!UnknownFunction []

LogOutputDevice: Warning: [Callstack] 0x000000014415fae5 WindroseServer-Win64-Shipping.exe!UnknownFunction []

LogOutputDevice: Warning: [Callstack] 0x000000014127ee2b WindroseServer-Win64-Shipping.exe!UnknownFunction []

LogOutputDevice: Warning: [Callstack] 0x000000014128a631 WindroseServer-Win64-Shipping.exe!UnknownFunction []

LogOutputDevice: Warning: [Callstack] 0x0000000141284adf WindroseServer-Win64-Shipping.exe!UnknownFunction []

LogOutputDevice: Warning: [Callstack] 0x00000001416e76a5 WindroseServer-Win64-Shipping.exe!UnknownFunction []

LogOutputDevice: Warning: [Callstack] 0x00000001416ede45 WindroseServer-Win64-Shipping.exe!UnknownFunction []

LogOutputDevice: Warning: [Callstack] 0x00000001416e8efe WindroseServer-Win64-Shipping.exe!UnknownFunction []

LogOutputDevice: Warning: [Callstack] 0x00000001416c006f WindroseServer-Win64-Shipping.exe!UnknownFunction []

LogOutputDevice: Warning: [Callstack] 0x00000001438548a0 WindroseServer-Win64-Shipping.exe!UnknownFunction []

LogOutputDevice: Warning: [Callstack] 0x0000000144101341 WindroseServer-Win64-Shipping.exe!UnknownFunction []

LogOutputDevice: Warning: [Callstack] 0x00000001441048bc WindroseServer-Win64-Shipping.exe!UnknownFunction []

LogOutputDevice: Warning: [Callstack] 0x000000014410493a WindroseServer-Win64-Shipping.exe!UnknownFunction []

LogOutputDevice: Warning: [Callstack] 0x00000001441053ad WindroseServer-Win64-Shipping.exe!UnknownFunction []

LogOutputDevice: Warning: [Callstack] 0x000000014410a824 WindroseServer-Win64-Shipping.exe!UnknownFunction []

LogOutputDevice: Warning: [Callstack] 0x000000014bf2734e WindroseServer-Win64-Shipping.exe!UnknownFunction []

LogOutputDevice: Warning: [Callstack] 0x00006fffffa64819 kernel32.dll!BaseThreadInitThunk() [Z:\usr\src\packages\BUILD\dlls\kernel32\thread.c:61]

LogOutputDevice: Warning: [Callstack] 0x00006fffffc3fa1b ntdll.dll!UnknownFunction []

LogOutputDevice: Warning:

Edited April 15Apr 15 by CoZ

1 hour ago, CoZ said:

Yes. I see it now. Since I ran the docker pull command, I just needed to "install" it so I didn't need to re-download it. Strange. Thanks for getting this up and going so quickly!!!

Connected to it without issue. Thanks!

EDIT: spoke too soon. After the mini tutorial, it dumped me back out to the main screen. It finds the server without any problem (it does take a while for mine to show up)

Tried a few times, goes to the loading screen and then just dumps me back out to the main menu.

!!! R5Ensure happens !!!

Condition: 'false'

Message: Unexpected BL disconnect. AccountId 4E9E699D48B726BCB33017A99F25F30D. BLPlayerSessionId '1474c42483ac4cadaa7cc83dc64fca2d'

Where: UR5DataKeeperForServer::OnAccountBLDisconnected::<lambda_10>::operator () [D:\Source\Build\work\gameRepoCheckoutDir\Source\R5DataKeepers\Private\R5DataKeeperForServer.cpp:267]

LogOutputDevice: Warning: === FR5CheckDetails::PrintCallstackToLog ===

LogOutputDevice: Warning:

LogOutputDevice: Warning: [Callstack] 0x0000000146d19311 WindroseServer-Win64-Shipping.exe!UnknownFunction []

LogOutputDevice: Warning: [Callstack] 0x0000000144e7baec WindroseServer-Win64-Shipping.exe!UnknownFunction []

LogOutputDevice: Warning: [Callstack] 0x0000000144ef9166 WindroseServer-Win64-Shipping.exe!UnknownFunction []

LogOutputDevice: Warning: [Callstack] 0x000000014445f928 WindroseServer-Win64-Shipping.exe!UnknownFunction []

LogOutputDevice: Warning: [Callstack] 0x000000014415fae5 WindroseServer-Win64-Shipping.exe!UnknownFunction []

LogOutputDevice: Warning: [Callstack] 0x000000014127ee2b WindroseServer-Win64-Shipping.exe!UnknownFunction []

LogOutputDevice: Warning: [Callstack] 0x000000014128a631 WindroseServer-Win64-Shipping.exe!UnknownFunction []

LogOutputDevice: Warning: [Callstack] 0x0000000141284adf WindroseServer-Win64-Shipping.exe!UnknownFunction []

LogOutputDevice: Warning: [Callstack] 0x00000001416e76a5 WindroseServer-Win64-Shipping.exe!UnknownFunction []

LogOutputDevice: Warning: [Callstack] 0x00000001416ede45 WindroseServer-Win64-Shipping.exe!UnknownFunction []

LogOutputDevice: Warning: [Callstack] 0x00000001416e8efe WindroseServer-Win64-Shipping.exe!UnknownFunction []

LogOutputDevice: Warning: [Callstack] 0x00000001416c006f WindroseServer-Win64-Shipping.exe!UnknownFunction []

LogOutputDevice: Warning: [Callstack] 0x00000001438548a0 WindroseServer-Win64-Shipping.exe!UnknownFunction []

LogOutputDevice: Warning: [Callstack] 0x0000000144101341 WindroseServer-Win64-Shipping.exe!UnknownFunction []

LogOutputDevice: Warning: [Callstack] 0x00000001441048bc WindroseServer-Win64-Shipping.exe!UnknownFunction []

LogOutputDevice: Warning: [Callstack] 0x000000014410493a WindroseServer-Win64-Shipping.exe!UnknownFunction []

LogOutputDevice: Warning: [Callstack] 0x00000001441053ad WindroseServer-Win64-Shipping.exe!UnknownFunction []

LogOutputDevice: Warning: [Callstack] 0x000000014410a824 WindroseServer-Win64-Shipping.exe!UnknownFunction []

LogOutputDevice: Warning: [Callstack] 0x000000014bf2734e WindroseServer-Win64-Shipping.exe!UnknownFunction []

LogOutputDevice: Warning: [Callstack] 0x00006fffffa64819 kernel32.dll!BaseThreadInitThunk() [Z:\usr\src\packages\BUILD\dlls\kernel32\thread.c:61]

LogOutputDevice: Warning: [Callstack] 0x00006fffffc3fa1b ntdll.dll!UnknownFunction []

LogOutputDevice: Warning:

Getting same error, not sure why

it could be upnp but not allowing us to specifically select the port is a bit of an odd choice. I'm trying to connect locally to my own server as well.

I did see in the steam page that there was problem right now.

Something to try is this docker from someone in the thread and see if the samething happen. I basically did the exact samething but who knows. It's not the same base docker image.

GitHub

GitHub - UberDudePL/windrose-dedicated-server-docker: Doc...

Dockerized Windrose Dedicated Server (SteamCMD + Wine) with persistent saves and 24/7 hosting setup. - UberDudePL/windrose-dedicated-server-docker

Maybe just to see if it's related or not.