2 hours ago, Tombet said:

enshrouded update when? =)

It doesn't look like it's available yet. I'm using the Proton version and have tried both Release and Beta options but it's still showing Mismatched Version one I try to connect in Enshrouded.

On 4/22/2026 at 4:45 PM, Drider said:

So, I set up this container on my UnRAID server, (Was currently running Windrose server in a Windows 8.1 Enterprise VM on one of my unRAID servers.

Had no real issues getting it up and running, as well as importing my saved world, and verifying everything loaded correctly. I didn't get to testing mods, but pretty sure most will work as they did normally on the Windows VM (at least the ones you place in <\content\pak\~mods> UE4SS mods seem to not be there yet, and crash/lag the servers I've tested pretty bad so far).

The problem I had, and the reason I stopped testing, and went back to running on the Window 8.1 VM, the CPU usage is CRAZY in comparison, Honestly it makes Windows 8.1 look like the best OS ever made from Microsoft, (Which is all honesty watching the CPU Threads balance across 4 cores + 4Threads Pinned and dedicated, (Both were pinned and isolated for the Docker, and The VM) the win 8.1 is beautiful. Load balancing couldn't be split up better between all cores and threads, (even when no players are in the server, and CPU usage spikes, and I so hope the devs fix this soon)

The problem with the docker container I found in my system, there simply is no load balance, from the start of the server, regardless if players are connected or not, 2 of the non threaded cores immediately spike to 100% usage, and never come down. other assigned cores/threads barely ever take any load. (This was testes using the same pinning and isolation for both the Win8.1 VM and the container one at a time.)


I only bring this up because it's so surprising to me a docker would take so much more overhead over a VM, but I have to assume WINE is just not running as efficient, or it's multiplying the poor resource optimization of the Windrose Server.

At least for now I'll be sticking with my Windows 8.1 Enterprise VM as the differences were extremely noticeable by users in game, but plan to check back when hopefully more optimization has been made.

Thanks for your efforts with the docker.

Did you have to do anything special when moving your saved world into the docker container?

I have seen a bunch of descriptions on how to move the server over from a user to a server but I am having an issue.

I copy over the alphanumeric folder in it's entirety to my server and add it to the ../0.10.0/Worlds folder, I delete the other world that was in there, I ensure that the ServerDescription.json is updated with the matching WorldIslandId and I start the server.

A new world is created and the ServerDescription.json is overwritten with this new world ID.

If I reboot the server that new world continually persists. It's only when I try to inject my world that I am moving over that it doesn't work. I even tried using the new WorldIslandId to name the folder that I am moving over and tried updating the WorldDecription,json to match as well, thinking there were some other links somewhere that weren't working.... but that didn't work. I made sure the ownership for the files and folders are the same and made sure all users have full read write and execute permissions on the folder and all its contents....

Any ideas?

On 4/20/2026 at 12:27 PM, CoZ said:

Just tried that. It only copies the "map" over. No buildings, fast travel locations, etc..etc...

Even the places I've visited are still "shrouded" by the fog of the map. So, unless something is very wrong with those instructions.... I'm not sure what it's supposed to "bring" over from your solo play to the dedicated one?

Did you ever sort this out? I am having the same problem (seey post above)

I have done it successfully finally. You are copying the world file from your /Users/Username/appdata/local/R5....etc..etc.. to your /appdata/Windrose/R5...etc..etc.. worlds folder?

Then right-click the worlds folder name, copy it. Open up serverdescription.json and paste it into the WorldIslandId entry and save it. All while the docker container is not running.

I had forgotten to rename the WorldIslandId in the serverdescription.json file the first time and it just kept creating a "new" world over and over every time I deleted the old world file that it created.

15 minutes ago, HurracaineIke said:

Did you have to do anything special when moving your saved world into the docker container?

I have seen a bunch of descriptions on how to move the server over from a user to a server but I am having an issue.

I copy over the alphanumeric folder in it's entirety to my server and add it to the ../0.10.0/Worlds folder, I delete the other world that was in there, I ensure that the ServerDescription.json is updated with the matching WorldIslandId and I start the server.

A new world is created and the ServerDescription.json is overwritten with this new world ID.

If I reboot the server that new world continually persists. It's only when I try to inject my world that I am moving over that it doesn't work. I even tried using the new WorldIslandId to name the folder that I am moving over and tried updating the WorldDecription,json to match as well, thinking there were some other links somewhere that weren't working.... but that didn't work. I made sure the ownership for the files and folders are the same and made sure all users have full read write and execute permissions on the folder and all its contents....

Any ideas?

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 ;)

Yeah, that is what I am doing but no luck unfortunately :( it's coming as a zip file from my friend's computer and I have unzipped it, moved it onto my server, and followed all these instructions multiple times and it doesn't want to stick.

I got it! I was previously sending the unzipped folder over the network to my server which I think caused some weird permissions issues. Unzipping the folder in the destination folder solved it!

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

16 hours ago, Nodiaque said:

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 I've enabled direct connect, here is that config file:


I can't connect to it using the LAN IP (10.0.1.105), WAN IP, or any of my domains/subdomains. I also can't connect to it if I use a VPN to connect externally via WAN. Same behavior every time, I type in IPs, enter port 7777, type my password, it loads for 10-20 seconds, then reloads the main menu. I did also try the invite code, with the one thats in there on install and a custom one. I also tried with the docker in bridge and host network. I have tried the docker installed with the default wine tag and the headless wine one.

Through all those connect attempts, zero logs show on the docker logs. It just sits at

R5LogPreloader: Display: [000069] UR5Preloader::Load Start preloading GenlandiaMulty [D:\Source\Build\work\gameRepoCheckoutDir\Source\R5Preloader\Private\R5Preloader.cpp:39]

Edited April 24Apr 24 by suchamoneypit

8 hours ago, Nodiaque said:

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..

ah i understand. Sorry i'm new to unraid and dedicated servers.

thank you

3 hours ago, suchamoneypit said:

Yeah I've enabled direct connect, here is that config file:


I can't connect to it using the LAN IP (10.0.1.105), WAN IP, or any of my domains/subdomains. I also can't connect to it if I use a VPN to connect externally via WAN. Same behavior every time, I type in IPs, enter port 7777, type my password, it loads for 10-20 seconds, then reloads the main menu. I did also try the invite code, with the one thats in there on install and a custom one. I also tried with the docker in bridge and host network. I have tried the docker installed with the default wine tag and the headless wine one.

Through all those connect attempts, zero logs show on the docker logs. It just sits at

R5LogPreloader: Display: [000069] UR5Preloader::Load Start preloading GenlandiaMulty [D:\Source\Build\work\gameRepoCheckoutDir\Source\R5Preloader\Private\R5Preloader.cpp:39]

Just to make sure,..
You have Forwarded ports 7777 and 7778 UDP to your host IP for the server right?

Also when running direct IP connection invite codes will no longer work.

Edited April 24Apr 24 by Drider

2 minutes ago, Drider said:

Just to make sure,..
You have Forwarded ports 7777 and 7778 UDP to your host IP for the server right?

Also when running direct IP connection invite codes will no longer work.

Correct, I'm port forwarding 7777 and 7778 TCP/UDP. When testing via LAN it shouldn't matter either, but I've tested from LAN and WAN with port forwarding.

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.

Edited April 24Apr 24 by Nodiaque

10 hours ago, Nodiaque said:

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.

Yes I believe my game_params is correct. I left the default ports. I believe multihome should be left as 0.0.0.0


The direct IP of this server is 10.0.1.105 so that is one of the addresses im trying to direct connect to on port 7777. But like I mentioned Im trying everything, including turning on a VPN on my gaming PC and trying to connect via my WAN IP and port (which is port forwarded ports 7777-7778 TCP/UDP).

I didn't touch the DirectConnectionServerAddress because of that warning I saw also but I can give it a try. Its extra confusing because other people here seem to be having success without any trouble. I can't even connect on LAN. Which is what initially lead me to believe that the server was not starting at all and was hanging on world gen.

EDIT: no change in behavior when setting DirectConnectionServerAddress to either its LAN IP 10.0.1.105 or my WAN IP address.

Edited April 24Apr 24 by suchamoneypit

2 hours ago, suchamoneypit said:

Yes I believe my game_params is correct. I left the default ports. I believe multihome should be left as 0.0.0.0


The direct IP of this server is 10.0.1.105 so that is one of the addresses im trying to direct connect to on port 7777. But like I mentioned Im trying everything, including turning on a VPN on my gaming PC and trying to connect via my WAN IP and port (which is port forwarded ports 7777-7778 TCP/UDP).

I didn't touch the DirectConnectionServerAddress because of that warning I saw also but I can give it a try. Its extra confusing because other people here seem to be having success without any trouble. I can't even connect on LAN. Which is what initially lead me to believe that the server was not starting at all and was hanging on world gen.

EDIT: no change in behavior when setting DirectConnectionServerAddress to either its LAN IP 10.0.1.105 or my WAN IP address.

There is a weird fix that isn't mentioned anywhere except for Windrose Discord, and that's where I found it.
For some reason, and only sometimes, you will not be able to connect to your own Windrose server if you're hosting it from the same LAN. The fix is to literally hotspot your PC using mobile data, whilst leaving your Unraid server on your network. Then suddenly, you'll be able to connect without any issues whatsoever.

This is a Windrose-specific issue, and they're still working on a fix. At least they were last time I checked - I've already completed all the quest that the game offers a week ago and haven't played since; waiting on new content updates to drop before I dive back in it. So I can't say that the same issue is still happening, but nothing hurts to test out and hotspot your PC to check if it works then. (Keep in mind that I didn't use the "windrose-xvfb" tag, just the latest one)

Just searching the latest issues on their Discord - this same issue was fixed by using a mobile hotspot just 4 days ago as of writing.

Windrose currently has a ton of connection issues. There's only so much the Docker Container Maintainer can do - if anything at all. You're much better off joining Windrose Official Discord and seeking help there - the Devs are also quite active and willing to help out. They still have the Discord invite on the main menu of the game.

Edited April 25Apr 25 by Tremmert
Adding more context to the image

3 hours ago, Tremmert said:

There is a weird fix that isn't mentioned anywhere except for Windrose Discord, and that's where I found it.
For some reason, and only sometimes, you will not be able to connect to your own Windrose server if you're hosting it from the same LAN. The fix is to literally hotspot your PC using mobile data, whilst leaving your Unraid server on your network. Then suddenly, you'll be able to connect without any issues whatsoever.

This is a Windrose-specific issue, and they're still working on a fix. At least they were last time I checked - I've already completed all the quest that the game offers a week ago and haven't played since; waiting on new content updates to drop before I dive back in it. So I can't say that the same issue is still happening, but nothing hurts to test out and hotspot your PC to check if it works then. (Keep in mind that I didn't use the "windrose-xvfb" tag, just the latest one)

Just searching the latest issues on their Discord - this same issue was fixed by using a mobile hotspot just 4 days ago as of writing.

Windrose currently has a ton of connection issues. There's only so much the Docker Container Maintainer can do - if anything at all. You're much better off joining Windrose Official Discord and seeking help there - the Devs are also quite active and willing to help out. They still have the Discord invite on the main menu of the game.

By attempting to connect via a VPN, I am connecting as if I were connecting from the outside just like a mobile data hotspot, and I still can't connect. I have also tried with and without windrose-xvfb.

1 hour ago, suchamoneypit said:

By attempting to connect via a VPN, I am connecting as if I were connecting from the outside just like a mobile data hotspot, and I still can't connect. I have also tried with and without windrose-xvfb.

I only every ran the docker with network Type set to host.
I then assigned an internal IP, open and available, outside my DHCP pool, managed by my Gateway.

Local IP connection, and remote connection via testing VPS from New York, to my gateway's external IP both worked from the start after setting my ServerDescription.json , "similar" to how you've set yours.

You're issue definitely sounds of networking configuration. Are you by chance running a vLAN on the same host as where your Docker resides with your Winrose server, and/or a vLAN within your gateway local network/internet traffic?

Outside of networking within unRAID, specifically if you're indeed running a vLAN, I would start looking at network configurations outside your unRAID server

Edited April 25Apr 25 by Drider
grammar / additional thought

I installed the docker, but I get an error in the log:
Loading Steam API...IPC function call IClientUtils::GetSteamRealm took too long: 60 msec

Can anybody tell me how to fix that?

On 4/23/2026 at 5:58 PM, thunderclap said:

It doesn't look like it's available yet. I'm using the Proton version and have tried both Release and Beta options but it's still showing Mismatched Version one I try to connect in Enshrouded.

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

6 hours ago, Drider said:

I only every ran the docker with network Type set to host.
I then assigned an internal IP, open and available, outside my DHCP pool, managed by my Gateway.

Local IP connection, and remote connection via testing VPS from New York, to my gateway's external IP both worked from the start after setting my ServerDescription.json , "similar" to how you've set yours.

You're issue definitely sounds of networking configuration. Are you by chance running a vLAN on the same host as where your Docker resides with your Winrose server, and/or a vLAN within your gateway local network/internet traffic?

Outside of networking within unRAID, specifically if you're indeed running a vLAN, I would start looking at network configurations outside your unRAID server

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.

4 minutes ago, C.Imre said:

I installed the docker, but I get an error in the log:
Loading Steam API...IPC function call IClientUtils::GetSteamRealm took too long: 60 msec

Can anybody tell me how to fix that?

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

2 minutes ago, Nodiaque said:

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

I'm aware of the procedure and have done it. I've also installed fresh versions of the docker but still no update.

Just now, thunderclap said:

I'm aware of the procedure and have done it. I've also installed fresh versions of the docker but still no update.

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).

Edited April 25Apr 25 by Nodiaque

SteamCmdForcePlatformType" = "windows"

Connecting anonymously to Steam Public...OK
Waiting for client config...OK
Waiting for user info...OK
Success! App '4129620' already up to date.
Unloading Steam API...OK
---Checking if WINE workdirectory is present---
---WINE workdirectory found---
---Checking if WINE is properly installed---
---WINE properly set up---
---Prepare Server---
---Server ready---
---Start Server---
Starting Windrose dedicated server
Executable: /serverdata/serverfiles/R5/Binaries/Win64/WindroseServer-Win64-Shipping.exe
---Ensuring UID: 99 matches user---
usermod: no changes
---Ensuring GID: 100 matches user---
usermod: no changes
---Setting umask to 000---
---Checking for optional scripts---
---No optional script found, continuing---
---Taking ownership of data...---
---Starting...---
---Update SteamCMD---
Redirecting stderr to '/serverdata/Steam/logs/stderr.txt'
Logging directory: '/serverdata/Steam/logs'
[  0%] Checking for available updates...
[----] Verifying installation...
UpdateUI: skip show logo
Steam Console Client (c) Valve Corporation - version 1773426366
-- type 'quit' to exit --
Loading Steam API...IPC function call IClientUtils::GetSteamRealm took too long: 59 msec
OK

Connecting anonymously to Steam Public...OK

Screenshot of the appdata

It downloaded everything, above the logfile and the link to the screenshot of the appdata.

Where do I find the complete logfile?

Here the error:

Starting Windrose dedicated server
Executable: /serverdata/serverfiles/R5/Binaries/Win64/WindroseServer-Win64-Shipping.exe
error: XDG_RUNTIME_DIR is invalid or not set in the environment.
wine: Unhandled illegal instruction at address 000000014147CC38 (thread 0024), starting debugger...
0130:err:winediag:nodrv_CreateWindow Application tried to create a window, but no driver could be loaded.
0130:err:winediag:nodrv_CreateWindow L"Make sure that your display server is running and that its variables are set."
0128:err:winediag:nodrv_CreateWindow Application tried to create a window, but no driver could be loaded.
0128:err:winediag:nodrv_CreateWindow L"Make sure that your display server is running and that its variables are set."
0128:fixme:dbghelp:elf_search_auxv can't find symbol in module
0128:fixme:dbghelp:elf_search_auxv can't find symbol in module

Edited April 25Apr 25 by C.Imre

9 hours ago, Nodiaque said:

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.

Yes I miss-typed, I meant I set Network to Custom Br0, then assigned the IP

20 hours ago, Drider said:

I only every ran the docker with network Type set to host.
I then assigned an internal IP, open and available, outside my DHCP pool, managed by my Gateway.

Local IP connection, and remote connection via testing VPS from New York, to my gateway's external IP both worked from the start after setting my ServerDescription.json , "similar" to how you've set yours.

You're issue definitely sounds of networking configuration. Are you by chance running a vLAN on the same host as where your Docker resides with your Winrose server, and/or a vLAN within your gateway local network/internet traffic?

Outside of networking within unRAID, specifically if you're indeed running a vLAN, I would start looking at network configurations outside your unRAID server

I've had a friend connect via a true external connection and still no connection. I tried bridge and host networking. I have many other services and servers hosted that are working fine, including my abiotic factor server that operates on the same port. This server works for internal and external just fine. I am not actively running it though because it conflicts with Windrose.