CoZ

For anyone that is/was having issues copying the single player world over to the dedicated server, they've changed how it's done (again). The easiest way that I have found is to copy the entire \Username\appdata\local\R5\Saved\SaveProfiles\{Bunch of random numbers' folder\RocksDB and the RocksDB_V2 folders over to your \appdata\windrose saved world location. Then go into your windrose directory on your server, delete everything out of RocksDB and RocksDB_V2 folders that IS NOT "worlds" subdirectoy. There was an issue with the patch changing the RocksDB to RocksDB_V2 and the single player world not migrating correctly blah blah blah. I tried every which way to get it to "stick" otherwise it would just create a new world and overwrite any changes to the Serverdescription.json file that you put into it.

They aren't making it easy for us - they keep introducing breaking changes. Now for instance, since today's update, they've changed the location of the "world / save" folder. I've fixed the crashing on the container start. I've figured out the new format for copying over a single player to the dedicated server with no crashes. However, now I'm unable to connect anymore to the dedicated server as I could before with just the invite code. It's back to dropping me back into the main loading screen. Sigh. LoL

Got to post #2. You need to delete a file to "kick start" the update. It's been mentioned in this thread 30+ times now.

I sent in a bug report with what I posted earlier, the errors. I have been tinkering in the meantime. It seems that the P2pProxyAddress entry in the server.json MUST match the IP Unraid assigns it. For example, I earlier had that P2pProxyAddress set to my tower's IP address of 192.168.X.XXX and it was working fine before the updates were pushed out. I've changed it to the internal IP set by the container (172.17.0.28) and I am no longer getting the crash/restart cycle.

Yes. It's the same procedure I've used in the past to move over the world.

Just started the container after a few weeks because I'm about to travel for work and wanted to test it out. However, it's now in some sort of loop. Spits out these error messages and then re-starts... spits out the same error messages, re-starts... etc.. I've nuked the /appdata/Windrose folder. Pulled down the windrose folder again fresh. Starts fine. The error occurs when I copy over my world folder now from my localPC to the /appdata/Windrose folder and try to start the container. Maybe some permission error or something? LogOutputDevice: Error: === Crash Stack Trace: === LogOutputDevice: Error: LogOutputDevice: Error: [Callstack] 0x0000000141475686 WindroseServer-Win64-Shipping.exe!UnknownFunction [] LogOutputDevice: Error: [Callstack] 0x000000014413ba9d WindroseServer-Win64-Shipping.exe!UnknownFunction [] LogOutputDevice: Error: [Callstack] 0x00000001414024b3 WindroseServer-Win64-Shipping.exe!UnknownFunction [] LogOutputDevice: Error: [Callstack] 0x0000000141370d0a WindroseServer-Win64-Shipping.exe!UnknownFunction [] LogOutputDevice: Error: [Callstack] 0x0000000149139e6f WindroseServer-Win64-Shipping.exe!UnknownFunction [] LogOutputDevice: Error: [Callstack] 0x00000001490ff629 WindroseServer-Win64-Shipping.exe!UnknownFunction [] LogOutputDevice: Error: [Callstack] 0x000000014451e1d9 WindroseServer-Win64-Shipping.exe!UnknownFunction [] LogOutputDevice: Error: [Callstack] 0x0000000144500f21 WindroseServer-Win64-Shipping.exe!UnknownFunction [] LogOutputDevice: Error: [Callstack] 0x0000000144500903 WindroseServer-Win64-Shipping.exe!UnknownFunction [] LogOutputDevice: Error: [Callstack] 0x000000014c01d8e9 WindroseServer-Win64-Shipping.exe!UnknownFunction [] LogOutputDevice: Error: [Callstack] 0x00006ffff91f1074 VCRUNTIME140_1.dll!UnknownFunction [] LogOutputDevice: Error: [Callstack] 0x00006ffff91f239c VCRUNTIME140_1.dll!call_catch_block4() [Z:\usr\src\packages\BUILD\dlls\msvcrt\handler4.c:440] LogOutputDevice: Error: [Callstack] 0x00006fffffc3f869 ntdll.dll!UnknownFunction [] LogOutputDevice: Error: [Callstack] 0x0000000144ee2abe WindroseServer-Win64-Shipping.exe!UnknownFunction [] LogOutputDevice: Error: [Callstack] 0x0000000146b76117 WindroseServer-Win64-Shipping.exe!UnknownFunction [] LogOutputDevice: Error: [Callstack] 0x0000000146adbd13 WindroseServer-Win64-Shipping.exe!UnknownFunction [] LogOutputDevice: Error: [Callstack] 0x0000000146b51a9e WindroseServer-Win64-Shipping.exe!UnknownFunction [] LogOutputDevice: Error: [Callstack] 0x0000000141427842 WindroseServer-Win64-Shipping.exe!UnknownFunction [] LogOutputDevice: Error: [Callstack] 0x0000000146a6a404 WindroseServer-Win64-Shipping.exe!UnknownFunction [] LogOutputDevice: Error: [Callstack] 0x0000000146a72458 WindroseServer-Win64-Shipping.exe!UnknownFunction [] LogOutputDevice: Error: [Callstack] 0x000000014141ec48 WindroseServer-Win64-Shipping.exe!UnknownFunction [] LogOutputDevice: Error: [Callstack] 0x000000014128a9d1 WindroseServer-Win64-Shipping.exe!UnknownFunction [] LogOutputDevice: Error: [Callstack] 0x0000000141284e7f WindroseServer-Win64-Shipping.exe!UnknownFunction [] LogOutputDevice: Error: [Callstack] 0x00000001416e7ec5 WindroseServer-Win64-Shipping.exe!UnknownFunction [] LogOutputDevice: Error: [Callstack] 0x00000001416ee665 WindroseServer-Win64-Shipping.exe!UnknownFunction [] LogOutputDevice: Error: [Callstack] 0x00000001416e971e WindroseServer-Win64-Shipping.exe!UnknownFunction [] LogOutputDevice: Error: [Callstack] 0x00000001416c088f WindroseServer-Win64-Shipping.exe!UnknownFunction [] LogOutputDevice: Error: [Callstack] 0x00000001438550d0 WindroseServer-Win64-Shipping.exe!UnknownFunction [] LogOutputDevice: Error: [Callstack] 0x0000000144101b61 WindroseServer-Win64-Shipping.exe!UnknownFunction [] LogOutputDevice: Error: [Callstack] 0x000000014410512c WindroseServer-Win64-Shipping.exe!UnknownFunction [] LogOutputDevice: Error: [Callstack] 0x00000001441051aa WindroseServer-Win64-Shipping.exe!UnknownFunction [] LogOutputDevice: Error: [Callstack] 0x0000000144105c1d WindroseServer-Win64-Shipping.exe!UnknownFunction [] LogOutputDevice: Error: [Callstack] 0x000000014410b094 WindroseServer-Win64-Shipping.exe!UnknownFunction [] LogOutputDevice: Error: [Callstack] 0x000000014bf6aace WindroseServer-Win64-Shipping.exe!UnknownFunction [] LogOutputDevice: Error: [Callstack] 0x00006fffffa64819 kernel32.dll!BaseThreadInitThunk() [Z:\usr\src\packages\BUILD\dlls\kernel32\thread.c:61] LogOutputDevice: Error: [Callstack] 0x00006fffffc3fa1b ntdll.dll!UnknownFunction []

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.

I saw the same issue. Since I currently have no friends that have the game, I only start the container when I'm about to play. Otherwise, it stays off. Once I join, the "cores to 100" stops and everything levels out. It's damn strange.

Ok so deleting the container and the 'template container' won't delete the Windrose Appdata folder.

I just pulled down the update and none of the new parameters that you've listed show up when I edit the docker. What's the trick to getting them to show up or, should I just follow along your guide and manually create them?

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?

I haven't had an issue in bridge mode since I put my Unraid's internal IP in the server config. I can NOT vouch if it works for external access as I am still waiting on some friends to get the game. Would you not just need to point your SFTP program (FileZilla, etc) to the /appdata/Windrose/R5 directory? I would assume the mods go into there? Really? That is wild. I haven't left my running because I was watching 2 cores of my CPU spike to 100% when it was running with no one in it. (not due to Nodiaque container, it's just EA)

@Poundsy have you tried changing the "P2pProxyAddress": to the IP address of your Unraid? I am still running it in bridge mode, and I am able to connect to my server using after changing what the default entry was on that line.

@Nodiaque Greetings from Belgium. After waiting a few hours trying to download Windrose on the horrible Hotel WiFi speed and then Wireguarding into my Unraid server to start your container, I can now report that it works!!! I did not need to change it from bridge to host. It just works now. As others have stated, wow does this thing eat up some CPU and RAM even with no players on it. The DEVs need to do a lot of optimization and, quickly. Thanks again.

No I haven't tried to "self host" locally. I've got to head out to Belgium for a few days in a little bit so, I will keep an eye on this thread. When I come back, I will try the "self host" thing and report back if any issues. Sorry I can't do more at the moment. I have to pack and get ready to go. Where are you located in the World? I'm wondering if it is the whole "Russia" ISP blocking thing that someone mentioned earlier?

So, I've pulled someone else's Windrose containter down and installed it. Looking at the logs, there were a lot of different things going on in the background of that other person's container than yours when it was first booting. Regardless, the end result is still the same error message as your container that I posted earlier: Condition: 'false' Message: Unexpected BL disconnect. AccountId 4E9E699D48B726BCB33017A99F25F30D. BLPlayerSessionId 'f459599ea75f4647b4783f7dbfbc0f20' Where: UR5DataKeeperForServer::OnAccountBLDisconnected::<lambda_10>::operator () [D:\Source\Build\work\gameRepoCheckoutDir\Source\R5DataKeepers\Private\R5DataKeeperForServer.cpp:267] This other container C.T.D., at least yours dumped me out into the main menu LoL I wonder why you are, so far, the only one without any issue???

@Pieper your posts are making it sound like you were able to successfully connect to your dedicated server - is this true?

Well I thought it would be as simple as taking out your repo and pasting in "ghcr.io/uberdudepl/windrose-dedicated-server-docker:v1.0.0" and re-starting the docker. Ah no. That failed miserably. LOL His name "UberDudePL" doesn't come up in the dockerhub search in CA either so can't find it there. I have enough knowledge to be a danger to myself. I've gone ahead and removed everything related to the Windrose container/template/appdata folder. I don't want to get too far into playing a local copy because then I'm going to have to rebuild everything all over again once everyone figures out the kinks in the UnRaid dedicated.

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:

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.

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?

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

Thank you friend. I've done what you've suggested. It seems to have improved the start-up time after an update, etc and the /logs directory now contains only a few instead of hundreds of thousands of entries

So I let that command / open terminal window sit there for 2 hours or so. Nothing happened at all. All those log files are still in that directory.

So you are suggesting to copy/paste that above command into the terminal of UnRaid or, the terminal of the container? I've manually opened the .unamanic/logs/buffer directory and I have files in there from 2025..... So I went and copy/paste your above command into a terminal window in UnRaid and hit enter. It's been about 30 minutes now. I can no longer access any of my UnRaid shares over the network, it just "times out". I still have access to the UnRaid webgui though. So perhaps it's due to this command running causing it to time out over the network. However, this is making me very nervous LOL I've gone from waiting for 10-15 minutes for this container to start up to, now, hours of waiting for the container /WebGUI to start.